Messages in this thread |  | | Date | Tue, 27 Mar 2001 19:26:21 -0500 | | From | jgarzik@mandrake ... | | Subject | Re: 2.4.2 and NETDEV WATCHDOG |
| |
Jens Gecius wrote: > > John Madden <weez@freelists.org> writes: > > > I'm receiving the following errors while botting a previously-fine 2.2 > > machine (Dell 2450, 2 eepro 100's): > > > > NETDEV WATCHDOG: eth0: transmit timed out > > eth0: Transmit timed out: status f048 0c00 at 0/28 command 001a000 > > Same here on 2.4.1 smp with two dirt-cheap ne2pci-clones. System > unusuable (as stated by clem ealier today) and need for > reboot. Nothing special happened on the box before. > > Other message in that context: > > Mar 21 18:28:58 maniac kernel: NETDEV WATCHDOG: eth1: transmit timed out > Mar 21 18:28:58 maniac kernel: eth1: Tx timed out, lost interrupt? > TSR=0x3, ISR=0x3, t=27.
This is a generic message generated by card-specific errors and events. The same message does not imply that the two problems are at all related...
-- Jeff Garzik | May you have warm words on a cold evening, Building 1024 | a full moon on a dark night, MandrakeSoft | and a smooth road all the way to your door. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |