R8169 on 2.6.0-test9
Quoted 1 line
The r8169 gigabit ethernet card causes lockups on both 2.4.22 and
2.6.0-test9.
It does it even on 2.4.20 and using the 8139cp. Heres lspci -vvv, starting to wonder if this card is special/odd/unsupported or if its just this hardware not being happy.
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 (rev
10)
Subsystem: CNet Technology Inc ProG-2000L
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 (8000ns min, 16000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at e000 [size=256]
Region 1: Memory at e8000000 (32-bit, non-prefetchable) [size=256] Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mAPME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
---
John Bäckstrand
Quoted 6 lines · John Bäckstrand
Quoted 1 line
The r8169 gigabit ethernet card causes lockups on both 2.4.22 and
2.6.0-test9.
It does it even on 2.4.20 and using the 8139cp. Heres lspci -vvv, starting to wonder if this card is special/odd/unsupported or if its just this hardware not being happy.
This is bug report is somewhat confusing, are you using r8169.c (CONFIG_R8169)?
Quoted 9 lines
Quoted 6 lines
Quoted 1 line
The r8169 gigabit ethernet card causes lockups on both 2.4.22 and
2.6.0-test9.
It does it even on 2.4.20 and using the 8139cp. Heres lspci -vvv, starting to wonder if this card is special/odd/unsupported or if its just this hardware not being happy.
This is bug report is somewhat confusing, are you using
r8169.c(CONFIG_R8169)?
I have tried the r8169 driver on 2.4.22 and 2.6.0-test9, and r8139cp on 2.4.20. On 2.4.22, it printed "too much work at interrupt" forever after 3-60 seconds of connection to a lan. I commented the printk out, that didnt help though. The behaviour is exactly the same on 2.6.0-test9 and 2.4.20, a few seconds after "ifconfig eth1 up" the machine hangs, though on 2.4.20 atleast there was no printk message seen. ifconfig shows it does receive and send a few packets before it hangs, atleast on 2.4.22. The 8169 cards have been confirmed to be working, but not on this particular motherboard though.
---
John Bäckstrand
Quoted 8 lines · John Bäckstrand
I have tried the r8169 driver on 2.4.22 and 2.6.0-test9, and r8139cp on 2.4.20. On 2.4.22, it printed "too much work at interrupt" forever after 3-60 seconds of connection to a lan. I commented the printk out, that didnt help though. The behaviour is exactly the same on 2.6.0-test9 and 2.4.20, a few seconds after "ifconfig eth1 up" the machine hangs, though on 2.4.20 atleast there was no printk message seen. ifconfig shows it does receive and send a few packets before it hangs, atleast on 2.4.22. The 8169 cards have been confirmed to be working, but not on this particular motherboard though.
Let's stick to r8169 for now, can you send a dmesg from test9 also throw in /proc/interrupts.
Quoted 1 line
Let's stick to r8169 for now
The cnet page on the product (http://www.cnet.com.tw/product/prog-2000s.htm)
states it requires PCI 2.2, the motherboard was only 2.1. Sorry for the inconvenience.
---
John Bäckstrand