Code: <1>Unable to handle kernel NULL pointer dereference at virtual
address 00000000
current->tss.cr3 = 01eb0000, %cr3 = 01eb0000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0108c11>]
EFLAGS: 00010046
eax: 00000000 ebx: 00000000 ecx: 00000000 edx: c0fda000
esi: 0000002b edi: c1eb4000 ebp: c2800000 esp: c1eb3e3c
ds: 0018 es: 0018 ss: 0018
Process apmd (pid: 115, process nr: 11, stackpage=c1eb3000)
Stack: 000066ae c1eb2000 c01fad4e 00004102 000066ae c1eb3f04 0000000e
00000001
00000002 00000000 00000000 00010046 02000000 c3000000 c0108c74
c1eb3ec0
c01b3278 c01b474e 00000000 00000000 c010dbf4 c01b474e c1eb3ec0
00000000
Call Trace: [<c3000000>] [<c0108c74>] [<c01b3278>] [<c01b474e>]
[<c010dbf4>] [<c01b474e>] [<c01088b5>]
[<c0106294>] [<c0106388>] [<c01063ab>] [<c0106762>] [<c0106d43>]
[<c012b4ed>] [<c01087b0>]
Code: 8a 04 0b 89 44 24 38 50 68 70 32 1b c0 e8 11 98 00 00 83 c4
Passing this into ksymoops gives a bunch of mismatch warnings then
>>EIP: c0108c11 <die_if_no_fixup+3d/40>
Trace: c3000000 <END_OF_CODE+7772ac/????>
Trace: c0108c74 <do_int3+0/60>
Trace: c01b3278 <error_table+9d4/1edc>
Trace: c01b474e <error_table+1eaa/1edc>
Trace: c010dbf4 <remap_area_pages+50/250>
Trace: c01b474e <error_table+1eaa/1edc>
Trace: c01088b5 <reserved+5/c>
Trace: c0106294 <apm_bios_call_simple+38/60>
Code: c0108c11 <die_if_no_fixup+3d/40> 00000000 <_EIP>: <===
Code: c0108c11 <die_if_no_fixup+3d/40> 0: 8a 04
0b movb (%ebx,%ecx,1),%al <===
Code: c0108c14 <do_divide_error+0/60> 3: 89 44 24
38 movl %eax,0x38(%esp,1)
Code: c0108c18 <do_divide_error+4/60> 7:
50 pushl %eax
Code: c0108c19 <do_divide_error+5/60> 8: 68 70 32 1b
c0 pushl $0xc01b3270
Code: c0108c1e <do_divide_error+a/60> d: e8 11 98 00
00 call c0112434 <printk+a0/174>
Code: c0108c23 <do_divide_error+f/60> 12: 83 c4
00 addl $0x0,%esp n:
My kernel configuration for apm is as follows:
Advanced Power Management BIOS support: ON
Ignore USER SUSPEND: OFF
Enable PM at boot time: OFF
Make CPU Idle calls when idle: OFF
Enable console blanking using APM: OFF
Power off on shutdown: ON
Ignore multiple suspend: OFF
Ignore multiple suspend/resume cycles: OFF
/var/log/messages reports that APM starts OK at boot. No messages are
recorded regarding the oops.
cat /proc/apm reports: 1.9 1.2 0x03 0x01 0xff 0xff -1% -1 ?
(the -1% is because I don't have a battery installed at the moment - but
APM works fine with DOS without any special drivers, so I don't think
this is the problem)
If there's any more information I can give please let me know. I'm new
to oopses (oopsi?)
Mark Paterson
-
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/