Ubuntu: halt command throws error messages continuously and fails to shut down board
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
IglooCommunity |
New
|
Low
|
Unassigned |
Bug Description
Description:
-------------
halt command throws error messages continuously and fails to shut down board
tescase reference: https:/
Reproducible:
---------------
yes , 5/5
Steps to reproduce:
-------
Type halt on serial console after device is up and running.
Logs:
------
serial logs attached.
Snippet of logs below:
#halt
root@linaro-
Broadcast message from root@linaro-
(/dev/ttyAMA2) at 13:49 ...
The system is going down for halt NOW!
root@linaro-
[ 44.630615] init: Failed to create pty - disabling logging for job
Checking for running unattended-
[ 44.645660] init: Failed to create pty - disabling logging for job
[ 47.947418] Bluetooth: BTCG2900 NULL supplied for driver_data
nm-dispatcher.
...done.
[ 47.971313] Bluetooth: BTCG2900 NULL supplied for info
nm-dispatcher.
[ 48.493194]
[ 48.493225] [4f9aa3ff:320f5024] CG2900_FM_Driver: cg2900_
[ 48.504425]
[ 48.504455] [4f9aa3ff:32bb245d] CG2900_FM_Driver: cg2900_fm_deinit: Already de-Initialized
[ 50.417236] System halted.
[ 50.420043] BUG: scheduling while atomic48>] (schedule_
[ 50.470581] bad: scheduling from the idle thread!
[ 50.471191] BUG: scheduling while atomic: swapper/
Changed in igloocommunity: | |
milestone: | none → 2012.06 |
Changed in igloocommunity: | |
importance: | Undecided → Medium |
Changed in igloocommunity: | |
milestone: | 2012.06 → 2012.07 |
Changed in igloocommunity: | |
milestone: | 2012.07 → 2012.08 |
Changed in igloocommunity: | |
importance: | Medium → Low |
milestone: | 2012.08 → none |
Observed on hardware pack:
http:// snapshots. linaro. org/precise/ hwpacks/ lt-snowball- x11-base/ 65/hwpack_ linaro- lt-snowball- x11-base_ 20120514- 65_armhf_ supported. tar.gz
with ubuntu image:
http:// snapshots. linaro. org/precise/ images/ ubuntu- desktop/ 158/linaro- precise- ubuntu- desktop- 20120515- 158.tar. gz
The board even be rebooted after hit lots of error information, refer to attachment to get the detailed log output.