Re: eth*: transmit timed out since .27 (was: linux-2.4.27 released)

[Marcelo Tosatti]

Hi Oliver,

On Tue, Aug 10, 2004 at 02:23:34PM +0200, Oliver Feiler wrote:
> Hi,
> 
> I've upgraded a server from .26 to .27, but ran into problems with the network 
> cards.
> 
> The kernel throws a lot of errors into the syslog and the net devices don't 
> work:
> Aug 10 13:39:25 spot kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Aug 10 13:39:26 spot kernel: NETDEV WATCHDOG: eth1: transmit timed out
> Aug 10 13:39:26 spot kernel: eth1: Transmit timeout, status 00000004 00000249 
> Aug 10 13:39:34 spot kernel: NETDEV WATCHDOG: eth1: transmit timed out
> Aug 10 13:39:34 spot kernel: eth1: Transmit timeout, status 00000004 00000241 
> Aug 10 13:39:42 spot kernel: NETDEV WATCHDOG: eth1: transmit timed out
> Aug 10 13:39:42 spot kernel: eth1: Transmit timeout, status 00000004 00000240 
> [...]
> 
> and:
> Aug 10 13:39:25 spot kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, 
> ISR=0x3, t=515.
> Aug 10 13:40:25 spot kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, 
> ISR=0x3, t=5015.
> Aug 10 13:40:40 spot kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, 
> ISR=0x3, t=1014.
> [...]
> 
> The system has three network cards.
> eth0: SIS900 (sis900.c)
> eth1: RTL-8029 (ne2k-pci.c)
> eth2: onboard VIA VT6102 Rhine-II (via-rhine.c)
> 
> eth0 and eth1 share the same interrupt
> 
>            CPU0       
>   0:      91986          XT-PIC  timer
>   1:        935          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   8:          1          XT-PIC  rtc
>   9:          0          XT-PIC  acpi
>  10:      25109          XT-PIC  via82cxxx, usb-uhci, usb-uhci, eth0, eth1
>  11:         24          XT-PIC  usb-uhci, eth2
>  14:       7523          XT-PIC  ide0
>  15:       7021          XT-PIC  ide1
> NMI:          0 
> ERR:          0

Wow, you have four devices on the same interrupt line. /proc/interrupts
from 2.4.26/27 looks the same?

> That was not a problem in .26 however. Though it seems to be the cause of the 
> problem (lost interrupt)? The hardware this is all running on is an Asrock 
> K7VM4 mainboard. The system is booted with "pci=noacpi" (ACPI, no APM). 
> Otherwise IRQ255 is assigned to IDE and someone told me the noacpi parameter 
> would fix the board's braindead BIOS.
> 
> Either way .27 doesn't want to boot. I've attached dmesg from a running 2.4.26 
> kernel and the config used for 2.4.27.

You mean it boots but you get the Tx timeouts?

> Other postings I've found say that the transmit timeouts mean that the 
> lowlevel ethernet connection between the NICs broke. But this works fine in 
> earlier kernels and only eth0 and eth1 which share an interrupt are affected. 
> I'd be glad for any more suggestions on what might be causing this. :)

Well there are some changes to sis900 between .26 and .27 but I doubt
they could be causing it.

Can you try to boot with ACPI disabled? I think the problem might be 
related to ACPI configuration. 

Also, can you post the boot messages from 2.4.27?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/