8.10: no reboot, no shutdown

Bug #321132 reported by Xavier Bestel
8
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

Hi,

I know this problem seems to be widely reported, but apparently there are many subltly different variants.

In my case, I tried booting with acpi=off (gdm doesn't start in that case), apm=power-off, replacing halt by shutdown, rmmoding sdn-hda-intel, but notthing worked.

In fact, I saw that /etc/rc0.d/S90halt is never executed (I disabled usplash and inserted an echo line at start). As I don't know how to find my way in the boot scripts, I can't tell you more.

I have an up-to-date ubuntu 8.10, installed from scratch (not an update).

Here's an lspci + dmesg:
(see attachments - webpigeon)

Revision history for this message
Chris Crisafulli (itnet7) wrote :

Thanks for your bug report and for your contribution to ubuntu. In order to determine if this issue is usplash related, would you boot your computer with usplash disabled and then shutdown to see if you can reproduce the issue? To disable usplash for a single boot, you can follow these steps :

1.Press Esc during Grub boot delay to access the boot menu.
2.Select your actual Ubuntu boot line and press "e" to edit it.
3.Select the "kernel" line and press "e" to edit it.
4.At the end of the line, remove "splash" and "quiet" and press "enter".
5.Type "b" to boot the custom boot line.

After reading what you had written I saw that you disabled usplash and inserted and echo line at start. I had the same issue you're talking about here and did what it said to test. Then just modified my menu.lst file when I saw it worked.

Revision history for this message
Xavier Bestel (xavier-bestel) wrote :

Hi,

I have already disabled usplash, but it doesn't help (it just helps to know the S90halt isn't executed).

Revision history for this message
Chris Crisafulli (itnet7) wrote :

I read that you had disabled but wasn't sure that it was by passing it at boot time. There are three other similar bugs (probably a lot more than that) 250506, 274508, 71004. All describing similar circumstance. Do you know whether or not you have a Intel HDA audio chip? Can you attach the output of the following commands:

# uname -a > uname-a.log
# cat /proc/version_signature > proc_version_signature.log
# sudo lspci -vvnn > lspci-vvnn.log (those are 2 v's not a w)
# dmesg > dmesg.log

It seems as though they are suggesting that you might not have a problem shutting down if you try two things.... run the shutdown from the terminal using sudo , example: sudo shutdown -h now
or adding rmmod snd-hda-intel if it's present and trying to shutdown when that module is removed.

Hope some of his may help.

Chris

Revision history for this message
Xavier Bestel (xavier-bestel) wrote :

You should re-read my bugreport .. I already tried all of this :)

Revision history for this message
Chris Crisafulli (itnet7) wrote :

You're right, Maybe it would have been easier to remember the details if you would have included the lspci/debug as an attachment instead of having the need to scroll to remember what was said :-)

Revision history for this message
Chris Crisafulli (itnet7) wrote :

So you also can't successfully shutdown from a terminal using sudo?

Revision history for this message
Chris Crisafulli (itnet7) wrote :

What are the results of shutting down when using a LIVE Cd? Does it also hang then?

Revision history for this message
Xavier Bestel (xavier-bestel) wrote :

So, in a terminal using sudo, neither shutdown -h now nor halt shutdown the computer.
And the live cd doesn't shutdown either.

Revision history for this message
Steve Langasek (vorlon) wrote :

Not sure where this bug is, but it's not an acpi-support bug; removing the package assignment.

If S90halt is not called, have you tried inserting similar debug echo's into the other scripts in /etc/rc0.d to see where things get hung up?

affects: acpi-support (Ubuntu) → ubuntu
Revision history for this message
Xavier Bestel (xavier-bestel) wrote :

Sorry for not following up ... I fixed the init/shutdown sequence (indeed with great help from echo and ping) by changing the position of nfs mounts. The problem I had was that my fstab has some NFS mounts, which are unmounted AFTER the network is shut down. That's why it didn't work.

Revision history for this message
Joseph Walton-Rivers (webpigeon) wrote :
Revision history for this message
Joseph Walton-Rivers (webpigeon) wrote :

I know this is probably the wrong way to do it, but, in an attempt to tidy up the bug report I've added the lspci and dmesg as attachments to the bug report and removed them from the description.

description: updated
Revision history for this message
David Tombs (dgtombs) wrote :

Hi Xavier, thanks for the info. Would you still consider this a bug? NFS mounts in fstab should work fine, if they don't it's a bug.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
David Tombs (dgtombs) wrote :

Actually, this appears to be a dupe of Bug 211631. Though it regards CIFS and this regards NFS, the underlying issue with n-m is the same. If you are on a wired connection, Xavier, this should now be fixed for you.

Changed in ubuntu:
status: Incomplete → Confirmed
Revision history for this message
Xavier Bestel (xavier-bestel) wrote :

Indeed, it's fixed for Ubuntu (wish it was for Debian too).

Thanks.

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.