Re: [PLEASE REVERT] "Add a WARN_ON_ONCE" at net/sched/sch_generic.c:

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <komurojun-mbn@...>
Cc: <linux-kernel@...>, <netdev@...>
Date: Tuesday, May 27, 2008 - 9:14 am

From: Komuro <komurojun-mbn@nifty.com>
Date: Tue, 27 May 2008 21:34:24 +0900


The MAC of the chip transmits and ACKs the packet in the hardware even
if the link is down.  The packet is simply dropped.

Also, when the link goes down, the driver should mark the device as
such.  In such a state, the generic networking does not pass new
packets to the driver.

Therefore, transmit timeouts in this case are a hardware
or driver error.

If there is an IRQ issue, that is an error that'd we would like to
have as much information as possible to diagnose.  So the warning is
still entirely appropriate.

I sense that you are seeing this warning triggered, and if so I
would suggest that you investigate it fully as it should not be
happening under normal circumstances.
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
RE: NETDEV WATCHDOG: wifi0: transmit timed out, Komuro, (Tue Jul 29, 8:53 am)
Re: NETDEV WATCHDOG: wifi0: transmit timed out, Arjan van de Ven, (Tue Jul 29, 9:58 am)
Re: NETDEV WATCHDOG: wifi0: transmit timed out, Arjan van de Ven, (Wed Jul 30, 9:22 am)
Re: NETDEV WATCHDOG: wifi0: transmit timed out, Justin Mattock, (Wed Jul 30, 10:55 am)
Re: NETDEV WATCHDOG: wifi0: transmit timed out, David Miller, (Tue Jul 29, 4:47 pm)
Re: NETDEV WATCHDOG: wifi0: transmit timed out, Justin Mattock, (Tue Jul 29, 6:48 pm)
Re: NETDEV WATCHDOG: wifi0: transmit timed out, Dan Williams, (Wed Jul 30, 7:41 am)
Re: NETDEV WATCHDOG: wifi0: transmit timed out, Justin Mattock, (Tue Jul 29, 9:43 am)
Re: [PLEASE REVERT] "Add a WARN_ON_ONCE" at net/sched/sch_ge..., David Miller, (Tue May 27, 9:14 am)