Kernel bug trying to enable more kernel debugging

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I get this when trying to boot my kernel. I am trying to find the cause of a lockup in the networking that could be related to memory handling.

NET: Registered protocol family 1
Kprobe smoke test started
Kprobe smoke test passed successfully
Unable to handle kernel paging request at virtual address 0040000c
ptbr = 90222000 pgd = 00000000
Oops: Kernel access of bad area, sig: 11 [#1]
FRAME_POINTER chip: 0x01f:0x1e82 rev 2
Modules linked in:
PC is at preh_val+0x2/0x4
LR is at vprintk+0x342/0x350
pc : [<908a16e6>]    lr : [<90024592>]    Not tainted
<0>sp : 91c29ea0  r12: 00000000  r11: 9018198e
r10: 900240f4  r9 : 00400002  r8 : 00000000
r7 : 00000000  r6 : 00000000  r5 : eef9ff68  r4 : 91c29ef4
r3 : 908a16e4  r2 : 00000000  r1 : 00000000  r0 : 90049494
Flags: qvnZc
Mode bits: hjmde....g
CPU Mode: Supervisor
Process: swapper [1] (task: 91c20000 thread: 91c28000)
Stack: (0x91c29ea0 to 0x91c2a000)
9ea0: 91c29eb0 908a16e4 00000000 00000000 90049690 91c29ef4 908a16e4 00000000
9ec0: 00000000 90049494 91c29ed8 908a16e4 9036ae68 00000000 90049608 91c29ef4
9ee0: 908a16e4 9036ae68 00000000 9036ae68 9036aea8 90004f3e 91c29fa4 00000000
9f00: 9036aee8 00000000 901dd3c4 90025f5a 9038f954 00000000 00000000 900aa82a
9f20: 00000001 00400022 00000000 901819ac 91c29f50 90379b78 91cd9d00 901819b2
9f40: 91c29f50 90379b78 91cd9d00 00000000 900aa82a 91c29f68 00000000 91cd9d00
9f60: 00000000 0000006f 900aa8ba 91c29f90 91cd9d00 90048cf8 00000000 00000000
9f80: 90025f5a 9038f954 00000000 90379aa4 90004e4a 91c29fb4 90014ff0 00000000
9fa0: 00000000 90017688 91c29fc8 90014ff4 90004e80 00000000 00000000 90025f5a
9fc0: 9038f954 00000000 9000039a 91c29fec 90014ff4 00000000 00000000 00000000
9fe0: 90025f5a 90000338 00000000 90025f5a 00000000 00000000 00000000 00000000
Call trace:

Disabling lock debugging due to kernel taint
Kernel panic - not syncing: Attempted to kill init!
Call trace:
[<9001aa48>] dump_stack+0x18/0x20
[<900237b8>] panic+0x34/0xdc
[<90025f94>] do_exit+0x3a/0x412
[<900195d6>] die+0xde/0x114
[<9001bffa>] do_page_fault+0x23a/0x338
[<900160e2>] page_not_present+0x14/0x16

Is this error orginated from a problem with the ram of the flash? Or can someone help me? :D

Edit:
It seems to be the:
"Kernel hacking ---> Kprobes sanity tests"
that failes miserably. Anyone know if that is a bad thing or does it not work on the avr32 branch?

Attachment(s): 

Life's to short for waiting on slow CPU's

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It seems like the message:

Kprobe smoke test passed successfully 

Tells me that the test are complete ( looked in the code ) but the error occurs when the kernel tries to continue loading ?!?

Life's to short for waiting on slow CPU's

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hm, I've never run Kprobes on AVR32 but seeing as support was written I guess someone has!

Looks like the Kprobes test munged the pagetable during its test. I don't know where you'd start debugging this one (pity the stack trace doesn't go back further)..

-S.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Any way to get the stack trace going back further?

Life's to short for waiting on slow CPU's

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Nah, it's going back all the way to the exception entry, the rest of the track is a 'rete' away :-)

-S.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My worry is that this error is somthing simulair to what is happending when I use my board over time. I have a system crash when running networing over ppp0 and usb0 at the same time. After 2-5 hours.

Life's to short for waiting on slow CPU's

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hm, is this over the usb gadget link I've seen you talking about?

I've seen lockups in those kinds of periods with ppp0 over a USB GSM modem due to driver bug causing a race; I've tried to push the changes upstream but the vendor (Sierra) isn't responsive.

-S.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ok.. But this is one local lan connection between a computer and a board over usb, and a connection over a ttySn -> ppp0 (GSM/GPRS) modem to upload information over the internet. This fault mentioned here is during boot test, while the other is after running the system for 2-5 hours.

Life's to short for waiting on slow CPU's

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Can onyone comment on if this could be related? http://www.mail-archive.com/u-bo...

Life's to short for waiting on slow CPU's

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

eaanon01 wrote:
Can onyone comment on if this could be related? http://www.mail-archive.com/u-bo...
If you have multi cycles instructions in front of a branch, yes, then you might be subjected to the branch folding errata.

Hans-Christian

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Nope did not solve my problem :(

Life's to short for waiting on slow CPU's