bug in via-rhine network-driver (transmit timed out)

bug in via-rhine network-driver (transmit timed out)

[ksardem]

Hi,

my Linux-PC (Kernel 2.4.19, SuSE 8.1)
has two PCI D-LINK DFE530-TX network card (10/100mbit) using driver via-rhine.o
Sometimes one or both of the interfaces (eth0/eth1) "time out", which means I
cannot send or transmit any more packets on this interface.

When I do a 'dmesg' I get these error-messages:

NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: Setting half-duplex based on MII #8 link partner capability of 0021.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
...and so on

or:
NETDEV WATCHDOG: eth1: transmit timed out
eth1: Transmit timed out, status 0000, PHY status 782d, resetting...
eth1: reset did not complete in 10 ms.
NETDEV WATCHDOG: eth1: transmit timed out
eth1: Transmit timed out, status 0000, PHY status 782d, resetting...
eth1: reset did not complete in 10 ms.
...

I had the same problem with the D-LINK DFE-530TX-cards some time ago
with earlier releases of the 2.4.x-Kernel.
If I do a 'ifconfig eth0/eth1 down', 'rmmod via-rhine' and then
again 'modprove via-rhine' and 'ifconfig up...' it works again but
this is no real solution - I think it's a bug in the driver, isn't it?

This is my version of the via-rhine module:
V_NAME        "via-rhine"
DRV_VERSION     "1.1.14"
DRV_RELDATE     "May-3-2002"

Here are some informations about my system which may be helpful:

/proc/modules:
via-rhine              13612   2
mii                     1232   0 [via-rhine]

/proc/version:
Linux version 2.4.19-my (root@geeko) (gcc version 3.2)

/proc/cpuinfo: 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 5
model name      : Pentium II (Deschutes)
stepping        : 2
cpu MHz         : 349.968
cache size      : 512 KB

/proc/ioports:
e400-e4ff : PCI device 1106:3065
  e400-e4ff : via-rhine
e800-e8ff : PCI device 1106:3065
  e800-e8ff : via-rhine
f000-f00f : PCI device 8086:7111

/proc/iomem:
e2000000-e20000ff : PCI device 1106:3065
  e2000000-e20000ff : via-rhine
e2001000-e20010ff : PCI device 1106:3065
  e2001000-e20010ff : via-rhine

lspci -vvv:
00:09.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 43)
        Subsystem: D-Link System Inc DFE-530TX rev A
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B-Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
        Latency: 64 (750ns min, 2000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 9
        Region 0: I/O ports at e400 [size=256]
        Region 1: Memory at e2001000 (32-bit, non-prefetchable) [size=256]
        Expansion ROM at e0000000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot
-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0a.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 43)
        Subsystem: D-Link System Inc DFE-530TX rev A
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
        Latency: 64 (750ns min, 2000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 9
        Region 0: I/O ports at e800 [size=256]
        Region 1: Memory at e2000000 (32-bit, non-prefetchable) [size=256]
 Expansion ROM at e1000000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot
-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
01:00.0


Thanks for any help.
Bye.

Re: bug in via-rhine network-driver (transmit timed out)

[Justin A]

I had the same problem with the integrated nic on a soyo k7vdragon+

search google/the archives for "via-rhine timeouts"

Try the linuxfet driver found here:

http://www.viaarena.com/?PageID=87#ethernet
http://downloads.viaarena.com/LinuxApplicationNotes/RedHat/May02/VIA%20RH7.2-7.1%20Fast%20Ethernet%20Controller%20Driver%20Installation%20ver%200.9.gz

I've been using it since then without problems.  I had to change malloc.h or 
whatever it used to be to slab.h a few versions ago to make it compile 
without whining, but thats all.
-- 
-Justin

Re: bug in via-rhine network-driver (transmit timed out)

[Manfred Spraul]

>
>
>When I do a 'dmesg' I get these error-messages:
>
>NETDEV WATCHDOG: eth0: transmit timed out
>eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
>eth0: reset did not complete in 10 ms.
>NETDEV WATCHDOG: eth0: transmit timed out
>
The tx_timeout code performs a full hardware reset to recover from 
hangs, but it seems that the nic hangs during the hardware reset :-(

The hang could be caused by incomplete tx underrun handling, the 
linuxfet driver resets several registers after a tx underrun.
Could you load the driver with debug=3? For example by adding 'options 
via-rhine debug=3' into your /etc/modules.conf?

If it hangs again, then send the dmesg messages to the mailing list - 
especially the last few lines before the first transmit timeout will help.

--
    Manfred

Re: bug in via-rhine network-driver (transmit timed out)

[ksardem]

Hi,

I successfully got the old transmit-out-error again ;-)
- and this time with "options via-rhine debug=3" in modules.conf.
So here are the debug-messages:

dmesg:

eth0: Shutting down ethercard, status was 081a.
eth0: via_rhine_open() irq 9.
eth0: reset finished after 5 microseconds.
eth0: Done via_rhine_open(), status 081a MII status: 7809.
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Shutting down ethercard, status was 883a.
eth0: via_rhine_open() irq 9.
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Done via_rhine_open(), status 881a MII status: 782d.
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Shutting down ethercard, status was 883a.
eth0: via_rhine_open() irq 9.
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Done via_rhine_open(), status 881a MII status: 7829.
eth0: Shutting down ethercard, status was 883a.  

lsmod was:

via-rhine 13612 2
mii        1232 0 [via-rhine]

-- 
Bye.
Kristof <ksardem@linux01.gwdg.de>

Re: bug in via-rhine network-driver (transmit timed out)

[Jeff Garzik]

On Mon, Dec 09, 2002 at 05:54:07PM +0100, ksardem@linux01.gwdg.de wrote:
> Hi,
> 
> I successfully got the old transmit-out-error again ;-)
> - and this time with "options via-rhine debug=3" in modules.conf.

Does booting with "noapic" in lilo/grub fix this?

Re[2]: bug in via-rhine network-driver (transmit timed out)

[Kristof Sardemann]

Hi,

>> 
>> I successfully got the old transmit-out-error again ;-)
>> - and this time with "options via-rhine debug=3" in modules.conf.

JG> Does booting with "noapic" in lilo/grub fix this?
Yes, it did - as I mentioned in my previous postings ;)
..this was just a debug-report for source-bugfixing.

--
Bye.
Kristof <ksardem@linux01.gwdg.de>

Adaptec 2940 not working on 2.5.50

[David Lang]

after watching from the sidelines for a while I finally had some time to
try the 2.5 kernels over the weekend.

unfortunantly I was unable to build a kernel that will work for me.

the system is a K6-3 400 with several IDE drives and a SCSI drive hooked
to an adaptec 2940. LILO and the boot kernels are on IDE, but the linux
root filesystem is on the SCSI drive

I compile the kernel without a problem, but when it boots it generates
several screens of errors as it attempts to initialize the SCSI buss.
unfortunantly I don't have a serial console on that box so I haven't been
able to capture the messages (I can't capture dmesg becouse the system
never finds the drive and so can't complete the boot)

I have verbose errors turned on, and have attempted both the old and the
new drivers with the same results.

this system ran 2.4.0 up until about two months ago when I upgraded to
2.4.18 and has had no problems.

a quick google search has not found any posts about this, although
2.5.50-ac1 has a fix for this driver (doesn't sound like quite the same
problem though)

suggestions? additional info required?

David Lang