On Sun, 30 Jun 2002 04:29, Svetoslav Slavtchev wrote:
> and what does this mean
>
> Unable to handle kernel NULL pointer dereference*pde = 000
> 00000
It means what it says. You have a pointer that is not initialised, or is
initialised to zero, and it is being dereferenced. Could be just about
anything, although the most common error is to forget to kmalloc a structure,
and then reference an element.
> Oops: 0000
> CPU: 1
> EIP: 0010:[<c0216111>] Not tainted
> EFLAGS: 00010297
> eax: 0000007e ebx: 00000000 ecx: 0000007e edx: 00000001
> esi: c2ad1010 edi: 0000007e ebp: c12d7d58 esp: c12d7d40
> ds: 0018 es: 0018 ss: 0018
> Process swapper (pid: 0, stackpage=c12d7000)
> Stack: c12d7d58 00000001 0000007e 00000001 c2ad1010 0000007e c12d7d6c
> c021635a 00000000 0000007e 00000001 c12d7d9c c0265ffd c2269ce0 00000001
> 0000007e 00000001 00000000 33323130 c2269ce0 c24e2460 00000001 c24e2500
> c12d7dcc Call Trace: [<c021635a>] [<c0265ffd>] [<c0265b98>] [<c02629ba>]
> [<c0262ae7>] [<c0240a28>] [<c0262d14>] [<c0262d38>] [<c28e31b2>]
> [<c28e357e>] [<c28e3621>]
>
> [<c010a004>] [<c010a34b>] [<c010c638>] [<c0106eb4>] [<c0106ef7>]
> [<c011b2a8>]
>
> [<c011b112>] [<c0105000>]
>
> Code: 8b 33 74 12 0f b6 45 f0 00 c0 30 d0 0f b6 c0 50 e8 ac 49 ff
> Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing
You can figure out where the problem is by running this through a program
called ksymoops, which turns these stack variables back into a call trace.
You _must_ do this yourself, with a System.map file that matches your kernel
compile.
Brad
--
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
|
