Bug#245398: via_rhine timeout problem persists
Well, spoke too soon two years ago,
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (750ns min, 2000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 177
Region 0: I/O ports at c400 [size=256]
Region 1: Memory at b2001000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Somewhere down the line in 2.6.x kernels, something broke. My current
setup is running ACPI=off since since 2.6.17, leaving ACPI on caused the
kernel to spend huge amount of time in almost any syscall. But now,
transferring data to a different box gives me,
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
$ netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP
TX-OVR Flg
eth0 1500 0 1898616 0 0 0 2373172 10 0
0 BMRU
lo 16436 0 394 0 0 0 394 0 0
0 LRU
Each timeout is indicated by the TX-ERR.
This bug seems to persist. Other NICs work perfectly. A workaround was
to install another NIC and disable the onboard one.
- Adam
Reply to: