Ubuntu doesn't halt or reboot machine

[Eric Munson]

I have two machines: one desktop with an Asus P6X58D Premium motherboard and a Lenovo T61 laptop that both show this problem and another desktop with an Asus Sabertooth X58 motherboard that does not. When I select shutdown or reboot from the logout menu (or when I run shutdown -h now or reboot from the terminal) the system gets all the way to the power off step and stops. When shutting down I hear the hard disks spin down as they normally would but it the machine stays live. I have tried adding acpi=force to my GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and running update-grub but this does not help. I do not think this is a hardware problem because windows can reboot and shutdown both machines.

[Eric Munson (emunson)]

Is there any more information I can provide for this bug?

[Ben Howard (darkmuggle-deactivatedaccount)]

I can confirm this behavior on 11.04 for a Thinkpad W520 as well.

[Ben Howard (darkmuggle-deactivatedaccount)]

Using command line arg of "pcie_aspm=off" fixes this for me.

[Eric Munson (emunson)]

This did not help my desktop, I will try my T61 later today.

[Eric Munson (emunson)]

This did not help my T61 either, both machines are still unable to reboot or power off.

[EliCoten (launchpad-elicoten)]

I've noticed something similar since installing Natty with 2.6.38 kernel. If I use the 2.6.35 kernel, all works fine (mostly). (It's probably unrelated to this bug, but on my system the X server seems to hang while resuming from standby)

[Eric Munson (emunson)]

Unfortunately, I cannot run that old of a kernel and have X start. I tried back to .37 (the oldest that will start X without hanging the machine) and it still showed the problem. I will try .35 on the T61 and see if it helps.

[Ben Howard (darkmuggle-deactivatedaccount)]

This problem appears to have been resolved with the 2.6.38-10-generic kernel update for me.

[Eric Munson (emunson)]

It didn't fix anything for me, I don't think my problem is related to the pcie power management issue.

I am happy to do anything that needs to be done to help diagnose the issue, but I need some direction there. It is incredibly frustrating that I have had this bug open for more than a month and nothing has moved. What do I need to do to get some more eyes on this issue?

[Launchpad Janitor (janitor)]

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

[Eliah Kagan (degeneracypressure)]

This bug has a task open for upstream Linux. Is there a task open on the actual upstream tracker (http://bugzilla.kernel.org)? If so, then this bug should be tracking that (expand the Linux task and put the bugzilla.kernel.org URL in under Remote Watch). If not, then either the bug should be reported upstream and then linked here, or (if there is not reason to think it is an upstream problem affecting systems other than Debian/Ubuntu), then the upstream task should be marked Invalid until which time as contrary information arises.

[Eric Munson (emunson)]

After an upgrade to Oneiric this problem still exists and is present on 3.1-rc10 as well. When bugzilla.kernel.org returns I will report it there.