Realtek 8139 driver or sucky hardware?

Realtek 8139 driver or sucky hardware?

[Silviu Marin-Caea]

I have a server that had a Realtek 8139 card that worked nicely under
normal circumstances.

But I made a mistake in a crontab and I had 60 instances of a backup
script starting one per minute, all of them wishing to create the same
.tar.gz into a samba mounted share.

This crazy situation had the server freeze solid, with only cold boot as
remedy.

No matter what stupid things I do on it, I shouldn't be able to take the
kernel down, right?

After I replaced the Realtek with a 3com, I could see all of the 60
instances fighting like worms in shit, but the server survived.

Kernel 2.4.5 compiled with Red Hat gcc 2.96-81.  With kgcc, it was
acting the same way.

Please CC me.

Thank you.

-- 
Systems and Network Administrator - Delta Romania
Phone +4093-267961

Re: Realtek 8139 driver or sucky hardware?

[Matthias Andree]

On Wed, 27 Jun 2001, Silviu Marin-Caea wrote:

> No matter what stupid things I do on it, I shouldn't be able to take the
> kernel down, right?
> 
> After I replaced the Realtek with a 3com, I could see all of the 60
> instances fighting like worms in shit, but the server survived.

Did the card share IRQs with another card?

What driver did you use? 8129/8139 or 8139too?

Re: Realtek 8139 driver or sucky hardware?

[Silviu Marin-Caea]

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

On Wed, 27 Jun 2001 10:05:20 +0200
Matthias Andree <matthias.andree@stud.uni-dortmund.de> wrote:

> On Wed, 27 Jun 2001, Silviu Marin-Caea wrote:
> 
> > No matter what stupid things I do on it, I shouldn't be able to take
the
> > kernel down, right?
> > 
> > After I replaced the Realtek with a 3com, I could see all of the 60
> > instances fighting like worms in shit, but the server survived.
> 
> Did the card share IRQs with another card?

I can tell you about the present situation, with the 3com plugged in the
same PCI slot.

After looking at dmesg and lspci -vv, I see that it shares the same IRQ
with the USB controller; but I did not compile USB support into the
kernel.

PCI: PCI BIOS revision 2.10 entry at 0xfb1b0, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
PCI: Found IRQ 10 for device 00:07.2
PCI: The same IRQ used for device 00:0d.0
Limiting direct PCI/PCI transfers.
[...]
PCI: Enabling device 00:0e.0 (0005 -> 0007)
PCI: Found IRQ 11 for device 00:0e.0
PCI: The same IRQ used for device 00:0a.1
[...]
PCI: Found IRQ 11 for device 00:0a.1
PCI: The same IRQ used for device 00:0e.0

> What driver did you use? 8129/8139 or 8139too?

8139too

-- 
Systems and Network Administrator - Delta Romania
Phone +4093-267961

[-- Attachment #2: lspci --]
[-- Type: application/octet-stream, Size: 6355 bytes --]

00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
        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: 64
        Region 0: Memory at e0000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [a0] AGP version 1.0
                Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
                Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) (prog-if 00 [Normal decode])
        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: 64
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
        Memory behind bridge: d8000000-dfffffff
        BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B+

00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
        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: 0

00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master])
        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
        Region 4: I/O ports at f000 [size=16]

00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
        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
        Interrupt: pin D routed to IRQ 10
        Region 4: I/O ports at d000 [size=32]

00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
        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-
        Interrupt: pin ? routed to IRQ 9

00:0a.0 PCI bridge: Intel Corporation: Unknown device 0962 (rev 02) (prog-if 00 [Normal decode])
        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, cache line size 08
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
        BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-

00:0a.1 RAID bus controller: Mylex Corporation: Unknown device 0050 (rev 02)
        Subsystem: Mylex Corporation: Unknown device 0052
        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, cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at e7000000 (32-bit, prefetchable) [size=8K]
        Expansion ROM at e4000000 [disabled] [size=32K]
        Capabilities: [80] 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:0d.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 64)
        Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
        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 (2500ns min, 2500ns max), cache line size 08
        Interrupt: pin A routed to IRQ 10
        Region 0: I/O ports at d400 [size=128]
        Region 1: Memory at e7002000 (32-bit, non-prefetchable) [size=128]
        Expansion ROM at e5000000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0e.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366 (rev 03)
        Subsystem: Triones Technologies, Inc.: Unknown device 0001
        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: 64 (2000ns min, 2000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at d800 [size=8]
        Region 1: I/O ports at dc00 [size=4]
        Region 2: I/O ports at e000 [size=8]
        Region 3: I/O ports at e400 [size=4]
        Region 4: I/O ports at e800 [size=256]
        Expansion ROM at e6000000 [disabled] [size=128K]
        Capabilities: [60] 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 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02) (prog-if 00 [VGA])
        Subsystem: S3 Inc. Trio3D/2X
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Ca        Region 0: Memory at d8000000 (32-bit, non-prefetchable) [size=64M]
        Expansion ROM at <unassigned> [disabled] [size=64K]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [80] AGP version 1.0
                Status: RQ=31 SBA- 64bit- FW- Rate=x1,x2
                Command: RQ=0 SBA- AGP- 64bit- FW- Rate=x2
p+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (1000ns min, 63750ns max)

Re: Realtek 8139 driver or sucky hardware?

[Jeff Garzik]

Silviu Marin-Caea wrote:
> I have a server that had a Realtek 8139 card that worked nicely under
> normal circumstances.
[...]
> This crazy situation had the server freeze solid, with only cold boot as
> remedy.

Driver.  Crash fix is in 2.4.6-pre5, and a more complete fix should be
out in the next day or two.

	Jeff


-- 
Jeff Garzik      | Andre the Giant has a posse.
Building 1024    |
MandrakeSoft     |

Re: Realtek 8139 driver or sucky hardware?

[Silviu Marin-Caea]

On Wed, 27 Jun 2001 07:34:27 -0400
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:

> Silviu Marin-Caea wrote:
> > I have a server that had a Realtek 8139 card that worked nicely
under
> > normal circumstances.
> [...]
> > This crazy situation had the server freeze solid, with only cold
boot as
> > remedy.
> 
> Driver.  Crash fix is in 2.4.6-pre5, and a more complete fix should be
> out in the next day or two.

Impressive!! :-)

-- 
Systems and Network Administrator - Delta Romania
Phone +4093-267961