Red Hat Bugzilla – Bug 57219
Network crashes when under load (such as downloading files)
Last modified: 2007-04-18 12:38:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Description of problem:
Networking was fine with RH 7.1 on the same machine. After doing a clean
install of RH 7.2 I immediately began seeing network failures. I did
another clean reinstall producing the same results. The net will seem OK
until I try to download something using (lynx, netscape, ftp, etc.) It
seems that the additional load of the download will cause a hang/stall
never to recover. After failure I will Ctl<C> out of the program and do a
ifdown/ifup. This will bring the net back up. It will fail consistantly
any time I try to download. I am using a static IP connecting to a hub
connecting to a LinkSys router. I have tried reconfiguring several times
with different IP's with the same result.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Try to download a file using Netscape, Lynx, FTP, etc..
2.The download process will stall/hang
3.Ctl<C> out of the program.
5.Repeat the process to cause another failure.
Actual Results: The network will stall/hang/fail.
Expected Results: A succesful file download
1)I have a Toshiba 2805-S402 Satellite with a Pentium 850 and 256M RAM.
2)The only error messages I have seen (in messages) is:
kernel: NETDEV WATCHDOG: eth0: transmit times out
kernel: eth0: Transmit timed out: status 0050 0c80 at 504/532 command
The network also crashes with normal browser (surfing) usage.
Any idea what network card this is ?
Yes, it is an Intel Pro/100 VE.
Ok then I have recently made a kernel with a fix for eepro100 crashes:
I'd be very interested to know if this kernel fixes your problem too....
I installed your fixed kernel (2.4.9-17.6) and have been testing it for several
minutes. The results are the same. When I download (or browse) the network
Anything else I can do to aid in debug? Do you want me to attach log files,
config. info., etc..
You can try to use the e100 module instead (by replacing "eepro100" with "e100"
in the /etc/modules.conf file)... it has a few more workarounds for hardware
As per your advice I installed the e100 module. I have been testing it for a
few minutes and it seems to be working. I have downloaded some large files that
always produced failure with the eepro100 module. What is the downside to using
the e100 module versus the eepro100? (performance?). I am using it in
conjunction with your (2.4.9-17.6) kernel. Is this OK? Will it be stable? Will
there be a fix to the eepro100 module in the near future? Thanks for the help...
the quality of the e100 driver implementation is rather poor; however in normal
cases you won't notice it; in corner cases (such as network error conditions)
the driver can freeze your system for several seconds though... however that
still beats not working at all ;(
Will there be a fix for the eepro100 driver in the near future?
We're doing what we can, but Intel is "not exactly helpful" with this.
*** This bug has been marked as a duplicate of 56058 ***
This bug may not be a duplicate of #56058. The kernel messages are different.
This sounds like the APIC problem (maybe) that seems to affect a lot of ne2k-pci
users (I just got bit by this).
There's a patch which may fix the problem here:
It's speculation on my part, but I thought I'd suggest it. I'm testing the
latest errata kernel on my machine now, after the APIC problem left it down all