shutdown hangs (sometimes) - Hardy 64 - ASUS P5LD2 SE

Bug #227844 reported by JB5
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Hi - Running MythTV (0.21) on Ubuntu box (Hardy-64).

[ASUS P5LD2 SE - MB; E2140 - CPU; MSI - nvidea 7300LE - GPU; 4GB - Corsair PC2-5400 RAM; ]

Previously Gutsy-64 had no problems shutting the machine down using the following command, issued by MythWelcome.
sudo shutdown -P now

After upgrade to Hardy-64, the same command issued through MythWelcome occasionally causes the system to stop short of a full shutdown.
Tried changing the boot options to use nosplash and acpi=force, without success.
The shutdown sequence gets as far as spinning down the drives and then the last command seen is:-
[some long number] Power Down
with a blinking cursor underneath. The fans and MB, GPU etc are still powered up. Other occasions the shut down will complete properly!

Note this was a clean install of Gutsy-64, followed by an upgrade to Hardy-64.
The same command issued from the terminal also OCCASIONALLY falls short of complete shutdown.

Attached are results of:-
uname -a
cat /proc/version_signature
dmesg
sudo lspci -vvnn
sudo dmidecode

Tags: cft-2.6.27
Revision history for this message
JB5 (sir-bunt) wrote :
Revision history for this message
JB5 (sir-bunt) wrote :

The problem persists after recent kernel & other associated upgrades/updates (2.6.24-17-generic).

The machine will also hang occasionally when trying to shutdown from the menu/button.

Changed in linux:
status: Confirmed → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
JB5 (sir-bunt) wrote :

I don't have a spare test rig so went the Live CD route, and entered command

sudo shutdown -P now

from the terminal.

The machine shut down successfully 25+ times.
I would have expected >4 power down failures if Hardy had been shut down 25 times!

So, from this limited test, it would appear that the newer Kernel does not suffer from this problem.

Thank you.
Good work. :)

Revision history for this message
JB5 (sir-bunt) wrote :

btw The alpha5 LiveCD was used.

Revision history for this message
JB5 (sir-bunt) wrote :

Ok - Upgraded machine to Intrepid-Beta1.

Problem has reoccurred.

This has been filed, please see :-
https://bugs.launchpad.net/ubuntu/+bug/281240

Revision history for this message
agenthex (hexsmith) wrote :

I experience this problem frequently in Intrepid.

Dell Inspiron 1520
Core 2 Duo T7500
nVidia 8400M GS
Intel 4965 AGN

Tested video driver 177 and 180 (beta). Recently replaced wireless chip.

Any other questions, just ask.

Revision history for this message
JB5 (sir-bunt) wrote :

Someone else has reported success upgrading to the proposed Intrepid ....-11 kernel.

Unfortunately, this did not resolve the problem for me.

Revision history for this message
Luis Lumbreras Picazo (luis-lumbreras-picazo) wrote :

I have the same problem, but it seems to be a "gdm" problem, not related with acpi nor with "apm"... le te mexplain why:

If i tell it to hybernate it power off at end of it and when powered on again it resumes well.
If i tell it to shutdown it does not power off at end, but hey only if gdm was running when asked.

More detailed:
If gdm is running and i open a terminal window: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works
If gdm is running and i press Ctrl+Alt+F2 to go to a console at full screen (text mode), but i let gdm running: no way to power off after shutdown, none commands: shutdown, halt --poweroff,... none works

But, if i press Ctrl+Alt+F2 to go to a console at full screen (text mode), and do:
#sudo /etc/init.d/gdm stop
So gdm is stopped then after few secconds i can confirm it is stopped with [ps -A | grep gdm], so i ask to shutdown with:
#sudo halt --poweroff
Or with shutdown,... all of them at end turns off the power and power off the notebook correctly.

I have seen on Internet a lot of forums on where they tell something about acpi=force, apm=power-off,... on /boot/grub/menu.lst also about adding apm to modules,... etc. none of that works for me.

And i found that if gdm is not running when calling shutdown it power off correctly.

