Kernel errors at very early stage

Kernel errors at very early stage

[Dunda, Matthias]

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

Hi all-

we've built a custom board with a FSL MPC8568EMDS CPU.

U-Boot works so far - at least it is able to load a Linux kernel and a
flattened device tree via network and launch the kernel.

I get no output on the serial console from the kernel, so my only chance is
to read out the __log_buf while in memory with my Abatron BDI 3000 debugger.

The thing is, I cannot break into the code really, because it never stops
reliable at my break points... :-(

Can anyone of you see a usual suspect in the attached log?

Is there something wrong with the timing, maybe? Maybe a hardware issue?

How can I check this?

Cheers
Matthias



[-- Attachment #2: kernel-log.008 --]
[-- Type: application/octet-stream, Size: 3527 bytes --]

<4>Invalid tag 0 scanning flattened device tree !
<4>Invalid tag 0 scanning flattened device tree !
<4>Invalid tag 0 scanning flattened device tree !
<4>PHYSICAL_START=0x00000000 
<4>klimit=0xc0442000 
<4>__pa(klimit)=0x00442000 
<4>First lmb_reserved passed!
<0>------------[ cut here ]------------
<2>Kernel BUG at c039b3ec [verbose debug info unavailable]
<4>Oops: Exception in kernel mode, sig: 5 [#1]
<4>PREEMPT 
<4>Modules linked in:
<4>NIP: c039b3ec LR: c038a308 CTR: c02e14ac
<4>REGS: c03ddef0 TRAP: 0700   Not tainted  (2.6.29.6-rt23-svn20)
<4>MSR: 00021000 <ME,CE>  CR: 28044024  XER: 00000000
<4>TASK = c03b1508[0] 'swapper' THREAD: c03dc000
<6>GPR00: 00000001 c03ddfa0 c03b1508 00000000 00400000 00000000 00400000 00000000 
<6>GPR08: 00000000 c0400000 00000104 c03ddfb0 28044022 00000000 7ff78e00 00000000 
<6>GPR16: 7ff494ec 7ff6d648 00000000 00000000 00000000 00000000 00000000 00000000 
<6>GPR24: 00000000 00000000 c03e0000 00000000 00400000 c03e0000 c0400000 c03ddfa0 
<4>NIP [c039b3ec] lmb_reserve+0x30/0x5c
<4>LR [c038a308] early_init_devtree+0x104/0x2e8
<4>Call Trace:
<4>[c03ddfa0] [000000e6] 0xe6 (unreliable)
<4>[c03ddfb0] [c038a308] early_init_devtree+0x104/0x2e8
<4>[c03ddfd0] [c038b1dc] machine_init+0x24/0x64
<4>[c03ddff0] [c000039c] skpinv+0x2c4/0x304
<4>Instruction dump:
<4>9421fff0 7c0802a6 93e1000c 90010014 7c3f0b78 7ca03379 7cc83378 7ca72b78 
<4>7c862378 7c651b78 7c000026 54001ffe <0f000000> 3c60c043 38635698 38630830 
<4>---[ end trace 31fd0ba7d8756001 ]---
<0>Kernel panic - not syncing: Attempted to kill the idle task!
<1>Unable to handle kernel paging request for data at address 0x00000010
<1>Faulting instruction address: 0xc0068824
<4>Oops: Kernel access of bad area, sig: 11 [#2]
<4>PREEMPT 
<4>Modules linked in:
<4>NIP: c0068824 LR: c006d9e8 CTR: c00687c0
<4>REGS: c03ddad0 TRAP: 0300   Tainted: G      D     (2.6.29.6-rt23-svn20)
<4>MSR: 00021000 <ME,CE>  CR: 28044024  XER: 00000000
<4>DEAR: 00000010, ESR: 00000000
<4>TASK = c03b1508[0] 'swapper' THREAD: c03dc000
<6>GPR00: 00000000 c03ddb80 c03b1508 c03ddbd8 00000000 00000000 00000000 00000000 
<6>GPR08: 59bbe120 00000000 00000000 00000000 00000000 00000000 7ff78e00 00000000 
<6>GPR16: 7ff494ec c03ddbd8 c03e31a0 c03e3190 c03e0000 c03e0000 00021000 c03ddbd8 
<6>GPR24: c03e0000 c03e0000 c03ddef0 00000000 00000000 c03b24c8 00000000 c03ddb80 
<4>NIP [c0068824] ktime_get+0x70/0x15c
<4>LR [c006d9e8] tick_nohz_stop_sched_tick+0x40/0x414
<4>Call Trace:
<4>[c03ddb80] [c033282d] 0xc033282d (unreliable)
<4>[c03ddbd0] [c006d9e8] tick_nohz_stop_sched_tick+0x40/0x414
<4>[c03ddc20] [c0048000] irq_exit+0x80/0xac
<4>[c03ddc30] [c000d760] timer_interrupt+0xb8/0x110
<4>[c03ddc50] [c0011c88] ret_from_except+0x0/0x18
<4>[c03ddd10] [c0041148] panic+0xb8/0x178
<4>[c03ddd60] [c004571c] do_exit+0x63c/0x6f8
<4>[c03ddda0] [c000e65c] die+0x1c0/0x1fc
<4>[c03dddd0] [c000ea08] _exception+0x168/0x194
<4>[c03ddec0] [c000efb4] program_check_exception+0x94/0x630
<4>[c03ddee0] [c0011c3c] ret_from_except_full+0x0/0x4c
<4>[c03ddfa0] [000000e6] 0xe6
<4>[c03ddfb0] [c038a308] early_init_devtree+0x104/0x2e8
<4>[c03ddfd0] [c038b1dc] machine_init+0x24/0x64
<4>[c03ddff0] [c000039c] skpinv+0x2c4/0x304
<4>Instruction dump:
<4>3f20c03e 3e80c03e 3ea0c03e 83d93180 3a5431a0 3a753190 3f00c03e 73db0001 
<4>408200bc 813831a8 815431a0 81753190 <81290010> 80130004 83920004 7f4a5a14 
<4>---[ end trace 31fd0ba7d8756002 ]---
<0>Kernel panic - not syncing: Attempted to kill the idle task!

Re: Kernel errors at very early stage

[Xianghua Xiao]

On Wed, May 5, 2010 at 3:27 AM, Dunda, Matthias
<Matthias.Dunda@de.thalesgroup.com> wrote:
> Hi all-
>
> we've built a custom board with a FSL MPC8568EMDS CPU.
>
> U-Boot works so far - at least it is able to load a Linux kernel and a
> flattened device tree via network and launch the kernel.
>
> I get no output on the serial console from the kernel, so my only chance is
> to read out the __log_buf while in memory with my Abatron BDI 3000 debugger.
>
> The thing is, I cannot break into the code really, because it never stops
> reliable at my break points... :-(
>
> Can anyone of you see a usual suspect in the attached log?
>
> Is there something wrong with the timing, maybe? Maybe a hardware issue?
>
> How can I check this?
>
> Cheers
> Matthias
>
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
from the log it seems your device tree has issue, also you may want to
turn on verbose debug, turn off preempt, turn off no_hz and see how
far it can go.

if only log_buf is available to get some output, you may want to
increase the buffer size to see more

xianghua