> > Using the updated rtl8139 in 2.3.18ac5 turned out to be not really a
> > pleasure. Actually, the card reliably hangs in rtl8129_open(). And it
> > hangs the whole machine, "hang" meaning I can't even use the ATX power
> > switch to turn it off. Don't even think about magic syskeys and the like.
>
> At that point you have to ask some hard questions about the hardware. An ATX
> level crash is normally a PCI bus hang. In this case the change you have
> made is disabling PCI posting, and it could easily be a real PCI posting
> bug if there are delay loops involved.
>
> What chipset is this ?
It's an MSI-6120 SMP board.
belbo@yksi:~> /sbin/lspci -s00:00 -vvv
00:00.0 Host bridge: Intel Corporation 440BX - 82443BX Host (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
Latency: 64 set
Region 0: Memory at e8000000 (32-bit, prefetchable)
I just tried a vanilla ac5 on my server and it locks as well on the
Realtek. The ATX switch was still functional though. I have to add that on
my other machine where did most of the testing, I usually used the reset
button, the ATX thing there was just a tried once, failed once. On my
server I tried twice. The lock-ups were identical except the ATX switch
kept working.
My server is an ASUS XP55T2P4 UP.
belbo@abulafia:~> /sbin/lspci -vvv -s00:00
00:00.0 Host bridge: Intel Corporation 430HX - 82439HX TXC [Triton II]
(rev 03)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ >SERR- <PERR-
Latency: 32 set
Is anyone else able to use the vanilla rtl8139 in ac5?
Regards,
Daniel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/