Hi!
Reproducible panic when squid gets the first request. Always at the same
place in the pinger process. test12, test13-pre3 fail, but test12 runs
fine on another machine with nearly the same config (netcard and disk
drivers differ, and the failing machine has devfs).
Hardware: Compaq proliant dl360 with a quad starfire card, UP
(Serverworks chipset), cpqarray.
Unable to handle kernel NULL pointer dereference at virtual address 003c
c01a20de
*pde =
Oops:
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: ebx: ecx: c7b5e9e0 edx: c7b5e9e0
esi: 1fb1 edi: c7b09c00 ebp: 1df0 esp: c6e4bc40
ds: 0018 es: 0018 ss: 0018
Process pinger (pid: 289, stackpage=c6e4b000)
Stack: c7b5e9e0 8b5e 017f 0014 c01a2453 c7b5e9e0
c7b09c00 c6e4e500 c7b09c00 c01a4db8 c6e4bd44 11e4bc84 c01c5770
c7b09c00 c6e4bd34 c029d998 c01c5089 c7b09c00 c6e4bd34 c029d998 c01a4db8
Call Trace: [] [] [] [] []
[] []
[] [] [] [] [] []
[] []
[] [] [] [] [] []
[] []
[] [] [] [] [] []
[] []
[] []
Code: 8b 40 3c 89 41 3c 8b 47 5c c7 47 18 00 00 00 00 01 41 18 8b
>>EIP; c01a20de<=
Trace; c01a2453
Trace; c01a4db8
Trace; c01c5770
Trace; c01c5089
Trace; c01a4db8
Trace; c0108dc8
Trace; c01c44e0
Trace; c01a4db8
Trace; c018ea5c
Trace; c01a4db8
Trace; c01a4db8
Trace; c018ec73
Trace; c01a4db8
Trace; c01a440b
Trace; c01a4db8
Trace; c01b82cc
Trace; c01a450e
Trace; c01b82cc
Trace; c01b8725
Trace; c01b82cc
Trace; c018815b
Trace; c0188db0
Trace; c01b7aec
Trace; c01bd5d6
Trace; c01857d5
Trace; c018641c
Trace; c0128a37 <__free_pages+13/14>
Trace; c0128a72
Trace; c013a6da
Trace; c013a9d8
Trace; c018645a
Trace; c0186bb1
Trace; c0108d1f
Code; c01a20de
<_EIP>:
Code; c01a20de<=
0: 8b 40 3c mov0x3c(%eax),%eax <=
Code; c01a20e1
3: 89 41 3c mov%eax,0x3c(%ecx)
Code; c01a20e4
6: 8b 47 5c mov0x5c(%edi),%eax
Code; c01a20e7
9: c7 47 18 00 00 00 00 movl $0x0,0x18(%edi)
Code; c01a20ee
10: 01 41 18 add%eax,0x18(%ecx)
Code; c01a20f1
13: 8b 00 mov(%eax),%eax
Kernel panic: Aiee, killing interrupt handler!
Does anyone know, what this can be? If any other information would be
needed, please tell me! Thanks.
--
Dani
...and Linux for all.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/