lkml.org 
[lkml]   [2001]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 2.4.2 and NETDEV WATCHDOG - different bug?
From
Date
	jgarzik@mandrakesoft.com writes:

> > > 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...

Then, my question will be, why is the kernel loosing the irq for eth1
and gets unusable?

Sorry I didn't know about the generic message.

--
Tschoe, Get my gpg-public-key here
Jens http://gecius.de/gpg-key.txt
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:17    [W:0.788 / U:0.668 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site