[lkml]   [1999]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectThe Deadly `ping -f'
Hello, world!

There's a scary problem with the newer kernels (tried 2.2.3 and 2.2.6) and
flood ping. I was able to kill my computer with the following (as root):
# (ping -f somehost) & (ping -f otherhost) &
I would consider this as a serious bug.

The machine fell into the ever-interesting land of __delay, __udelay and
__global_cli (as witnessed with SysRq-P), and was not able to respond
outside pings. Unfortunately, SysRq-U (or -S) didn't work.

Nothing in the logs, either. A solitary `ping -f' seems to work okay (but
didn't under 2.2.3, IIRC), but I only tried for a minute or so.

This is on a 2xPII with 3c509 and IPv4. The 3c509 is compiled as a module,
and there were no other modules loaded. My .config is available upon
request. ping version is from Debian (potato) netbase 3.12-2. If I left
out something relevant please be so kind and tell me.

The machine (and network) in question are mine and I can try patches or
provide more info.

Taneli <>

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:51    [W:0.069 / U:0.240 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site