Hi;
we have 4 Intel boxes running linux. Their primary occupation are
being xterminal-servers. All of the machines have 512Mb Ram and twice
the size swap. Each have approximately 15 xterminals connected. The
Cpus range from dual 350 Pentium II to dual 550 Pentium III
Before we upgraded to 2.2.x (from 2.0.36) the machines were very
stable.
Since we upgraded (first to 2.2.14) the machines have been a real
pain. The freeze totally (approximately once a day) with messages as
the one below. We have applied the pacthes we could find - latest
patch is 2.2.15pre7 (some of the earlier patches include aa6 aa7 pre6
pre5) - without any change in behavior.
Special configuration:
/usr/src/linux/include/linux/tasks.h: NR_TASKS is raised to 2048
The first time after the upgrade "wild" netscape and gs processes also
caused the Oopses (By wild we mean processes that hangs/remains after
the user is logged out and are using a lot of CPU). This we have
solved now by running a script killing these processes. Since that all
the oopses are caused by "Process swapper".
A typical Oops is:
Unable to handle kernel NULL pointer dereference at virtual address 00000015
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<80131dd8>]
EFLAGS: 00010202
eax: 00006204 ebx: 00000015 ecx: 00000202 edx: 9c762000
esi: 8024b800 edi: 0050a37e ebp: fc370001 esp: 80249eb0
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=80249000)
Stack: 8b6286c0 0000001d 80169be3 8fb1ff6c 00000002 8ff9c520 8015ccaf 98d738c0 8015d642 8ff9c520 00000000 0050a37e a089260c 8ff9c520 90557440 04000001
00000000 00000009 000000e0 80173188 000008b6 00000002 a6def081 70172720Call Trace: [<80169be3>] [<8015ccaf>] [<8015d642>] [<a089260c>] [<80173188>] [<8016580e>] [<8010b5d2>]
[<80110022>] [<8010b743>] [<8010a218>] [<80107a1d>] [<80106000>] [<8010000>] [<801001b1>]
Code: 81 3b 01 46 00 00 74 10 68 a0 f0 1e 80 e8 32 43 fe ff 83 c4
Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing
+++++++++++++++++++++++++++++++++++++++++++++++++++++
The result of running ksymoops is:
WARNING: This version of ksymoops is obsolete.
WARNING: The current version can be obtained from ftp://ftp.ocs.com.au/pub/ksymoops
Options used: -V (default)
-o /lib/modules/2.2.15/ (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-m /boot/System.map (specified)
-c 1 (default)
Unable to handle kernel NULL pointer dereference at virtual address 00000015
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<80131dd8>]
EFLAGS: 00010202
eax: 00006204 ebx: 00000015 ecx: 00000202 edx: 9c762000
esi: 8024b800 edi: 0050a37e ebp: fc370001 esp: 80249eb0
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=80249000)
Stack: 8b6286c0 0000001d 80169be3 8fb1ff6c 00000002 8ff9c520 8015ccaf 98d738c0 8015d642 8ff9c520 00000000 0050a37e a089260c 8ff9c520 90557440 04000001
00000000 00000009 000000e0 80173188 000008b6 00000002 a6def081 70172720Call Trace: [<80169be3>] [<8015ccaf>] [<8015d642>] [<a089260c>] [<80173188>] [<8016580e>] [<8010b5d2>]
[<80110022>] [<8010b743>] [<8010a218>] [<80107a1d>] [<80106000>] [<8010000>] [<801001b1>]
Code: 81 3b 01 46 00 00 74 10 68 a0 f0 1e 80 e8 32 43 fe ff 83 c4
Warning: trailing garbage ignored on Code: line
Text: 'Code: 81 3b 01 46 00 00 74 10 68 a0 f0 1e 80 e8 32 43 fe ff 83 c4 '
Garbage: ' '
>>EIP: 80131dd8 <kill_fasync+c/44>
Code: 80131dd8 <kill_fasync+c/44> 00000000 <_EIP>: <===
Code: 80131dd8 <kill_fasync+c/44> 0: 81 3b 01 46 00 00
cmpl $0x4601,(%ebx) <===
Code: 80131dde <kill_fasync+12/44> 6: 74 10
je 80131df0 <kill_fasync+24/44>
Code: 80131de0 <kill_fasync+14/44> 8: 68 a0 f0 1e 80
pushl $0x801ef0a0
Code: 80131de5 <kill_fasync+19/44> d: e8 32 43 fe ff
call 8011611c <printk+0/184>
Code: 80131dea <kill_fasync+1e/44> 12: 83 c4 00
addl $0x0,%esp
Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing
Regards
Halvard Moe
-
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/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:18 EST