AnsweredAssumed Answered

CPU failed to boot : Error with 3.14.28 kernel

Question asked by sharvari harisangam on Jul 26, 2015
Latest reply on Jul 27, 2015 by sharvari harisangam

Hello all,

  I am facing issue with linux-imx 3.14.28 kernel. I have a imx6solo sabre auto based board.

When I flash the kernel generated from Yocto (meta-fsl-arm), it gives the following error

 

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

Virtual kernel memory layout:

  vector : 0xffff0000 - 0xffff1000 ( 4 kB)

  fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

  vmalloc : 0xa0800000 - 0xff000000 (1512 MB)

  lowmem : 0x80000000 - 0xa0000000 ( 512 MB)

  pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)

  modules : 0x7f000000 - 0x7fe00000 ( 14 MB)

  .text : 0x80008000 - 0x806d54ac (6966 kB)

  .init : 0x806d6000 - 0x80a6a100 (3665 kB)

  .data : 0x80a6c000 - 0x80aaa1e0 ( 249 kB)

  .bss : 0x80aaa1ec - 0x80b0cc20 ( 395 kB)

*SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1*

Preemptible hierarchical RCU implementation.

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

RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2

NR_IRQS:16 nr_irqs:16 16

L310 cache controller enabled

l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32050000, Cache size: 512 kB

failed to set parent of clk gpu2d_core_sel to pll2_pfd1_594m: -22

Switching to timer-based delay loop

sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every

1431655765682ns

Console: colour dummy device 80x30

Calibrating delay loop (skipped) preset value.. 1581.05 BogoMIPS

(lpj=7905280)

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)

Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)

CPU: Testing write buffer coherency: ok

CPU0: thread -1, cpu 0, socket 0, mpidr 80000000

Setting up static identity map for 0x10516040 - 0x10516098

*CPU1: failed to boot: -38*

Brought up 1 CPUs

SMP: Total of 1 processors activated.

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

 

My board is solo, but the kernel debug messages show CPUs =2.

Also it gives error as CPU1:failed to boot. Do i need to change any

configurations in Yocto or kernel config to make CPUS=1?

 

 

-Thanks

Sharvari

Outcomes