On Mon, 2011-11-21 at 20:13 +0100, Bjørn Mork wrote: > Looks like my wife did some external scans of our home network :-) > > Have to investigate further how she managed to kill the interface, but > this is definitely not related to the driver upgrade. Sorry for my > misleading initial report.
So far as I'm aware, if the TX watchdog fires it indicates one of: 1. A bug in the driver, firmware or hardware caused the hardware transmit queue to stop. 2. A bug in the driver, firmware or hardware meant that the kernel was not notified of link-down or another interruption that is expected to stop the hardware transmit queue. 3. Transmission is being continually blocked by (full-duplex link) pause frames or (half-duplex link) collisions. This may occur due to a switch misconfiguration or inconsistent configuration between switch and host. High levels of traffic or specific traffic patterns that overload the CPU should never cause this to happen. As the primary maintainer of another Linux network driver, I have to treat every 'TX watchdog' report as a bug unless it falls into case 3. So I don't want to just forget this either. But if you can't reproduce it, it may be difficult to track down. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else.
signature.asc
Description: This is a digitally signed message part
