Kernel 2.4.0 Panic?
I'm running an SMP 2.4.0 kernel on a production webserver and experienced a
rather odd situation half an hour ago. Everything was working fine for
hours, but then the system unexpectedly slowed down to a literal crawl. I
couldn't get many commands into the shell to get info, but a quick 'w'
showed a load of ~2, then a 'ps aux' showed nothing out of the ordinary in
terms of processes running on the server. I killed the apache daemons
thinking they might have been hording resources, but that did not change the
situation. At the end, I couldn't type anything at all (pings to the box
revealed ~50% packet loss from another server connected on the same 100mbps
switch) and had to power cycle the system. It came back online just fine.
Here's an excerpt of the syslog file up to the restart. It appears that
*something* happened and dumped a bunch of repeating binary symbols into the
syslog:
Jan 23 16:32:16 omega kernel: reset_xmit_timer sk=e35fbcc0 1 when=0x3598,
caller
=c0218172
Jan 23 16:32:16 omega kernel: reset_xmit_timer sk=e35fbcc0 1 when=0x31ed,
caller
=c0218172
Jan 23 16:32:16 omega cucipop[26130]: Opened nikon's mailbox
Jan 23 16:32:16 omega cucipop[26139]: Opened hieu's mailbox
Jan 23 16:32:16 omega cucipop[26139]: hieu 134.139.23.69 0, 0 (0), 0 (0)
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Jan 23 17:24:38 omega syslogd 1.3-3#33.1:
restart.
Jan 23 17:24:38 omega kernel: klogd 1.3-3#33.1, log source = /proc/kmsg
started.
Jan 23 17:24:38 omega kernel: Inspecting /boot/System.map-2.4.0
Jan 23 17:24:39 omega kernel: Loaded 15215 symbols from
/boot/System.map-2.4.0.
Jan 23 17:24:39 omega kernel: Symbols match kernel version 2.4.0.
Jan 23 17:24:39 omega kernel: No module symbols loaded.
Jan 23 17:24:39 omega kernel: Linux version 2.4.0 (root@omega) (gcc version
2.95
.2 20000220 (Debian GNU/Linux)) #1 SMP Fri Jan 19 23:03:21 PST 2001
Can someone provide insight on how to determine the cause of the problem?
--
Vibol Hou
KhmerConnection, http://khmer.cc
"Connecting Cambodian Minds, Art, and Culture"
Reply to: