jaunty and intrepid shutdown/restart hang on "acpid: exiting"

[Brion Swanson]

After reports and resolutions for many similar bugs (bug #288863, bug #126140, and bug #274995) none of those bugs or their resolutions have fixed the hang experienced during shutdown and reboot in Intrepid Ibex beginning near kernel release 2.6.27-5.

On occasion after Splashy times out or by pressing ctrl-alt-F7 or ctrl-alt-F8 I will see "acpid: exiting..." with a flashing cursor and no activity. No amount of waiting ever allows the shutdown/restart process to complete, only a hard reset or shutdown is successful.

Description: Ubuntu 8.10
Release: 8.10

acpid:
  Installed: 1.0.6-9ubuntu4
  Candidate: 1.0.6-9ubuntu4
  Version table:
 *** 1.0.6-9ubuntu4 0
        500 http://ubuntu.media.mit.edu intrepid/main Packages
        100 /var/lib/dpkg/status

uname -a
Linux lightyear 2.6.27-10-generic #1 SMP Fri Nov 21 19:19:18 UTC 2008 x86_64 GNU/Linux

[Brion Swanson (brions)]

This may be a duplicate of bug #286308. Not enough information at this time to determine if they are exactly the same.

[Brion Swanson (brions)]

It's probably also worth noting that using 'acpi=off' or 'noacpi' on the kernel boot line does not impact the (in)ability to shutdown / reboot.

[CarlosMartin (mostolescentro)]

I have exactly the same problem. Shutdown usually stop with a black screen and "acpid: exiting...", sometimes just a black screen and a few times (2 times in the last months) the system shutdown properly.

I am not an expert but I can provide as much information as needed. (I just don't know where to start.)

uname -a
Linux bslpsdr 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

[Max Littlemore (simon-leonard)]

I'm getting this too.

uname -a
Linux hector-luft 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

@Brion - after doing some searching and trying to find a report of this bug, I don't think this is a dupe. It is pretty serious though. This in combination with the fact that I can't wake up from suspend is making me wish I had stayed with hardy.

[Kurtismonger (kurtismonger)]

I'm having the same issue. I've tried all the fixes suggested in 274995 with no change.
Linux 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

[Kurtismonger (kurtismonger)]

Here are my system specs:

Acer TravelMate 4500

CPU: Intel Pentium M processor 1.60GHz

Memory
: 512MiB

Display:0 VGA compatible controller Intel 82852/855GM Integrated Graphics Device

eth0: Broadcom BCM4401 100Base-T

eth1: Intel PRO/Wireless 2200BG [Calexico2] Network Connection

Audio: Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller

Like Max, suspend/wake is flaky as well but I don't care as much about that as I do this acpid: exiting issue.
I'm happy to help testing if someone can help me here.

[FredBezies (fredbezies-deactivatedaccount)]

Stinks like a linux 2.6.27.xx problem. I tried a Fedora 10 two weeks ago, and shutdown problem was here too.

Maybe 2.6.28 fixed it ?!

[Tobias Jost (tjost)]

Hello,

I can confirm this problem on Acer Extensa 3000 (nearly identical with Travelmate 4500 posted above).

I tried a workaround suggested at http://ubuntuforums.org/showthread.php?t=987699 but I don't think alsa is the problem here. Unloading snd_hda_intel doesn't help either.

I'm running kernel 2.6.27-9, I am going to try compiling 2.6.28 and report if the problem persists

[Timo Karhu (nalle-karhulitos)]

Hello,

here is one Acer Aspire 7520G too and same exact problem.
Stopping networking from network-manager before doing shut down allows the PC to power off properly, just shutting PC down results in eternal wait and power still on.

[Alvaro Fernandez (alvaro-fernandez)]

it solved when I updated to kernel 2.6.28

[Greg Yates (gyates)]

I started receiving this problem after I changed graphic driver. I changed NVidia driver from the recommended driver to the older one trying to figure out the problem of the screen going blank on boot when the desktop should be up. This worked, now however, the system now won't shut down sometimes and gives the "acpid: exiting" error.

[FredBezies (fredbezies-deactivatedaccount)]

Seeing it too with jaunty :[

It drives me crazy. I was hoping that jaunty kernel was free of this horrible bug :(

[Brion Swanson (brions)]

Sadly I did see a fix come through (no idea which update) and when I tried to reboot to my amazement and joy it worked! Two updates later it was broken again. :(

Shutdown never worked during this period and reboot is not working again. I did a dist-upgrade recently with the alpha repository, but that didn't seem to make any difference.

[FredBezies (fredbezies-deactivatedaccount)]

To be complete : I booted an archlinux 2009.02 (USB key based version), and I saw the same problem : shutdown cannot be completed :/

And it is based on a 2.6.28.5 (or 6) linux kernel.

So, there was a bug introduced during 2.6.27 development time which block shutdown on some computer !

[FredBezies (fredbezies-deactivatedaccount)]

And it "stinks" like a 64 bits only bug. An Intrepid ibex 32 bits booted on an USB key shutdown properly !

[FredBezies (fredbezies-deactivatedaccount)]

Modifying title to add it also existing in jaunty.

[cronocopio (firefoxbt)]

same problem with real time kernel 2.6.27-3-rt in ubuntu studio, I switched to kernel 2.6.22-14-rt and the problem did not show up, system shutdown/reboot fine with stock kernel 2.6.27-11-generic

[Brion Swanson (brions)]

Update: Sometime in the recent past (it's always hard to tell because I don't reboot often) I downloaded yet another update from the Update Manager and now instead of hanging on reboot I get a series of fast system beeps while my monitors go into power save mode, and then I get a single long tone that never ends (until I hit the reset button).

So it's gone from bad to worse. I'd rather I have to press the reset button in silence than to listen to these hideous beeps (or to disconnect my PC speaker).

If anyone has a clue as to what's causing this or how I might troubleshoot and/or work around it I'd be very grateful!

[Guillaume Desmottes (cassidy)]

I just installed Jaunty on my brand new Lenovo X200s and have this bug too.

[DEFHol (dfleener)]

I just recently re-installed Ubuntu Studio 8.04 on a computer that I forgot my administrator password for. I then immediately did a distribution upgrade to 8.10, and another to 9.04 (Jaunty Beta), and I now have this bug. The realtime kernel is installed, it is 32 bit, and it didn't occur on 8.04, nor on 8.10, when I upgraded it. Update-manager crashed at the end of the Jaunty beta upgrade, and I did:

[dpkg --configure -a]

to finish configuration, after a reboot into failsafe terminal mode. I don't know if this is part of my problem or not, but the computer will not shutdown or reboot. Only a hard-reset will power it down. I'm not on the computer right now, to give detailed system info, but it is a Dell Optiplex GX280 with 3.0 GHz P4, Hyperthreaded, 2GB System RAM, 320GB SATA HDD. The kernel is the latest kernel release for Jaunty Beta as of April 02, 2009.

I will try all the workarounds mentioned here and otherwise, and post more info later, if possible.

[DEFHol (dfleener)]

After much tinkering around with updating packages (using update-manager) and doing [dpkg-reconfigure -a] to reconfigure my system, my system will shutdown and reboot properly now. I disabled the nVidia driver and changed to the generic kernel, instead of using the realtime kernel, which fixed the problem temporarily. But when I got the system fully updated, I installed envyng and was able to use that to re-install nVidia drivers. I am still using the Ubuntu generic kernel. I haven't tried re-instating the rt kernel yet. I am using Jaunty, all updates current as of April 5th. My system is behaving properly for now.

[mroe (mitchellroe-236)]

I can confirm the fix presented by DEFHol on a Dell XPS M1330.
my uname is:
Linux 2.6.28-11-generic #40-Ubuntu SMP x86_64 GNU/Linux
I don't have Intel video, so I just did the "dpkg-reconfigure -a", and it worked fine.
Everything working up to par.

[mroe (mitchellroe-236)]

Addendum:
I DO have Intel video. I DON'T have nVidia. Sorry.

[FredBezies (fredbezies-deactivatedaccount)]

I fixed this bug by using mainline kernel :

https://wiki.ubuntu.com/KernelMainlineBuilds

And my uname :

fred@fredo-ubuntu:~$ uname -a
Linux fredo-ubuntu 2.6.29-02062901-generic #02062901 SMP Fri Apr 3 13:36:07 UTC 2009 x86_64 GNU/Linux

Linux kernel 2.6.29.1

Strange to see this bug is fixed in this version.

[myo (myo-sound)]

I had this same problem, not audio or network related.
switching back to the 2.6.24-23-rt kernel from hardy solved for me.

[Brion Swanson (brions)]

Just updated to Jaunty with the 2.6.28 kernel and it still exhibits this problem. I will try to do the 'dpkg-reconfigure -a' to see if that helps.

It's a puzzle to me how this bug has remained through a full release of Ubuntu and a new kernel version.

[Charles Profitt (cprofitt)]

In Jaunty I get a hang, but no longer get the acpid: exiting...

I will attach two digital pictures.

The first one is where the system hangs on shutdown

[Charles Profitt (cprofitt)]

Here is what happens after I wait on the hang for 60 seconds and then hit cntll+alt+del

[Charles Profitt (cprofitt)]

I moved this to confirmed. but I feel there is more information that is needed before marking it triaged.

[aarons (aarons-ubuntu)]

I also have this problem. I believe it showed up for me after I upgraded to Jaunty.

Linux pork 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

It may have been present in intrepid with 2.6.27-11, but I can't remember for sure. The machine is a dell studio 1537.

[Charles Profitt (cprofitt)]

If I do an:

sudo ifconfig wlan0 down

and then shut down I do not get the hang... this appears to indicate that the issue is with the wireless card.

-- 03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5300

[aarons (aarons-ubuntu)]

I just tried bringing wlan0 down before rebooting and that worked for me as well.

[Matt Zimmerman (mdz)]

This problem is very unlikely to be caused by acpid, so I'm moving it to the kernel as a more likely spot. At least one of the screenshots here includes part of a kernel panic, and I see reports that "sudo ifconfig wlan0 down" before shutdown is a workaround for some people.

It is very likely, however, that there are multiple problems being described which happen to have similar symptoms.

[Matt Zimmerman (mdz)]

@Brion Swanson: please attach your hardware configuration to this bug by running the following command:

apport-collect 302452

(assuming you have upgraded to 9.04. If not, please try to reproduce this bug with a 9.04 live CD)

[Charles Profitt (cprofitt)]

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Fernando Miguel (fernandomiguel)]

Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux 2.6.28.11.15
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom davfs2 dialout dip fax floppy fuse kvm lpadmin nagios netdev plugdev polkituser sambashare scanner sudo sys syslog tape users video voice www-data

[António Lima (amrlima)]

I have the same issue but only when using fglrx, If i use the free drivers the pc shuts down properly.

[António Lima (amrlima)]

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: fglrx
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=pt_PT.UTF-8
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Brion Swanson (brions)]

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video

[Guilden_NL - Joop deBruin (guilden-nl)]

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Guilden_NL - Joop deBruin (guilden-nl)]

I have the same results as Charles Profitt, If I close down the wireless link through the HW switch or by using command: sudo ifconfig wlan0 down, the hang doesn't happen. Same hang properties, blinking cursor in upper left corner of monitor. It happens regardless of AC or battery power.

I've attached my dmesg and lspci-vvnn logs in a tar.

[ursaminor (ursa-juvenis)]

I run Jaunty 9.04 on HP Pavilion a1228x AMD64. Except for Jaunty hanging at shut down, I have no other problems. I ran Intrepid 8.10 before upgrade and had no problems with shut down. I included a jpeg image to show screen before I have to shut down my computer by the power button.

[Berend De Schouwer (berend-de-schouwer)]

If I run wireless and Jaunty's 2.6.28, I get a hang. (not a full crash: plugging USB devices in and out still causes a reaction.)

If I don't run wireless, I can shut down.

If I run the mainline 2.6.29, I can shut down.

Wireless driver: iwl3945

(I'm running mainline anyway to get this ATI video card working correctly in KDE. OpenSource drivers.)

[Tim (tim-ballymena-hey)]

Can confirm the fix by closing the wireless link via a hardware switch on my Dell.

My original symptom:
The screen goes a bright white and then fades very slowly to partially dark with black lines and never turns off.

With the fix:
It still exhibits the original symptom, but only for a few milliseconds, enough to notice it still happens though, then it shuts down completely.

My system:
Clean install with all updates applied as of yesterday. No other proprietary drivers - running all of the system defaults. Used both EnvyNG to install the drivers and also the restricted drivers installer.

Specs:
Dell XPS m1530
Ubuntu 9.04 LTS x64
Nvidia 8600M GS

Comments:
The dpkg-reconfigure -a fix people listed gave me a hell of a lot of options to have to decide upon - not very practical for most people

[Allan (allan-2bc)]

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
Uname: Linux 2.6.28-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[ursaminor (ursa-juvenis)]

My issue has been resolved by installing the 2.6.30-rc7 kernel for AMD64. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368366

[Djamu (djamu)]

My issue had been resolved ( on nfsmounted PXE clients ) by making sure the lo loopback interface is up and configured

in /etc/network/interfaces

auto lo
iface lo inet loopback

[aihua (aihua-tech)]

Agree with what FredBezies said, #15. I have install x86 ubuntu 8.10 desktop, it is ok, but after I remove x86 ubuntu 8.10 and then install x64 ubuntu 8.10 from ubuntu-8.10-desktop-amd64.iso, occured 'acpid: exiting....'

[aihua (aihua-tech)]

BTW, my notebook is Thinkpad 2055-2CA, the os is Linux open 2.6.27-14-generic #1 SMP Tue Jul 7 22:18:38 UTC 2009 x86_64 GNU/Linux

[Brion Swanson (brions)]

I've found a solution to this bug for me (the reporter) so if problems still remain it may be a good idea to open a new bug for your problem.

Main problem: reboot/shutdown hangs with either "acpid: exiting" or "nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /or/freedesktop/Hal/devices/net..." and nothing can persuade the compute to complete side from a hard power cycle

Primary cause (for me): nfs mounts in nested folders (i.e. /mnt/remote1/remote2)

Solution: move nfs mount locations to non-nested folders (i.e. /mnt/remote1, /mnt/remote2)

Further detail: Essentially my /etc/fstab mounts two remote filesystems in the following manner: mount remote1 to /mnt/remote1, then mount remote2 to /mnt/remote1/remote2. This works fine as long as the first nfs filesystem has a remote2 directory. However, on shutdown or reboot when unmounting the system tries to unmount /mnt/remote1 and fails because /mnt/remote1/remote2 is still mounted. Then it unmounts /mnt/remote1/remote2 which succeeds but it never attempts to unmount /mnt/remote1 again and thus we're left hanging waiting for all filesystems to be unmounted.

I hope this sheds some light on the problem for others. This doesn't so much seem to be a bug as it is a misunderstanding about how (not) to mount network filesystems.

I will be removing the binary package hint since this has nothing to do with acpid.

[Brion Swanson (brions)]

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-15-generic x86_64
UserGroups: adm admin audio cdrom dialout lpadmin mythtv plugdev sambashare video

[showgun (showgun)]

I have the same issue
Jaunty 64 will hang on shutdown and reboot ctrl alt del will rebbot it pwer botton will shut it down.
2.6.28-15-generic
It will do this only when I connect to my secure wireless network, but when I connect to any unsecure network it will shutdown or reboot no problem.

[Jim Rorie (jfrorie)]

Macbook Pro 5,1 appears to be rebooting as of Karmic Alpha 6.

[ibuntu (ubuntu-dkb3)]

Maybe this is a network issue. My system often hangs on shutdown but if I power down my DSL modem/router, the shutdown completes with "acpid: exiting" message.

[Bettina Kölling (bettina-koelling)]

This problems occurs on my HP 6830s laptop after upgrading from 10.10 (64bit) to 11.04 (64bit).
Never seen this on 10.10

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.