reboot -p not work on imx6q,android-kitkat

cancel
Showing results for 
Search instead for 
Did you mean: 

reboot -p not work on imx6q,android-kitkat

498 Views
conteczxy
Contributor III

Hi,

I tried with command

root@sabresd_6dq:/ #  reboot

it reboot the system successfully, and the console shows log like this,

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

SysRq : Emergency Remount R/O

EXT4-fs (mmcblk0p5): re-mounted. Opts: (null)

EXT4-fs (mmcblk0p4): re-mounted. Opts: (null)

EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)

Emergency Remount complete

imx2-wdt imx2-wdt.0: Device shutdown: Expect reboot!

Restarting system with command ''.

WDOG ]

But, I want to shutdown the system through command reboot -p, then I type on the console,

root@sabresd_6dq:/ #  reboot -p

It is not shutdown, and something seems error,  the console log is like this,

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

reboot -p

SysRq : Emergency Remount R/O

EXT4-fs (mmcblk0p5): re-mounted. Opts: (null)

EXT4-fs (mmcblk0p4): re-mounted. Opts: (null)

EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)

Emergency Remount complete

imx2-wdt imx2-wdt.0: Device shutdown: Expect reboot!

Disabling non-boot CPUs ...

CPU1: shutdown

CPU2: shutdown

CPU3: shutdown

Power down.

note: init[1] exited with preempt_count 1

BUG: scheduling while atomic: init/1/0x00000002

Modules linked in:

[<c0056044>] (unwind_backtrace+0x0/0x138) from [<c06e63b4>] (__schedule+0x820/0x958)

[<c06e63b4>] (__schedule+0x820/0x958) from [<c06e6b7c>] (schedule_timeout+0x1c8/0x330)

[<c06e6b7c>] (schedule_timeout+0x1c8/0x330) from [<c06e591c>] (wait_for_common+0xac/0x150)

[<c06e591c>] (wait_for_common+0xac/0x150) from [<c00dd350>] (synchronize_rcu+0x40/0x54)

[<c00dd350>] (synchronize_rcu+0x40/0x54) from [<c0406474>] (input_close_device+0x60/0x6c)

[<c0406474>] (input_close_device+0x60/0x6c) from [<c040f1d8>] (keychord_disconnect+0xc/0x20)

[<c040f1d8>] (keychord_disconnect+0xc/0x20) from [<c0406784>] (input_unregister_handler+0x34/0xe4)

[<c0406784>] (input_unregister_handler+0x34/0xe4) from [<c040f118>] (keychord_release+0x1c/0x2c)

[<c040f118>] (keychord_release+0x1c/0x2c) from [<c0136bd8>] (fput+0xb8/0x1ec)

[<c0136bd8>] (fput+0xb8/0x1ec) from [<c013391c>] (filp_close+0x68/0x80)

[<c013391c>] (filp_close+0x68/0x80) from [<c00920b0>] (put_files_struct+0xd8/0xfc)

[<c00920b0>] (put_files_struct+0xd8/0xfc) from [<c00922a8>] (do_exit+0x158/0x764)

[<c00922a8>] (do_exit+0x158/0x764) from [<c00a38d4>] (sys_reboot+0x134/0x1c4)

[<c00a38d4>] (sys_reboot+0x134/0x1c4) from [<c004e900>] (ret_fast_syscall+0x0/0x30)

BUG: scheduling while atomic: init/1/0x00000002

Modules linked in:

[<c0056044>] (unwind_backtrace+0x0/0x138) from [<c06e63b4>] (__schedule+0x820/0x958)

[<c06e63b4>] (__schedule+0x820/0x958) from [<c06e6b7c>] (schedule_timeout+0x1c8/0x330)

[<c06e6b7c>] (schedule_timeout+0x1c8/0x330) from [<c06e591c>] (wait_for_common+0xac/0x150)

[<c06e591c>] (wait_for_common+0xac/0x150) from [<c00dd350>] (synchronize_rcu+0x40/0x54)

[<c00dd350>] (synchronize_rcu+0x40/0x54) from [<c040f1e0>] (keychord_disconnect+0x14/0x20)

[<c040f1e0>] (keychord_disconnect+0x14/0x20) from [<c0406784>] (input_unregister_handler+0x34/0xe4)

[<c0406784>] (input_unregister_handler+0x34/0xe4) from [<c040f118>] (keychord_release+0x1c/0x2c)

[<c040f118>] (keychord_release+0x1c/0x2c) from [<c0136bd8>] (fput+0xb8/0x1ec)

[<c0136bd8>] (fput+0xb8/0x1ec) from [<c013391c>] (filp_close+0x68/0x80)

[<c013391c>] (filp_close+0x68/0x80) from [<c00920b0>] (put_files_struct+0xd8/0xfc)

[<c00920b0>] (put_files_struct+0xd8/0xfc) from [<c00922a8>] (do_exit+0x158/0x764)

[<c00922a8>] (do_exit+0x158/0x764) from [<c00a38d4>] (sys_reboot+0x134/0x1c4)

[<c00a38d4>] (sys_reboot+0x134/0x1c4) from [<c004e900>] (ret_fast_syscall+0x0/0x30)

Kernel panic - not syncing: Attempted to kill init!

[<c0056044>] (unwind_backtrace+0x0/0x138) from [<c06e13a8>] (panic+0x74/0x194)

[<c06e13a8>] (panic+0x74/0x194) from [<c009288c>] (do_exit+0x73c/0x764)

[<c009288c>] (do_exit+0x73c/0x764) from [<c00a38d4>] (sys_reboot+0x134/0x1c4)

[<c00a38d4>] (sys_reboot+0x134/0x1c4) from [<c004e900>] (ret_fast_syscall+0x0/0x30)

Not sure where is the problem, any suggestion is appreciated.

Thanks.

Labels (2)
Tags (3)
0 Kudos
1 Reply

70 Views
igorpadykov
NXP TechSupport
NXP TechSupport

Hi Xiyuan

for reliable reboot both processor and pmic should be reset,

while at soft reboot pmic is not reset and its voltage may be lower

(due to cpufreq driver) than necessary for rebooting processor.

Best regards

igor

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

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

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

0 Kudos