shutdown does not switch off power

Bug #483007 reported by Philip Martin on 2009-11-15
30
This bug affects 7 people
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: upstart

I have 9.10 (64bit) installed on a new Lenovo Thinkpad SL500. When I choose shutdown or reboot from the GUI it appears to shut most things down, like the GUI, but doesn't switch off the power or reboot. I get left with a blinking cursor on the console.

If I stop gdm and run halt from the command line I get this:

$ halt
The system is going down for halt NOW!
* Using Makefile-style concurrent boot in runlevel 0
init: rsyslog-kmsg main process (858) killed by TERM signal
init: hal main process (945) teminated with status 1
init: avahi-daemon main process (943) terminated with status 255
modem-manager: Caught signal 15, shutting down...
init: Disconnected from system bus

and then it just sits there until I press and hold the power button.

If I run "halt -f -p" then it doesn't do the normal shutdown process but it does switch off the power. I've tried putting an explicit "halt -f -p" at the start of /etc/init.d/halt but that doesn't help. /etc/default/halt contains the line "HALT=poweroff".

Reboot has the same problem as shutdown, and again "reboot -f" does reboot but once again doesn't run the shutdown scripts.

shutdown is still handled by sysvinit, it sounds like a service isn't going down

how long have you waited at that point?

affects: upstart (Ubuntu) → sysvinit (Ubuntu)

Scott James Remnant <email address hidden> writes:

> shutdown is still handled by sysvinit, it sounds like a service isn't
> going down
>
> how long have you waited at that point?

As much as ten minutes. Even if I boot in recovery mode and drop to a
root shell it still doesn't poweroff when I run shutdown. I've even
tried stopping all the services manually before running shutdown.

--
Philip

Philip Martin <email address hidden> writes:

> Scott James Remnant <email address hidden> writes:
>
>> shutdown is still handled by sysvinit, it sounds like a service isn't
>> going down
>>
>> how long have you waited at that point?
>
> As much as ten minutes. Even if I boot in recovery mode and drop to a
> root shell it still doesn't poweroff when I run shutdown. I've even
> tried stopping all the services manually before running shutdown.

More info: alt-sysrq-l shows the cpu in acpi_idle_enter_bm. If I boot
with acpi=off it's atomic_notifier_call_chain from cpu_idle.

--
Philip

More info: I booted in recovery mode with the --debug option and
dropped into a root shell. When I shutdown the last few messages are:

init: Disconnected from system bus
init: job_process_handler: Ignored event 2 (15) for process 1146
init: job_process_handler: Ignored event 1 (0) for process 953
init: dbus main process (953) exited normally
init: dbus state changed from killed to post-stop
init: dbus state changed from post-stop to waiting
init: event new: Pending stopped event
init: job_change_state: Destroyed inactive instance dbus
init: event_finished: Finished runlevel event
init: Handling stopped event
init: event_finished: Finished stopped event

--
Philip

If I run 'sudo /etc/rc0.d/S90halt stop' then that also switches off
the power. So it appears that shutdown doesn't invoke the scripts. I
have noticed that other init scripts not being run: I have the
cpufrequtils package installed and its init script doesn't get run
when I boot (invoking '/etc/init.d/cpufrequtils start' works). So the
problem is that whatever is supposed to trigger the scripts (upstart?)
doesn't seem to be doing it. How do I debug this? As far as I am
aware I haven't made any local modifications to these packages; I'm
using the default install configuration.

--
Philip

Setting "CONCURRENCY=none" in /etc/default/rcS works. I can now run
"sudo halt" and the machine powers-off. How do I go about determining
what is wrong with CONCURRENCY=makefile?

--
Philip

On Fri, 2009-11-20 at 21:47 +0000, Philip Martin wrote:

> Setting "CONCURRENCY=none" in /etc/default/rcS works. I can now run
> "sudo halt" and the machine powers-off. How do I go about determining
> what is wrong with CONCURRENCY=makefile?
>
"none" is basically all we support in Ubuntu

Scott
--
Scott James Remnant
<email address hidden>

Scott James Remnant <email address hidden> writes:

> On Fri, 2009-11-20 at 21:47 +0000, Philip Martin wrote:
>
>> Setting "CONCURRENCY=none" in /etc/default/rcS works. I can now run
>> "sudo halt" and the machine powers-off. How do I go about determining
>> what is wrong with CONCURRENCY=makefile?
>>
> "none" is basically all we support in Ubuntu

I didn't set CONCURRENCY=makefile, the standard install does that.

--
Philip

On Mon, 2009-11-23 at 16:13 +0000, Philip Martin wrote:

> Scott James Remnant <email address hidden> writes:
>
> > On Fri, 2009-11-20 at 21:47 +0000, Philip Martin wrote:
> >
> >> Setting "CONCURRENCY=none" in /etc/default/rcS works. I can now run
> >> "sudo halt" and the machine powers-off. How do I go about determining
> >> what is wrong with CONCURRENCY=makefile?
> >>
> > "none" is basically all we support in Ubuntu
>
> I didn't set CONCURRENCY=makefile, the standard install does that.
>
Err, it damned well shouldn't.

Only Debian has it set to that value.

Scott
--
Scott James Remnant
<email address hidden>

Scott James Remnant <email address hidden> writes:

> On Mon, 2009-11-23 at 16:13 +0000, Philip Martin wrote:
>>
>> I didn't set CONCURRENCY=makefile, the standard install does that.
>>
> Err, it damned well shouldn't.
>
> Only Debian has it set to that value.

Hmm, I don't remember changing it but I suppose I must have done. I
guess I read /usr/share/doc/insserv/README.Debian and didn't realise
that CONCURRENCY=makefile is a Debian only value. Perhaps the
documentation could state explicitly that it's not supported on
Ubuntu.

--
Philip

description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sysvinit (Ubuntu):
status: New → Confirmed
Sergey Naumov (sknaumov) wrote :

I have the same issue with Xubuntu 12.10. It does not poweroff system if halt command is used. It happens both on AMD Athlon II x2 255 machine with ASUS M4A78LT-M LE motherboard and on virtualbox 4.2.4 virtual machine.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers