Realtek 8139 driver or sucky hardware?
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.
Signature · 2 lines
Systems and Network Administrator - Delta Romania Phone +4093-267961
Quoted 5 lines · Silviu Marin-Caea
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?
Quoted 3 lines · On Wed, 27 Jun 2001 10:05:20 +0200 Matthias Andree…
Quoted 1 line · Silviu Marin-Caea
No matter what stupid things I do on it, I shouldn't be able to take
the
Quoted 6 lines
Quoted 4 lines
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
Quoted 1 line
What driver did you use? 8129/8139 or 8139too?
8139too
Signature · 2 lines
Systems and Network Administrator - Delta Romania Phone +4093-267961
Quoted 2 lines · Silviu Marin-Caea
I have a server that had a Realtek 8139 card that worked nicely under normal circumstances.
[...]
Quoted 2 lines
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
Signature · 3 lines
Jeff Garzik | Andre the Giant has a posse. Building 1024 | MandrakeSoft |
Quoted 2 lines · On Wed, 27 Jun 2001 07:34:27 -0400 Jeff Garzik <[email protected]> wrote:
Quoted 1 line · Silviu Marin-Caea
I have a server that had a Realtek 8139 card that worked nicely
under
Quoted 3 lines
Quoted 1 line
normal circumstances.
[...]
Quoted 1 line
This crazy situation had the server freeze solid, with only cold
boot as
Quoted 4 lines
Quoted 1 line
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!! :-)
Signature · 2 lines
Systems and Network Administrator - Delta Romania Phone +4093-267961