[meta-freescale] MPC8641D SMP "Processor 1 is stuck"

Chris Enrique microdevel at googlemail.com
Wed Aug 13 03:17:09 PDT 2014


Unfortunately copy-paste messed up the kernel log a bit. sorry for that but
the important part is here:

mpic: Setting up MPIC " MPIC     " version 1.2 at fef40000, max 2 CPUs
mpic: ISU size: 256, shift: 8, mask: ff
mpic: Initializing for 256 sources
clocksource: timebase mult[1e00000] shift[22] registered
Console: colour dummy device 80x25
Mount-cache hash table entries: 512
smp_prepare_cpus
mpic: requesting IPIs ...
smp: kicking cpu 1
Processor 1 is stuck.
Brought up 1 CPUs


2014-08-12 16:23 GMT+02:00 Chris Enrique <microdevel at googlemail.com>:

> Hello,
>
> i am currently working on a GE PPC9A board which has a MPC8641D processor.
>
> i created a bsp for this board and yocto generates a fully working 3.14
> kernel and rootfs as well as devicetree.
>
> the only thing which is causing problems is SMP. i included the following
> kernel options:
>
> CONFIG_SMP=y
> CONFIG_SCHED_SMT=y
> CONFIG_NR_CPUS=64
>
> Unfortunately, only one CPU is brought up during boot:
>
> ...
> PID hash table entries: 4096 (order: 2, 16384 bytes)
> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Sorting __ex_table...
> Memory: 2066916K/2097152K available (4312K kernel code, 188K rwdata, 952K
> rodata, 200K init, 131K bss, 30236K reserved, 1310716K highmem)
> Kernel virtual memory layout:
>   * 0xffbdf000..0xfffff000  : fixmap
>   * 0xff400000..0xff800000  : highmem PTEs
>   * 0xff3dd000..0xff400000  : early ioremap
>   * 0xf1000000..0xff3dd000  : vmalloc & ioremap
> Preemptible hierarchical RCU implementation.
>     Dump stacks of tasks blocking RCU-preempt GP.
>     RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2.
> RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
> NR_IRQS:512 nr_irqs:512 16
> mpic: Setting up MPIC " MPIC     " version 1.2 at fef40000, max 2 CPUs
> mpic: ISU size: 256, shift: 8, mask: ff
> mpic: Initializing for 256 sources
> clocksource: timebase mult[7800001] shift[24] registered
> Console: colour dummy device 80x25
> pid_max: default: 32768 minimum: 301
> Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
> mpic: requesting IPIs...
> ProcePID hash table entries: 4096 (order: 12, 16384 bytes)
> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> Memory: 2044396k/2097152k available (4464k kernel code, 51632k reserved,
> 148k data, 145k bss, 196k init)
> Kernel virtual memory layout:
>   * 0xfffe0000..0xfffff000  : fixmap
>   * 0xff800000..0xffc00000  : highmem PTEs
>   * 0xff3db000..0xff800000  : early ioremap
>   * 0xf1000000..0xff3db000  : vmalloc & ioremap
> NR_IRQS:512
> mpic: Setting up MPIC " MPIC     " version 1.2 at fef40000, max 2 CPUs
> mpic: ISU size: 256, shift: 8, mask: ff
> mpic: Initializing for 256 sources
> clocksource: timebase mult[1e00000] shift[22] registered
> Console: colour dummy device 80x25
> Mount-cache hash table entries: 512
> smp_prepare_cpus
> mpic: requesting IPIs ...
> smp: kicking cpu 1
> Processor 1 is stuck.
> Brought up 1 CPUs
> NET: Registered protocol family 16
> ...
>
> GE had also released a kernel for this board (2009 2.6 kernel), SMP seems
> to fail there as well:
>
> ...
> Kernel virtual memory layout:
>   * 0xfffe0000..0xfffff000  : fixmap
>   * 0xff800000..0xffc00000  : highmem PTEs
>   * 0xff3db000..0xff800000  : early ioremap
>   * 0xf1000000..0xff3db000  : vmalloc & ioremap
> NR_IRQS:512
> mpic: Setting up MPIC " MPIC     " version 1.2 at fef40000, max 2 CPUs
> mpic: ISU size: 256, shift: 8, mask: ff
> mpic: Initializing for 256 sources
> clocksource: timebase mult[1e00000] shift[22] registered
> Console: colour dummy device 80x25
> Mount-cache hash table entries: 512
> smp_prepare_cpus
> mpic: requesting IPIs ...
> smp: kicking cpu 1
> Processor 1 is stuck.
> Brought up 1 CPUs
> ...
>
> Does anybody have an idea what might cause this problem?
>
> Kind regards,
> Chris
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20140813/6ec38065/attachment.html>


More information about the meta-freescale mailing list