Ubuntu
acpi package

Ubuntu 11.10 Shutdown wont power down

Asked by Rudi Hansen

I am running Ubuntu 11.10 with all updates, and i have had this problem from the beginning.
When i shutdown the computer, it does not power down, the last thing i see on the screen is:
[ xxxx.xxxxxx ] Power down. (Where xxxx is some numbers)

I have also tried # shutdown -h now
With the same result

This should be the last lines of the kern.log...
Feb 4 15:55:20 rsh-linux kernel: [ 14.106496] NET: Registered protocol family 31
Feb 4 15:55:20 rsh-linux kernel: [ 14.106497] Bluetooth: HCI device and connection manager initialized
Feb 4 15:55:20 rsh-linux kernel: [ 14.106499] Bluetooth: HCI socket layer initialized
Feb 4 15:55:20 rsh-linux kernel: [ 14.106500] Bluetooth: L2CAP socket layer initialized
Feb 4 15:55:20 rsh-linux kernel: [ 14.106799] Bluetooth: SCO socket layer initialized
Feb 4 15:55:20 rsh-linux kernel: [ 14.108448] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 4 15:55:20 rsh-linux kernel: [ 14.108450] Bluetooth: BNEP filters: protocol multicast
Feb 4 15:55:20 rsh-linux kernel: [ 14.111107] Bluetooth: RFCOMM TTY layer initialized
Feb 4 15:55:20 rsh-linux kernel: [ 14.111110] Bluetooth: RFCOMM socket layer initialized
Feb 4 15:55:20 rsh-linux kernel: [ 14.111111] Bluetooth: RFCOMM ver 1.11
Feb 4 15:55:21 rsh-linux kernel: [ 14.312856] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 4 15:55:21 rsh-linux kernel: [ 14.312860] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
Feb 4 15:55:21 rsh-linux kernel: [ 14.312991] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 4 15:55:21 rsh-linux kernel: [ 14.313156] /dev/vmnet: open called by PID 1118 (vmnet-bridge)
Feb 4 15:55:21 rsh-linux kernel: [ 14.313164] /dev/vmnet: hub 0 does not exist, allocating memory.
Feb 4 15:55:21 rsh-linux kernel: [ 14.313178] /dev/vmnet: port on hub 0 successfully opened
Feb 4 15:55:21 rsh-linux kernel: [ 14.313187] bridge-eth0: up
Feb 4 15:55:21 rsh-linux kernel: [ 14.313189] bridge-eth0: attached
Feb 4 15:55:21 rsh-linux kernel: [ 14.513243] userif-2: sent link down event.
Feb 4 15:55:21 rsh-linux kernel: [ 14.513246] userif-2: sent link up event.
Feb 4 15:55:21 rsh-linux kernel: [ 15.066782] EXT4-fs (dm-5): re-mounted. Opts: errors=remount-ro,user_xattr,commit=0
Feb 4 15:55:21 rsh-linux kernel: [ 15.210089] init: plymouth-stop pre-start process (1904) terminated with status 1
Feb 4 15:55:22 rsh-linux kernel: [ 15.451847] EXT4-fs (dm-5): re-mounted. Opts: errors=remount-ro,user_xattr,commit=0
Feb 4 15:55:22 rsh-linux kernel: [ 15.637093] userif-2: sent link down event.
Feb 4 15:55:31 rsh-linux kernel: [ 15.637095] userif-2: sent link up event.
Feb 4 15:55:31 rsh-linux kernel: [ 24.272011] vmnet1: no IPv6 routers present
Feb 4 15:55:31 rsh-linux kernel: [ 24.544009] vmnet8: no IPv6 routers present
Feb 4 15:55:31 rsh-linux kernel: [ 24.800008] eth0: no IPv6 routers present

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu acpi Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
mycae (mycae) said : 		#1

The numbers are the timestamp from boot (seconds, i believe) I don't suppose that you are booting with noacpi ?

If you are using a laptop can you post the make & model? perhaps someone has had similar problems. Otherwise, the motherboard model might be useful.

Also, please post:

uname -a
lsb_release -a

Revision history for this message
Rudi Hansen (rsh-pobox) said : 		#2

I found this line in my Grub.cfg:
linux /boot/vmlinuz-3.0.0-15-generic-pae root=UUID=99166848-cb15-460b-805d-43bf853d135e ro quiet acpi=force
Does that mean that i use acpi?

My machine is not a labtop, and the motherboard is an ASUS P5LD2

$ uname -a
Linux rsh-linux 3.0.0-15-generic-pae #26-Ubuntu SMP Fri Jan 20 17:07:31 UTC 2012 i686 i686 i386 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric

Revision history for this message
mycae (mycae) said : 		#3

This is reported for earlier kernels, but I couldn't find anything against a 3.0 kernel.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/227844

I assume that this occurs in a live session too and/or in amd64 (assuming you have a 64 bit chipset).

Revision history for this message
Rudi Hansen (rsh-pobox) said : 		#4

Not sure what you mean with a live session, and i am running on an Intel 32 Bit version.

Revision history for this message
Chris (fabricator4) said : 		#5

By live session, he means when booted off a LiveCD or LiveUSB - the desktop install CD or USB running in "try it" mode.

'acpi=force' means that the system will be forced to use acpi. Ubiquity must have detected that this would not be done automatically but that the BIOS was at least partly compatible. I've never seen it added before. You could try adding the switch 'acpi_osi=Linux' after the 'acpi=force' and see if that helps. This will force Linux to communicate to the BIOS that is correctly using Linux ACPI.

Chris

Revision history for this message
Rudi Hansen (rsh-pobox) said : 		#6

Thanks that did the trick.

Wow this thing has been bothering me ever since i installed linux on my machine, i should have asked here from the beginning :-)

Revision history for this message
Rudi Hansen (rsh-pobox) said : 		#7

Thanks Chris, that solved my question.

Revision history for this message
Chris (fabricator4) said : 		#8

Cool. I'm adding this fix and information to a config folder that I'm starting to keep. It's not the first time I've come across the same or similar question being asked.

Maybe one day when I get that Ubuntu blog up and running...

Chris

Revision history for this message
Rudi Hansen (rsh-pobox) said : 		#9

Ohh crap well it worked the first time i shutdown my computer, but now it's not working again.
The last lines from my console when i shutdown is as follows:
 * Killing all remaining processes... [fail]
modem-manager[675]: <info> Caught signal 15, shutting down...

nm-dispatcher.action: Caught signal 15, shutting down...
 * Deconfigureing network interfaces... [OK]
 * Deactivating swap... [OK]
umount: /run/lock: not mounted
 * Will now halt
[ 64.736308] Power down.

Revision history for this message
Rudi Hansen (rsh-pobox) said : 		#10

Bump, still having problems.

Though now some times my computer will halt, it seems to be random if it works or not.

Revision history for this message
mfauzirahman (mfauzirahman) said : 		#11

have try to upgrade kernel?
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Revision history for this message
Rudi Hansen (rsh-pobox) said : 		#12

I am running with all the latest updates installed, so i should have the latest kernel i think.

Revision history for this message
Torsten Sievers (ww0311) said : 		#13

Hi,

same behavoir observered here in with multiple installations:

- recent kernel upgrade to an already running kunbutu 11.10 with 32 bit pae kernel, power down was working before the kernel update absolutly without issues. This issue exists with 3.0.0-14 and 15
- upgraded a pc from an old ubuntu 08.04 (or something) to 11.10 with 32 bit pae and non-pae kernel. power down does not work since upgrade. The used kernel is 3.0.0-14 and 15
- created a oracle virtual box image with 11.10 from scratch with 32-bit pae and non-pae kernel. does also not power down, having dozens of virtual boxes, this is the only virtual box i have with 11.10 and its the only one that does not power down. Again Kernel tried is 3.0.0-14 and 15

So for me it is quite obvious that there is a general issue with the power-down in the kernel or some glitch in some settings !?

best regards

Can you help with this problem?

Provide an answer of your own, or ask Rudi Hansen for more information if necessary.

To post a message you must log in.