I have bisected the problem to commit : f96972f2dc6365421cf2366ebd61ee4cf060c8d5 is the first bad commit commit f96972f2dc6365421cf2366ebd61ee4cf060c8d5 Author: Shawn Guo <shawn....@linaro.org> Date: Thu Oct 4 17:12:23 2012 -0700
kernel/sys.c: call disable_nonboot_cpus() in kernel_restart()
As kernel_power_off() calls disable_nonboot_cpus(), we may also want to
have kernel_restart() call disable_nonboot_cpus(). Doing so can help
machines that require boot cpu be the last alive cpu during reboot to
survive with kernel restart.
This fixes one reboot issue seen on imx6q (Cortex-A9 Quad). The machine
requires that the restart routine be run on the primary cpu rather than
secondary ones. Otherwise, the secondary core running the restart
routine will fail to come to online after reboot.
Signed-off-by: Shawn Guo <shawn....@linaro.org>
Cc: <sta...@vger.kernel.org>
Signed-off-by: Andrew Morton <a...@linux-foundation.org>
Signed-off-by: Linus Torvalds <torva...@linux-foundation.org>
:040000 040000 9d52d2bcb08689a18a61799e78437a4bd7431e26
42041136e8a0f12434c06ddca32f6b7826f5d122 M kernel
It seems to have been reported on arch [1] and upstream [2].
Strangely this commit has been backported to 3.6.2 and I can also find
it in linux_3.6.9.orig.tar.xz so, but I don't have any problem with
the 3.6 kernel so it seems to trigger something else in the 3.7 era.
Or bisecting between 3.6 and 3.7 on linux-stable isn't possible ? I've
atached the log just in case I made a mistake.
I'll try to revert this particular patch on 3.7.1-1~experimental.2 and
see what happens.
[1] https://bugs.archlinux.org/task/31938
[2] https://bugzilla.kernel.org/show_bug.cgi?id=49001
--
Nicolas Le Cam
broken_reboot_bisect.log
Description: Binary data
