Freeze when ping flooded
Brought to you by:
jgarzik
When I am ping flooded (don't ask why) with 20000 size
packets (possible a lot other sizes as well) my
computer hangs after a few minutes (sometimes
instantly, sometimes after 5 minutes).
This is even if I try to ignore pings with:
/bin/echo "1" > /proc/sys/net/ipv4/icmp_echo_ignore_all
Otherwise I have no problems with the drivers at all
and my network works fine.
I have compiled the module with debugging info, but in
this case the computer doesn't hang, so I can't see
where the problem is. I cannot really tell if this is
the same bug reported already.
output from rtl8139-diag and /proc/pci
Logged In: YES
user_id=407603
yeah, everybody who buyed such a rtl8139 card hands up and shame..
i also have such a thing, and tested it already with kernel 2.4.3, 5, 10, 14, 16, 17 and some alan cox
patches. then (when i have installed the kernel) and want to send or rescieve a large file to that box, via
http smb or ftp, the machine hangs, with no messages in syslog or something similar.
yesterday i installed that 2.4.17 thing and the rtl8139too 0.9.22a driver. reboot, test, and the machine
hangs. then i added pio instead mmio for the card, and after that, the box runs fine for 4 or 5 hours. after i
celebrated my success, i want to send (or rescieve? ..never mind..) a file to the box, after a minute or so,
the collision led on the hub starts blinking, and the machine died (aargh!).
i really dont know what i shall do (in fact, i know - but i dont want to buy a new ethernet card..).
for information, theres also an 3c509b 10mb/s card in the computer, that works fine, but not with the hub
;(
if somebody is interested (probably not..) to help me, drop me a message in icq (33101192) or an email.
and uh, b4 i forget: after the machine hangs up, linux starts fsck the next time i start the box, and reports
a large amount of errors on the filesystem, and asks for root passwort or ctrl-D for shell. is there a way to
skip that point, so that i can run fsck <AFTER> booting via ssh ? ( i dont have a keyboard or monitor
connected to that box, so its really terrible to work on that machine..)
thanks,
Patrick
Logged In: YES
user_id=17443
This problem is fixed in the latest version of the driver. You
can download the driver from the download section on this
SourceForge web page.