On 1/30/07, vimal.raj <vimal.raj@xxxxxxxxxxxxxxxxxx> wrote:
Hi,
In RT Linux when I try to run my module my kernel crashes and i get an Oops
message
So can someone explain what this trace down there means ?
Where do I get information regarding these messages, how can I learn to
understand them ? and debug it??
Code: ff 00 0f 88 8d 04 00 00 89 74 24 04 89 1c 24 e8 54 4b 01 00
<1> Unable to handle kernel NULL pointer dereference at virtual address
0000002c
printing eip:
c0122780
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0122780>] Tainted:P
EFLAGS: 00010206
eax: ffffffff ebx: cf05a568 ecx: 00000000 edx: 00000028
esi: cf05a568 edi: 00000014 ebp: 00000001 esp: cf05be3c
ds: 0018 es: 0018 ss: 0018
Process (pid:0 stackpage = cf05b000)
Stack: 00000010 00000202 cf05a000 00000000 cf05a000 c0122984 00000014 cf05a568
00000009 c0122c02 00000009 cf05a000 00000000 00021324 cf05a000
00000000
00000000 c0121928 00000009 00000001 cf05a000 cf05a000 cf05a000
00000000
Call Trace: [<c0122984>] [<c0122c02>] [<c0121928>] [<c012198d>] [<c0121b58>]
[<c010e51b>] [<c010a802>] [<c010a9d4>] [<e08ca782>]
[<e08ca7b0>]
[<e08ca7d5>] [<c0109960>] [<c0115574>]
Try using ksymoops to display you the readable backtrace of the stack.
Have you tried CONFIG_KALLSYMS?
CODE: 39 7A 04 74 IB 89 D3 8B 13 85 D2 75 F3 B9 01 00 00 00 83 C4
<0> Kernel panic: Aiee, killing interrupt handler!
In Interrupt handler- not syncing.
Not sure ... but are you doing something that is trying to sleep in
atomic context? (try using in_atomic())
Regards,
Rajat
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
