Messages in this thread | | | Date | Mon, 31 May 1999 17:45:13 +0200 (CEST) | From | Morten Storgaard Nielsen <> | Subject | Crashing linux 2.2.[4-6] - what to do? |
| |
My linux has got the Redmond disease :-(
Maybe it's becase it's standing next to a lot of NT's, but anyway...
I'm quite unsure where to send this oops, since I haven't found out what causes it ( except that it maybe has smthg. to do with the swap). I'd like a litte additional information, about how to aid the debugging process - or a clue to whether it might be a hardware error or smthg. like that. Or eventully a hint saying that I might solve the problem by upgrading to NT ... nah not that I think
I've concluded the report in three different parts: OOPS decription SYSTEM description RUNNING decription
- after thouroghly reading the /usr/src/linux/Doc*/oops*
OOPS DESCR. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The regulartity of the crashes is giving max 2 or 3 days uptime. The syslog doesn't report any kernel oopses but the screen dump is something like:
Oops: 0000 CPU: 0 EIP: 0010: [<c011e62c>] Eflags: 00010086 eax: cf89e49c ebx: c009e140 ecx:00000000 edx: c0217a88 esi: cf89e400 edi: 00000202 ebp:00000026 esp: c0227eec Process swapper ( pid: 0, process nr: 0, stackpage=c0227000 ) Aiee killing int handler Kernel Panic Attempted to kill the idle task ! In swapper task - not syncing
Running through ksymoops doesn't yield very much - at least not for a kernel illiterate person such as I:
[root@gatekeeper ksymoops]# cat ~/oops | ./ksymoops -v /usr/src/linux/vmlinux -m /usr/src/linux/System.map Options used: -v /usr/src/linux/vmlinux (specified) -o /lib/modules/2.2.6/ (default) -k /proc/ksyms (default) -l /proc/modules (default) -m /usr/src/linux/System.map (specified) -c 1 (default)
Oops: 0000 CPU: 0 EIP: 0010: [<c011e62c>] Eflags: 00010086 eax: cf89e49c ebx: c009e140 ecx:00000000 edx: c0217a88 esi: cf89e400 edi: 00000202 ebp:00000026 esp: c0227eec Process swapper ( pid: 0, process nr: 0, stackpage=c0227000 ) Aiee killing int handler Kernel Panic Attempted to kill the idle task ! In swapper task - not syncing Warning, Code line not seen, dumping what data is available
>>EIP: c011e62c <kfree+74/1b8>
1 warning issued. Results may not be reliable. [root@gatekeeper ksymoops]#
OOPS DESCR. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
SYSTEM DESCR. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> RH 5.2 kernel 2.2.6 (plain vanilla) (crashed also with 2.2.4-4, 2.2.5 but not 2.0.* series ...)
120MB swap 256MB ram (Digital DS21142/3 Tulip tulip.o ) Intel Etherexpress 10/100 eepro100.o
crashes with either one..
Adaptec AHA-294X Ultra SCSI with 5 scsi disks type IBM DCAS-34330W
processor: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 5 model name : Pentium II (Deschutes) stepping : 0 cpu MHz : 334.099314 cache size : 512 KB fdiv_bug : no hlt_bug : no sep_bug : no f00f_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx osfxsr bogomips : 333.41
SYSTEM DESCR. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
RUNNING DESCR. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
The machine performs as a proxy and gateway running squid-2.1.PATCH2. I don't think the machine is very heavily loaded since it's only getting 1000hits/min on the top and usually has a lower load. It is dimensioned to have a higher load, but people tends to avoid unstable proxies if they can... the load in therms of netw.-througput I estimate to be appx.: less than 1Mbit on peak . It does though use up a lot of filedescriptors, which was the reason for upgrading to kernel 2.2.* it couldn't get the filehandle patch to work :-( for 2.0.36.
Besides the squid proxy the machine has: tis firewall toolkit with telnet ftp pop3 realplayer nntp -proxies
apache webserver for interfacing the statistics (only for administration)
socks 4 socks 5 + some other RH things...
RUNNIG DESCR. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |