Kernel crash in boot on p2041rdb / p3041ds (Yocto master)

martinborg · ‎03-18-2016

Hello,

I'm building Yocto on master branch (SDK 1.9, Linux kernel 3.12.37-rt51) and get kernel crashes early in boot on both p2041rdb and p3041ds boards.

Yocto master has recently upgraded to binutils version 2.26, I tried to revert back to binutils 2.25.1 and then the build produced a working image.

Any help or suggestions would be greatly appreciated.

Thanks in advance,

Martin

-------------------------------------------------------------------------------

...

Kernel virtual memory layout:

* 0xfff5f000..0xfffff000 : fixmap

* 0xffc00000..0xffe00000 : highmem PTEs

* 0xffbfb000..0xffc00000 : early ioremap

* 0xf1000000..0xffbfb000 : vmalloc & ioremap

Hierarchical RCU implementation.

RCU debugfs-based tracing is enabled.

RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.

NR_IRQS:512 nr_irqs:512 16

mpic: Setting up MPIC " OpenPIC " version 1.2 at ffe040000, max 4 CPUs

mpic: ISU size: 512, shift: 9, mask: 1ff

mpic: Initializing for 512 sources

clocksource: timebase mult[2aaaaaab] shift[24] registered

Console: colour dummy device 80x25

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 512

mpic: requesting IPIs...

e500 family performance monitor hardware support registered

Oops: Exception in kernel mode, sig: 4 [#1]

Brought up 4 CPUs

SMP NR_CPUS=8 CoreNet Generic

Modules linked in:

CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.12.37-rt51 #1

task: e9093530 ti: e90ba000 task.ti: e90ba000

NIP: c0007ad4 LR: c0007ad4 CTR: c000edcc

REGS: e90bbee0 TRAP: 0700 Not tainted (3.12.37-rt51)

MSR: 00029002 <CE,EE,ME> CR: 22000808 XER: 00000000

GPR00: c0076e08 e90bbf90 e9093530 e90ba000 00000001 00000000 01000000 01000000

GPR08: 020e4000 c000edcc 00000000 00000000 ffffffff 00000000 00000001 9821da22

GPR16: 9273887f 01200c20 88c4f00e 34223e1b 1551f80b 90e0589e e90ba000 00000001

GPR24: c08e6ebc c08e6d36 c08f3cd0 c08f3c5c 00040000 e90ba000 e90ba080 e90ba000

NIP [c0007ad4] arch_cpu_idle+0x24/0x70

LR [c0007ad4] arch_cpu_idle+0x24/0x70

Call Trace:

[e90bbf90] [c00a1338] rcu_idle_enter+0xa8/0xf0 (unreliable)

[e90bbfa0] [c0076e08] cpu_startup_entry+0x118/0x170

[e90bbfd0] [c0011df0] start_secondary+0x240/0x250

[e90bbff0] [c0001d38] __secondary_start+0x30/0x84

Instruction dump:

60000000 60000000 60000000 3d20c08f 812976d0 2f890000 419e0044 9421fff0

7c0802a6 7d2903a6 90010014 4e800421 <7d2000a6> 712a8000 40820008 7c008146

---[ end trace 31fd0ba7d8756001 ]---

Oops: Exception in kernel mode, sig: 4 [#2]

SMP NR_CPUS=8 CoreNet Generic

Modules linked in:

CPU: 3 PID: 0 Comm: swapper/3 Tainted: G D 3.12.37-rt51 #1

task: e9096a70 ti: e90be000 task.ti: e90be000

NIP: c0007ad4 LR: c0007ad4 CTR: c000edcc

REGS: e90bfee0 TRAP: 0700 Tainted: G D (3.12.37-rt51)

MSR: 00029002 <CE,EE,ME> CR: 22000808 XER: 00000000

GPR00: c0076e08 e90bff90 e9096a70 e90be000 00000001 00000000 01000000 01000000

GPR08: 020f4000 c000edcc 00000000 00000000 ffffffff 00000000 00000001 05b05c00

GPR16: c2231584 864a2f00 40115400 b41a80e0 911ad050 00a00004 e90be000 00000001

GPR24: c08e6ebc c08e6d36 c08f3cd0 c08f3c5c 00040000 e90be000 e90be080 e90be000

NIP [c0007ad4] arch_cpu_idle+0x24/0x70

LR [c0007ad4] arch_cpu_idle+0x24/0x70

Call Trace:

[e90bff90] [c00a1338] rcu_idle_enter+0xa8/0xf0 (unreliable)

[e90bffa0] [c0076e08] cpu_startup_entry+0x118/0x170

[e90bffd0] [c0011df0] start_secondary+0x240/0x250

[e90bfff0] [c0001d38] __secondary_start+0x30/0x84

Instruction dump:

60000000 60000000 60000000 3d20c08f 812976d0 2f890000 419e0044 9421fff0

7c0802a6 7d2903a6 90010014 4e800421 <7d2000a6> 712a8000 40820008 7c008146

---[ end trace 31fd0ba7d8756002 ]---

Oops: Exception in kernel mode, sig: 4 [#3]

SMP NR_CPUS=8 CoreNet Generic

Modules linked in:

CPU: 2 PID: 0 Comm: swapper/2 Tainted: G D 3.12.37-rt51 #1

task: e9093030 ti: e90bc000 task.ti: e90bc000

NIP: c0007ad4 LR: c0007ad4 CTR: c000edcc

REGS: e90bdee0 TRAP: 0700 Tainted: G D (3.12.37-rt51)

MSR: 00029002 <CE,EE,ME> CR: 22000808 XER: 00000000

GPR00: c0076e08 e90bdf90 e9093030 e90bc000 00000001 00000000 01000000 01000000

GPR08: 020ec000 c000edcc 00000000 00000000 ffffffff 00000000 00000001 60016001

GPR16: 101e8126 2226c008 0408024a 0734ced7 60408008 82098231 e90bc000 00000001

GPR24: c08e6ebc c08e6d36 c08f3cd0 c08f3c5c 00040000 e90bc000 e90bc080 e90bc000

NIP [c0007ad4] arch_cpu_idle+0x24/0x70

LR [c0007ad4] arch_cpu_idle+0x24/0x70

Call Trace:

[e90bdf90] [c00a1338] rcu_idle_enter+0xa8/0xf0 (unreliable)

[e90bdfa0] [c0076e08] cpu_startup_entry+0x118/0x170

[e90bdfd0] [c0011df0] start_secondary+0x240/0x250

[e90bdff0] [c0001d38] __secondary_start+0x30/0x84

Instruction dump:

60000000 60000000 60000000 3d20c08f 812976d0 2f890000 419e0044 9421fff0

7c0802a6 7d2903a6 90010014 4e800421 <7d2000a6> 712a8000 40820008 7c008146

---[ end trace 31fd0ba7d8756003 ]---

Kernel panic - not syncing: Attempted to kill the idle task!

Rebooting in 180 seconds..

yipingwang · ‎03-22-2016

Hello Martin,

Linux SDK 1.9 integrates binutils 2.25, would you please let me know why you don't want to use SDK 1.9 directly?

Why do you want to use binutils 2.25.1 instead of 2.25?

Would you please also attach Linux Kernel uImage file? I will do more investigation on my target.

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

martinborg · ‎03-23-2016

Hi,

I am using Yocto (poky and meta-fsl-ppc layer) to build and not the SDK directly. The version of binutils used in Yocto has recently been upgraded to 2.26 on master branch (previously it was 2.25.1):

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/recipes-devtools/binutils

Attaching uImage files for p2041rdb and p3041ds.

Best Regards,

Martin

yipingwang · ‎04-06-2016

Hello Martin,

I also can reproduce your problem when update toolchain to binutils 2.26, I have tried to apply patches to binutils and Linux Kernel, but still cannot solve this problem.

I confirmed with Linux SDK production team, they are not planning to use binutils 2.26, they will update to binutils 2.27 directly.

So I recommend you to continue to use binutils 2.25 or update to binutils 2.27.

Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

martinborg · ‎04-06-2016

Hi Yiping,

Thank you for investigating. I have not found any solution to this problem either (for now, we have reverted back to binutils 2.25.1 as a workaround).

I have sent a message to the Yocto meta-freescale mailing list as well about this problem. The next Yocto release (2.1) will use binutils 2.26.

Best Regards,

Martin

matevzlangus · ‎11-18-2017

Hi,

did you have any progress. We are using kernel 4.9.49 and binutils 2.28.1 and exactly the same error occurs.

regards,

Matevz