Hello,
I have a lockup issue where the only thing that seems to work is the
networking portion of the kernel. We speratically have random servers that
"lockup" (no keyboard response, though the num-lock button still turns on
and off num-lock light, nothing displayed on the screen, nothing logged
into /var/log/messages, no core dumps on reboot, and none of the crons that
are cronned (like sa) ever run). The odd part is that the server pings, and
you can get established TCP sessions to the machine, although the underlying
programs never respond. (ie, I get an established socket to port 22, but the
ssh server doesn't respond at all (never prompts for a passed, etc), same
result on port 80, no response.). We currently are useing kernel 2.4.18,
with Intel EtherExpress 10/100 cards , AMD 2.1 ghz processors, 2 gigs of
ram, with an 80 gig IDE HD's. I have had our hardware department take a look
at the servers for ram issues errors, or processor issues, but nothing
apparent has ever shown up. Has anyone else experienced this sort of
behavior? I currently have a machine that is "locked" up like this ( and has
been for 24 hours), so I can test anyones ideas. The current bandwidth
showing from the mrtg graphs from the switch that I have is only showing
broadcast traffic.
Justin Booth
[justinb@test justinb]$ ping 192.168.1.11
PING 192.168.1.11 (192.168.1.11) from 192.168.1.12 : 56(84) bytes of data.
64 bytes from 192.168.1.11: icmp_seq=1 ttl=255 time=0.175 ms
64 bytes from 192.168.1.11: icmp_seq=2 ttl=255 time=0.130 ms
64 bytes from 192.168.1.11: icmp_seq=3 ttl=255 time=0.141 ms
---192.168.1.11 ping statistics ---
3 packets transmitted, 3 received, 0% loss, time 1998ms
rtt min/avg/max/mdev = 0.130/0.148/0.175/0.023 ms
[justinb@test justinb]$ ssh -l justinb 192.168.1.11
[1]+ Stopped ssh -l justinb 192.168.1.11
[justinb@test justinb]$ bg 1
[1]+ ssh -l justinb 192.168.1.11 &
[justinb@test justinb]$ netstat -an |grep 22
tcp 0 0 10.0.0.93:34329 192.168.1.11:22
ESTABLISHED
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
