Shutdown still doesn't turn off my computer

Bug #44008 reported by Frank McCormick
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Shutdown on my machine (HP Vectra VL 450 mhz Pentium III) still does not turn off the computer. The HD shutsdown but power is left applied to the computer. Dapper used to shut down everything until about 3 months ago. Breezy also worked properly. I am using the latest Kernel , and Dapper is up to date(May 10th).

Revision history for this message
Simon Law (sfllaw) wrote :

Hi Frank,

There are a few diagnostic tools that I'd like you to run so we can
try to pinpoint the problem. Could you shutdown your computer,
power it up again, and run:

$ lspci -vv > /tmp/lspci-vv.log
$ lspci -vvn > /tmp/lspci-vvn.log
$ dmesg > /tmp/dmesg.log
$ sudo dmidecode > /tmp/dmidecode.log

Then, please attach /tmp/lspci-vv.log, /tmp/lspci-vvn.log, /tmp/dmesg.log,
and /tmp/dmidecode.log to this bug.
https://launchpad.net/distros/ubuntu/+bug/44008/+addattachment

Thanks!

Revision history for this message
Frank McCormick (fmccormick) wrote : dmesg.log

As requested

Revision history for this message
Frank McCormick (fmccormick) wrote : dmidecode.log

As requested

Revision history for this message
Frank McCormick (fmccormick) wrote : lspci-vv.log

As requested

Revision history for this message
Frank McCormick (fmccormick) wrote : lspci-vvn.log

As requested

Simon Law (sfllaw)
Changed in linux-source-2.6.15:
status: Needs Info → Confirmed
Revision history for this message
Carlos Vicente (raven-cv) wrote :

I have exactly the same problem.
I have a P IV 3.4 GHz, and I'm using Edgy with 2.6.17-10-generic.

Other interesting thing to notice is that, after starting my machine, if I don't log on to my account and I try to do shutdown, it will work flawlessly!

Carlos Vicente

Revision history for this message
Carl (carl-kde) wrote :

I have the same problem Carlos Vicente described with gutsy and now with hardy : the computer is turned off only if I shutdown from kdm without having opened a kde session.
i join my files.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

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
vladimir prieto (vladimirprieto) wrote :

hi all.

i've been playing around with Intrepid Ibex since the First Beta Release. since then i been updating almost every day, and the problem persist: it does not power off.

i have attach the logs asked above and i'll be waiting for another way for helping.

by the way i have seen this bug on differents notebooks testing beta live cd.

Revision history for this message
Seppl (seppl) wrote :

Hi all,

several users report that this issue occurs "again" until the update to Ubuntu Jaunty.

See the following tread.
http://ubuntuforums.org/showthread.php?t=1107955&highlight=shutdown

Same for my Notebook Samsung R60 too. Intrepid worked flawless since the update to Jaunty the problem started.

Revision history for this message
Vinicius Camargo (vinicius-hotmail-de) wrote :

Hi

I have been had this problem since I updated my system to Ubuntu Hardy Heron. Recently I am using Ubuntu Jaunty and I am having the same problem. The computer give all normal messages of the shutdown process but it doesn't power off.
When I was using Ubuntu 8.04 LTS I didn't have this problem.

I also attached my log files.

Revision history for this message
phenest (steve-clark) wrote :

I have narrowed this down to wireless. If wireless is disabled in Network Manager, the computer shuts down correctly.

Revision history for this message
Vinicius Camargo (vinicius-hotmail-de) wrote :

Thanks for the help. but for me this wireless thing doesn't work and I already tried everything that involves "acpi=force", "apm=off", "rmmod snd_hda_intel", edit halt and insert the command "ifconfig wlan0 down", etc.
Even if I install the ubuntu server without any extra package I have this problem too. I thing that the bug is in the kernel compilation. It seems that they disabled some option that makes my laptop doesn't shutdown anymore.

Revision history for this message
Vinicius Camargo (vinicius-hotmail-de) wrote :

For my notebook, this problem is fixed in Ubuntu 9.10.
I also have the wireless light blinking now.

Revision history for this message
Keith Allcock (keith-allcock) wrote :

Hi,

I have just started to see this on an Intel Mac Mini using 9.10.
From 8.04 to 9.04 all versions were previously ok for me.

As my Mac is a mythtv box it needs to run the shutdown command as a script, but it fails. Running shutdown -h now manually as the same user succeeds.

I have tried disabling modules as above with no success

Revision history for this message
Keith Allcock (keith-allcock) wrote :

Logs ...

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
Keith Allcock (keith-allcock) wrote :

Hi,

Tried it but no joy.
I put my pc into a 3 minute cycle of shutdown, then acpi wakeup after 2 mins.
It seems to be ok for the first 2 restarts but seems to be 'reasonably' consistent that the 3rd time it hangs on shutdown. Power light goes off, but monitor output remains active (with no actual output, just a black screen).

Revision history for this message
Selmi (selmi) wrote :

sudo /etc/init.d/gdm stop didn't helped for me.

always when i try to shutdown (using gnome menu, or using halt --poweroff or halt) it end on text screen with last message about deactivating swap. then it stays until i press ctrl-alt-del. then reboot continues with killing tasks etc.

it worked before, even in karmic koala...i don't know what could breakit, maybe some update... but since it was working for sure i updated too much so i can't track what could it be

Revision history for this message
Keith Allcock (keith-allcock) wrote :

Poweroff now works again on 10.04

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

Frank,
    Can you confirm kja999's testing as above?

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
corigo (damon-corigo) wrote :

I've just done an install of MythBuntu 10.04 (32b release) on an HP Pavilion 5.5x (stock). I'm seeing the same problem. OS does normal shut down process, video turns off, but machine does not power down.

Changed in linux (Ubuntu):
status: Expired → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: New → Confirmed
dino99 (9d9)
Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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