What can I do to trace where the error is coming from? Its easy to see from the output that there is a null pointer in there somewhere: But where to from here?
Run your oops through "ksymoops". It will resolve the numbers in the oops to a human readable format, so you and we can have a look where the oops is actually taking place in the code.
Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: de9c8a15 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<de9c8a15>] Not tainted EFLAGS: 00010a96 eax: 00000000 ebx: 00000001 ecx: 00000000 edx: c0000000 esi: 00000000 edi: 00000001 ebp: db605e2c esp: db605dac ds: 0018 es: 0018 ss: 0018 Process modprobe (pid: 3576, stackpage=db605000) Stack: 00000001 de9fd000 de9a7e8d 00000001 00000000 00000001 de9d4a20 de9c8d60 de9d4a20 db605e2c 00000001 de9d4a64 de9d4a24 00000001 de9fd000 de9a7e8d de9d4a24 db605e2c 00000001 db4c4000 00000014 db605f04 de9fd1fe de9d4a24 Call Trace: [<de9a7e8d>] [<de9d4a20>] [<de9c8d60>] [<de9d4a20>] [<de9d4a64>] [<de9d4a24>] [<de9a7e8d>] [<de9d4a24>] [<de9fd1fe>] [<de9d4a24>] [<de9f42bb>] [<de9f51d0>] [<de9e6610>] [<de9e67ec>] [<de9ed880>] [<de9e68c2>] [<de9fd534>] [<de9fd1b0>] [<de9fe518>] [<de9fd7e8>] [<de9fd9ef>] [<c011bd4b>] [<de9fd060>] [<de9fe07c>] [<de9fd060>] [<de9fd060>] [<c0109103>]
Code: 0f b6 00 c1 e0 10 09 c2 89 d6 81 ce 8b 00 00 00 66 83 7d 04
> Any help much appreciated.
You must be extremely carful that you compile all modules and drivers against the same header files, ie. make sure that no old header files are lying around for example in /usr/include/linux that may be used by accident.
> Thanks, > Rob Wills
CU Michael.
-- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
