why my second cpu is killed by first cpu [Cubieboard2]

[宋晨川]

I have buy a cubieboard 2 and compile a android img for it but when i check the dmesg i found something is wrong:

<4>[   80.565110] CPU1: Booted secondary processor

<6>[   80.565158] Calibrating delay loop (skipped) already calibrated this CPU

<4>[   84.734216] [fantasy] wrn cpu need plugout, cpus_load_max:29<30 && cpus_rq_max: 159<200

<5>[   84.744456] CPU1: shutdown

<6>[   84.747496] [hotplug]: cpu(0) try to kill cpu(1)

<6>[   84.753664] [hotplug]: cpu1 is killed!

<4>[   86.474248] [fantasy] wrn cpu need plugin, freq: 91200000>=72960000 && rq: 584>200

<4>[   86.488071] [fantasy] wrn cpu up:1

<4>[   86.523490] CPU1: Booted secondary processor

<6>[   86.523538] Calibrating delay loop (skipped) already calibrated this CPU

<4>[  114.464234] [fantasy] wrn cpu need plugout, cpus_load_max:42<30 && cpus_rq_max: 98<200

<5>[  114.484339] CPU1: shutdown

<6>[  114.487375] [hotplug]: cpu(0) try to kill cpu(1)

<6>[  114.493524] [hotplug]: cpu1 is killed!

should i set up something to fix this?

now i am  only using  one cpu core to deal with the android 

any ideas for this issue? many tks for help

[benn]

To save energy, the cpu freq is scaling according to the system load.
and the cpu core can be also enable/disable at run time.


>
> --
> You received this message because you are subscribed to the Google
> Groups "Cubieboard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to cubieboard+...@googlegroups.com.
> Visit this group at http://groups.google.com/group/cubieboard.
> For more options, visit https://groups.google.com/groups/opt_out.

[SongChenchuan]

how could i force all cpu cores to be enable

To unsubscribe from this group and stop receiving emails from it, send an email to cubieboard+unsubscribe@googlegroups.com.

Visit this group at http://groups.google.com/group/cubieboard.
For more options, visit https://groups.google.com/groups/opt_out.

--
Best Regards

[tkg]

You need to set a governor that is not using hotplug.

If you have a root console try for instance:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

this should show you the governor used for cpu0

You can get a list of possible governors:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

and you can set a specific governor from the list (say for example performance):

echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor   

Please note that the governor setting might be reset on reboot and you might need to write a small script to set the intended governor on boot.

Alternatively you can also use the SetCPU android app (you still need root).