Re: [PATCH] scheduler cleanup

Ramon Pasetes (rayp@frosty.fnal.gov)
Thu, 14 Oct 1999 14:22:08 -0500 (CDT)

Hello,
We are experiencing a lot of system crashes on our machines and were
wondering if anyone else had similar experiences or could shed some
light as to what the problem may be. We have run both the RH 2.2.10 and
2.2.12 kernel (smp) on these machines with the same result. The hardware is:

2x PIII 500
512MB ECC memory
6.4GB Seagate ST36421A system disk (IDE, bus 0)
2x 17GB Maxtor 91700U5 (6800 series) data disks (IDE, bus 1)
Supermicro P6 DBE/DGE Motherboard
Intel eepro 100 Network card

The crash message we usually see is:

Unable to handle kernel NULL pointer dereference at virtual address 00000080
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0002
CPU: 1
EIP: 0010:[<8010a963>]
EFLAGS: 00010046
eax: 00000080 ebx: 8076a000 ecx: 9e360000 edx: 8076a000
esi: 00000000 edi: 00000000 ebp: 00000000 esp: 8076bfb0
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 1, stackpage=8076b000)
Stack: 00000010 00000246 00000000 8022c3b8 00000000 00001100 00000000 8022c3a0
80227f78 80106000 00001000 00000000 00090018 80100018 00000078 8010808a
00000010 00000206 ffffffff 0009e200
Call Trace: [<80106000>] [<80100018>] [<8010808a>]
Code: 90 68 01 ff ff ff eb d1 90 68 02 ffOct 14 13:01:06 fnd049 kernel: Unable
t
o handle kernel NULL pointer dereference at virtual address 00000080 ^M^M
ff ff eb c9 90 68 03 ff
Kernel panic: Attempted to kill the idle task!
Unable to handle kernel NULL pointer dereference at virtual address 00000040
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0002
CPU: 1
EIP: 0010:[<80113c0c>]
EFLAGS: 00010096
eax: 00000000 ebx: 8076a000 ecx: 00000002 edx: 00000000
esi: 8076be64 edi: 0000002a ebp: 8076be48 esp: 8076be34
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 1, stackpage=8076b000)
Stack: 0000002a 0000003b 00000004 00000001 80238010 00001601 80188a96 802434c0
0000002a 80a52160 00001601 00000286 8076a000 9e051edc 801895de 0000002a
00001601 00000000 8076beec 00000001 00000400 00000002 00000246 000000f4
MCall Trace: [<80188a96>] [<801895de>] [<80189873>] [<8012c222>] [<8012c33e>]
[<
8012c383>] [<80116ce5>]
[<8011b20f>] [<801e6550>] [<80109d23>] [<80111686>] [<801e5dbc>]
[<801099
79>] [<8010a963>] [<80107deb>]
[<80106000>] [<80100018>] [<8010808a>]
Code: 89 42 40 89 50 3c c7 43 3c 00 00 00 00 c7 43 40 00 00 00 00
Kernel panic: Attempted to kill the idle task!

We are running the machines fairly hard (~98% cpu, hard disk activity about
once per hour lasting anywhere from a couple of minutes to 15 minutes). We
have also seen the machine swap a little. When we reduce the load on the
machine, we seem to be a little more stable. We are running the seti
program (from seti@home), bonnie (the disk bench test) and netttest (from NCSA)
concurrently.

Thank you for your time,
Ray

-
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/