When i was using Ubuntu Intrepid Ibex and Ubuntu Jaunty Jackalope it allways power off correctly, but when i updated to Ubuntu Karmic Koala it starts to not do the final power off when shutdown... now i know the cause is gdm running when calling shutdown.

Maybe it is related in some way with Kernel or with propietary ATI graphics driver...

Also i can see some near identical lines (more than ten) on /var/messages at the end of it with this error:
Kernel: Assertion fail in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_rs780.0 at line: 53

I do not know if such error is related with the shutdown problem, but is the last error logged and it is at end ot /var/messages no more lines after it... but i can only see it when not powered off correctly, if i do the trick of stoping gdm it does not appear.

Hope this can help someone to fix-it. Till them i will do the trick of Ctrl+Alt+F2 -> login -> password -> sudo /etc/init.d/gdm stop -> sudo halt --poweroff

Note:
After doing such, i powered on again and then after some hours of work i press shutdown by mistake (did not remember ro do the trick "stop gdm then halt --poweroff") but what surprise! it turns off the notebook correctly... so when i have time i will re-check if it was only once or can be reproduced.

I mean:
-Power On, then tell destop menu to shutdown normally and check if it turns off.
-If not force turn off, then turn on again, do the trick of stopping gdm and halt --poweroff, then power on again then tell destop menu to shutdown normally and check if it turns off.

But i will not have time till weekend, so if any one can also check that, it would be great.

SOLUTION THAT WORKS FOR ME:
Ctrl+Alt+F2 -> Login -> Password -> sudo /etc/init.d/gdm stop -> sudo halt --poweroff

Revision history for this message
Aadil H (aadilh) wrote :

Reinstall initscripts from package manager.... see my experience with this annoyance...

Problem at shutdown failure at deactivating Swap.... Solved on Karmic Ubuntu

After over a month, desperately searching the INTERNET launchpad and wherever the search engines took me. I found the solution for my system. It is so simple I'm surprised none of the experts of the many many forums ever suggested it.

I forced my system off, i restarted to bios and power it off from there, tried to modify scripts and power down using various commands, yet it all failed, the hours & hours wasted. After almost giving up & waiting for the next major update to Lucid Lynx meaning months to shutdown my system properly (silly but well what can i say)

OK to the point.... which really really doesn't make me happy.... because of its simplicity.

I decided to find some shutdown tools in the hope that an advanced tool might help... So I Entered Synaptic Package Manager

Did a search... typed shut (& of course the results had a few tools for shutting down) or you can search initscripts which is my solution

1. I right clicked (sweet no command line)
2. Mark for re-installation (sweet so simple)
3. Apply & let the task complete

4. Reboot / perhaps shutdown & your computer powers off itself (You must love technology that turns off when you tell it to)

As a new user, why of why didn't anyone say i could have reinstalled that, i was thinking how to reinstall shutdown but didn't know the term i needed. I'd be interested to know, does this solve a

Revision history for this message
JB5 (sir-bunt) wrote :

Tried the above (initscripts & shut).
Seemed to help after a recent update caused regular power-off problems,
unfortunately had another couple of power-off problems since.

Revision history for this message
JB5 (sir-bunt) wrote :

Stopping GDM before shutting down doesn't work either.

The power-off problem was relatively rare until I applied the following updates [commit log - attached].
After these updates the problem became VERY frequent. (re-installing initscript seemed to help for a while).

I don't know if anything can be teased from the information or if it's just more noise.
Hopefully the former, apologies if the latter.

Revision history for this message
JB5 (sir-bunt) wrote :

Problem still persists in current Lucid(64) Kernel - 2.6.32-22-generic

Revision history for this message
JB5 (sir-bunt) wrote :

After upgrade to Maverick this problem has NOT recurred.

        Linux ERIC 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux

Shutdowns have executed properly for > 4 weeks. Will report if problem returns.

Thanks.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

JB5,
    As you are the original reporter, I am going to close this bug as fixed. If you see the issue again, you can reopen this bug.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Triaged → Fix Released
assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.