On Tue, Jan 30, 2007 at 02:46:59PM +0530, vimal.raj wrote:
> 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??
See Documentation/oops-tracing.txt.
> 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
^^^^^^^^^
Proprietary module loaded, Oops may be incorrect. Could be your own
module if you forgot a proper MODULE_LICENSE().
> 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>]
>
> 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.
The Oopses will be much easier to understand when you enable
CONFIG_STACKTRACE, CONFIG_FRAME_POINTER, and CONFIG_DEBUG_VERBOSE.
Erik
--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
Attachment:
signature.asc
Description: Digital signature
