MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check

Bug #274995 reported by astroman on 2008-09-26
424
This bug affects 44 people
Affects Status Importance Assigned to Milestone
NetworkManager
Invalid
Undecided
Unassigned
alsa-utils (Ubuntu)
Medium
Daniel T Chen
Intrepid
Undecided
Unassigned
linux (Fedora)
Fix Released
Medium
linux (Gentoo Linux)
Fix Released
Medium
linux (Ubuntu)
Undecided
Daniel T Chen
Intrepid
Undecided
Unassigned
network-manager (Ubuntu)
Medium
Unassigned
Intrepid
Undecided
Unassigned
pulseaudio (Ubuntu)
Undecided
Unassigned
Intrepid
Undecided
Unassigned

Bug Description

SRU information follows:

Impact: A subset of users with a default Ubuntu 8.10 install (with libasound2-plugins installed) experience nondeterministic hangs of up to several minutes on shutdown (or startup) when the sound card's mixer control state is (re)stored. This hang is due to a variable, PULSE_INTERNAL, in the pulse ALSA plugin having a non-NULL value when amixer and alsactl are called so that PulseAudio is probed preferentially, triggering name resolution over potentially partially configured network interfaces.

Resolution: In the alsa-utils initscript, unconditionally export PULSE_INTERNAL=0 to prevent native ALSA applications from probing PulseAudio while querying and (re)storing sound card state.

Jaunty patch: http://launchpadlibrarian.net/19941444/alsa-utils_1.0.18-1ubuntu2.debdiff
Intrepid SRU patch: http://launchpadlibrarian.net/19941520/alsa-utils_1.0.17-0ubuntu3.debdiff

TEST CASE: From an active GNOME session in a default Ubuntu 8.10 install, choose to reboot or shutdown. Note the erratic hang while attempting to store ALSA's mixer control state.

Regression potential: No regressions have been identified in production, and only users with both pulseaudio and libasound2-plugins packages installed have the potential to experience this nondeterministic hang.

Original report follows:

Ubuntu 8.10 beta 4 version updated.
When going for reboot or shutdown the system freezes on shuting down alsa.
The only way is to use the power off button of the computer.

My laptop is Insys GameForce.8761SU

Chipset:
• SiS© 671DX + SiS968

Description of problem:

If the snd_hda_intel module is loaded into the kernel (for example after
starting X), the computer will not power off when "poweroff" command is called.
My computer has an Asus P5GD1 motherboard.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Start computer at runlevel 5
2.Log in into X and play some sound just to be sure sound module is loaded
3.System -> Shut down.

Actual results:
The computer doesn't power off and hangs after a message "ACPI power down
called" is displayed.

Expected results:
The computer shoud poweroff

Additional info:

I added a 'modprobe -r snd_hda_intel' line in the stop) section of
/etc/init.d/kudzu and the computer shuts down correctly therafter.

Changing to proper owner, kernel-maint.

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Even with kernel-smp 2.6.18-1.22000.fc5 the problem persists. I tried booting
with the 'acpi=ht' boot option, but the system still doesn't poweroff, the only
thing changed is the last message printed: "System halted" instead of
"acpi_power_off called".
The only way to let the computer shutdown automatically is to call modprobe -r
snd_hda_intel somewhere during the shutdown process (I moved it from kudzu to
the halt script just after the "saving mixer settings" lines).

I can confirm the problem still exists in Fedora 7 with the Asus P5GD1
motherboard. I've had this annoying shutdown problem for five months and finally
I have found a workaround here, thanks Davide!! Unfortunately I found the bug
still exists in Fedora 8 Test 2 as well.

Changing version to F7 since that it the last released version that this problem
is reported in. You mention F8T2, does it exist in released F8?

*** Bug 212726 has been marked as a duplicate of this bug. ***

This bug is still present in F8 - kernel 2.6.23.9-85.fc8

Davide,

Could you try booting with acpi=off and then try powering off. Could you also
attach the following from a normal boot as separate attachments to this bug
(type text/plain):

# dmidecode
# lspci -vvxxx
dmesg

Created attachment 291992
dmidecode, lspci and dmesg output

Comment on attachment 291992
dmidecode, lspci and dmesg output

The system with acpi=off still does not power off.

Hello Davide,

Some more things to try:

Could you try unloading your vmware modules before powerdown. Could you also
attach the output (separate files please) of:

lsmod
/etc/modprobe.conf

Cheers
Chris

Created attachment 292123
lsmod

Created attachment 292124
/etc/modprobe.conf

(In reply to comment #11)
> Could you try unloading your vmware modules before powerdown.

It doesn't power off even without loading vmware and virtualbox modules.

the previous lsmod attachment is without vmware and vbox modules loaded and the
system did not power off.

Found the following which you should be able to use as a workaround:

If you edit /etc/init.d/halt and add “rmmod snd-hda-intel” this will unload the
module and poweroff completely.

I'm assigning anyway and adding ALSA blocker. Lowering severity and priority as
a workaround is available.

(In reply to comment #15)
> Found the following which you should be able to use as a workaround:
>
> If you edit /etc/init.d/halt and add “rmmod snd-hda-intel” this will unload the
> module and poweroff completely.

I'm already using that workaround since first reporting this bug, so it issn't a
big problem if it persists... :)

Bug still present in Fedora 9 - kernel 2.6.25.3-18.fc9.i686

314 comments hidden view all 322 comments
Luke Faraone (lfaraone) wrote :

What is the exact message that is displayed?

astroman (astrosousa) wrote :

The message is:

Shuting down ALSA...

The [OK] never apears... and freezes

astroman (astrosousa) wrote :

I notice that when I shutdown the network then this problem disapears and the pc shuts down normally.

My network is not operating correctly. How can I check for errors on this?

My internet connection is now very slow and cannot connect to several servers proprely, including the repositories servers. It happens both in ethernet and wireless.

I also notice that on the ethernet connection I notice several errors on:
Reception Errors, I have ethernet SIS 191 ubuntu 8.10‏.

any help?

Solitaire (bill-s0l) wrote :

Running a Dell Inspiron 8200 with Ubuntu 8:10 beta (Fully up to date)

Sound Card: Intel 82801CA-ICH3
Kernel : 2.6.27-5-generic

My network Wired and Wireless are fine.

Getting the "Shutting down ALSA..."
Have to wait 5 mins for ALSA to timeout for Shutdown to continue.

Alan Hartless (harty83) wrote :

Is anyone's sound actually working with this problem?

I've got the same problem and I just noticed that all I get when there is suppose to be sound is static. For example, play something with sound and all I hear is a scratchy noise.

Michael Rooney (mrooney) wrote :

I have had this happen as well on my Intrepid A5 install, Confirming.

Solitaire (bill-s0l) wrote :

@ Alan Hartless

My Audio is fine, no distortion or static to be heard.

Petrus Gomes (petrusgomes) wrote :

same problem here...Desktop

updated from hardy to 8.10 alpha6
issue with "shutting down ALSA" started with last beta updates...(kernel 2.6.27.5 and 2.6.27.6 generic)

sound and network are OK.

Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)

dieterv (dieterv77) wrote :

Just wanted to report that i'm seeing the same problem

Updated to 8.10 beta from up to date 8.04

sound card: Multimedia audio controller: C-Media Electronics Inc CM8738
kernel: 2.6.27-5-generic

I am able to get sound via ALSA, but shutdown hangs on "shutting down ALSA"

Feel free to let me know if there is other info i can provide.

Michael Rooney (mrooney) wrote :

dieterv and anyone else who can duplicate this bug (I've only had it happen once), you can help by removing the 'quiet' and 'splash' options from your boot entry (I think you hit 'e' when the grub timer is going to edit the option). Then when you shut down, it should hopefully give some more output when it gets stuck, such as perhaps the step it is getting stuck on. If you do this and post the output here, we will have a lot more information to go on. Thanks!

Solitaire (bill-s0l) wrote :

Mike

I removed 'quiet' and 'splash' then rebottede the machine twice.
Both times shutdown pauses on 'ALSA' for 5 mins before continuing.

No other message / error / warning was shown.

Anyone know if the shutdown messages kept in a logfile? or is logging stopped before that point?

Michael Rooney (mrooney) wrote :

Okay, if there is no extra info gained without quiet splash, I will mark to Confirmed until someone else can suggest what other information might be useful. I'll ask around.

Hi All,

First, this bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . This bug should be classified against the 'linux' kernel package so I am reassigning it there.

The second thing to note is that even though everyone here may be experiencing the same issue, it really is likely hardware specific. Unless you have the same hardware as the original bug reporter you should probably open a separate report.

@astroman, since you are the original bug reporter, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . I'm also curious if you try booting with the "reboot=b" boot option if that helps at all. Thanks again and we appreciate your help and feedback.

Michael Rooney (mrooney) wrote :

Hi Solitaire, thanks for filing a separate bug as Leann suggested, I'll link it here for reference, bug 280305.

Alan (mrintegrity) wrote :

Please note that this bug does not appear to be hardware specific, as previously noted, as it is seen with at least the following hardware configurations:

Intel Corporation 82801CA/CAM AC'97 Audio Controller [8086:2485] (rev 02) (Cirrus Logic Device)
VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller
ATI Technologies Inc SBx00 Azalia (Intel HDA)
Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)

The alsa-utils init script does not appear to be the culprit either as it starts and stops fine without problem although it is killing this script that will allow the shutdown process to continue.

In the Alpha6 release it was possible to switch to a virtual console, log in and "killall -9 K50alsa-utils" which immediately allowed the shutdown to continue however in the current beta it seems that keyboard login is disabled earlier and this is no longer possible, forcing the user to wait for the script to time out.

I installed ubuntu from an Alpha 6 desktop CD image and immediately ran update manager to get the latest packages.

Cheers,

Alan

Alan (mrintegrity) wrote :

I changed the affected package to alsa-utils as it seems to be related to the init script for this package. Also set status as confirmed.

Changed in linux:
status: Incomplete → Confirmed

Could this bug be related to x64 or does it effect 32 bit users as well?

Alan (mrintegrity) wrote :

I am on 32bit here.

Solitaire (bill-s0l) wrote :

I'm running 32 bit here as well.

Biji (biji) wrote :

32bit here.. probably when pulseaudio get hang but not crashes

eric.zhu5121 (simonz5121) wrote :

Same problem on my desktop with intel duo core 2. the mother board is asus p5ne-sli. the audio is using nvidia mcp55 hda.
each time when shutdown computer, it hangs there at ALSA. My workaround currently is to remove the pulseaudio package, then it's ok.

karlatsaic (krudnick) wrote :

I upgraded to 8.10 and have the exact same issue on a 32-bit Compaq Presario 2100 (circa 2003)

stu (sgeorge) wrote :

I'm on amd64 and same, I have an Asus xonar dx. After about 5 minutes I get something like "bad switch with amixer" and then after about another 5 minutes machine shuts down.

Same here with my Acer 5520G. Opened duplicate bug #285589 before finding this one. Weird bug.

J (jcastillob) wrote :

Same here with Intel 82801CA/CAM AC'97 Audio Controller, but I think the hang is network related: running "ifconfig wlan0 down" before shutdown allows the computer power off without any problem.

So, it looks like power off is blocked by a problem to "kill" wifi connection process. Could it be related in some way to network manager ?

http://changelogs.ubuntu.com/changelogs/pool/main/n/network-manager/network-manager_0.7~~svn20081015t224738-0ubuntu1/changelog

"* new upstream snapshot Wed 2008-10-15 22:47:38 +0000 (bzrrev 3641)
  - a few more follow up fixes for routing routing/subnet/vpn handling."

Could be the culprit here ?!

Insert
ifconfig wlan0 down
at the begin of /etc/init.d/alsa-utils to turn off wireless before shutdown alsa.

Lister (jojo-ditadres) wrote :

Same problem here on an AMD64 64bit system.
However, Network-manager is not installed and no wlan in use/availabe.

If I bring eth0 down before restarting I do not have to wait the 5 minutes for ALSA to shutdown.

Seems like it is not wifi or network-manager related...

Le Kien : your trick doesn't work for me.

Lister : laptop or fixed pc ?

If it is not wifi or network related, why does some people fix this bug by tweaking network connections ?

Lister (jojo-ditadres) wrote :

Fixed pc, a MSI K9N SLI, 6400+.
Tried the trick from Le Kien truc several times now with eth0 instead of wlan0 and it works everytime. If I don't use it, I have to wait a long time for a reboot.
So it does seem to be related to networking somehow.

Lister (jojo-ditadres) wrote :

btw, I do:
sudo ifconfig eth0 down
on the commandline, not via a line in /etc/init.d/alsa-utils.

bitstate (bitstate) wrote :

The fix with shuting down the network interface is confirmed. I experience the same problem with haning on alsa shutdown on a hp laptop with a usb 3g modem. But if i disconnect it using the network manager menu option ( below the list of available networks when left clicking on the network manager icon ) prior to shuting down the laptop it shuts down normally.

J (jcastillob) wrote :

The trick works inserting "ifconfig wlan0 down" (or the active network interface in use) at the begining of the stop) section of /etc/init.d/alsa-utils.
I'm sure it's not network-manager related, my laptop also hangs uninstalling the package and starting wifi via wicd.
Btw, if your alsa-mixer is always mute at system start, and does not remember the last settings, the trick also fixes it.

Well, it looks like it is related to network in a way.

I looked at var/log/syslog while trying to shutdown and when i asked for shutdown, I got this :

Oct 20 11:07:10 fred-laptop kernel: [ 214.557848] __ratelimit: 6 callbacks suppressed
Oct 20 11:07:10 fred-laptop kernel: [ 214.557875] compiz.real[5938]: segfault at 120 ip 000000000041024e sp 00007fff3fabc160 error 4 in compiz.real[400000+3b000]
Oct 20 11:07:11 fred-laptop init: tty4 main process (4660) killed by TERM signal
Oct 20 11:07:11 fred-laptop init: tty5 main process (4661) killed by TERM signal
Oct 20 11:07:11 fred-laptop init: tty2 main process (4667) killed by TERM signal
Oct 20 11:07:11 fred-laptop init: tty3 main process (4669) killed by TERM signal
Oct 20 11:07:11 fred-laptop init: tty6 main process (4670) killed by TERM signal
Oct 20 11:07:11 fred-laptop init: tty1 main process (5729) killed by TERM signal
Oct 20 11:07:11 fred-laptop NetworkManager: <info> (wlan0): device state change: 8 -> 3
Oct 20 11:07:11 fred-laptop NetworkManager: <info> (wlan0): deactivating device (reason: 38).
Oct 20 11:07:11 fred-laptop NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 6104
Oct 20 11:07:11 fred-laptop kernel: [ 215.153613] wlan0: disassociating by local choice (reason=3)
Oct 20 11:07:11 fred-laptop kernel: [ 215.179213] wlan0: authenticate with AP 00:1a:6b:1b:15:e5
Oct 20 11:07:11 fred-laptop kernel: [ 215.186362] wlan0: authenticated
Oct 20 11:07:11 fred-laptop kernel: [ 215.186374] wlan0: associate with AP 00:1a:6b:1b:15:e5
Oct 20 11:07:11 fred-laptop kernel: [ 215.188443] wlan0: RX AssocResp from 00:1a:6b:1b:15:e5 (capab=0x411 status=0 aid=1)
Oct 20 11:07:11 fred-laptop kernel: [ 215.188449] wlan0: associated
Oct 20 11:07:11 fred-laptop NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess
Oct 20 11:07:11 fred-laptop avahi-daemon[4926]: Withdrawing address record for 192.168.1.12 on wlan0.
Oct 20 11:07:11 fred-laptop avahi-daemon[4926]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.12.
Oct 20 11:07:11 fred-laptop avahi-daemon[4926]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct 20 11:07:11 fred-laptop kernel: [ 215.205718] wlan0: disassociating by local choice (reason=3)

And a little later :

[Bluetooth shutdown]
Oct 20 11:07:16 fred-laptop kernel: [ 219.787126] Bluetooth: RFCOMM ver 1.10
Oct 20 11:07:16 fred-laptop avahi-daemon[4926]: Got SIGTERM, quitting.
Oct 20 11:07:17 fred-laptop exiting on signal 15

And when I took a screenshot, it was blocked on acpi exiting.

So I'm kinda lost. Anyway, I'm adding the log I have.

Same problem here on a fixed Pc Dell Vostro 200, audio Intel. The "shutting down alsa" takes several minutes before halt the pc. At th startup instead, some times alsa won't start.

astroman (astrosousa) wrote :

Hi,
sorry for the late reply.

I send in attachment the log required, please take note that i made all the updates.
The freeze is now less frequent, and i notice that disabling the network will prevent the freeze to happen.
 This
I have also a diferent bug. the nm-applet do not show up and i had to install a previous version to apear in order to disable the network through it.

Another thing that may help, or not, my boot on the kernel only operates using the nohz=off option.
I notice that Ubuntu is quite slow opening software and operating it. This is strange since the computer his new:

Chipset:
• SiS© 671DX + SiS968
Intel Pentium Dual Core T2390 1.86Mhz
Nvidia 9300M GS 256Mb
4Gb RAM

Rodney Gordon II (meff) wrote :

Confirming that this bug still exists via asus-utils 1.0.17-0ubuntu2 on a SB Audigy2.

still exist on a fresh update. Less that 10 days to fix it...

varanus (bobiras12) wrote :

i had the same problem with alsa at shutting down, i had to wait 3-4 minutes to reboot or shutdown. i tried the same thing with the network manager. Before rebooting/shutting down pc i switched to offline mode from the network manager and it shut/rebooted normally without any problems.

frapell (frapell) wrote :

This started to happen to me a couple of days ago... i'm using 8.10 (amd64).
anyway, i changed the first line of the /etc/init.d/alsa-utils file to:
#!/bin/sh -x

so i noticed when "freezing" at shutdown, actually does not freeze, is doing something... now i don't know if all that, is logged somewhere, but i tried doing a sudo /etc/init.d/alsa-utils stop and copying the output to this file i'm attaching.

The part that goes from line 75 to line 190 is the part that takes forever... at least when the system is going to reboot (or shutdown)... i'm seeing each part of that (Master, PCM, Synth, etc) that takes like 30 seconds. (when doing /etc/init.d/alsa-utils stop didn't happened, ie it took like 5 seconds to finish everything)

ok, hope this helps...

Regards,
Franco

Daniel T Chen (crimsun) on 2008-10-22
Changed in alsa-utils:
assignee: nobody → crimsun
importance: Undecided → Medium
status: Confirmed → Incomplete
Changed in linux:
status: New → Invalid
Daniel T Chen (crimsun) on 2008-10-23
Changed in alsa-utils:
status: Incomplete → In Progress
Daniel T Chen (crimsun) on 2008-10-23
Changed in alsa-utils:
status: In Progress → Confirmed
Daniel T Chen (crimsun) on 2008-10-25
Changed in network-manager:
assignee: crimsun → nobody
Luke Faraone (lfaraone) on 2008-10-26
Changed in network-manager:
status: Confirmed → Triaged
Alexander Sack (asac) on 2008-10-28
Changed in network-manager:
status: Triaged → Invalid
Alexander Sack (asac) on 2008-10-28
Changed in network-manager:
status: New → Invalid
Daniel T Chen (crimsun) on 2008-10-29
Changed in pulseaudio:
status: New → Invalid
Changed in linux:
assignee: nobody → crimsun
status: Invalid → Incomplete
276 comments hidden view all 322 comments

Created attachment 322450
Add reboot notifier to intel8x0 driver

Davide, could you test the proposed patch for this issue or you need a full test kernel?

Better to get a full kernel if you can.

(In reply to comment #19)
> Davide, could you test the proposed patch for this issue or you need a full
> test kernel?

I have too much work to do, and can't set up a build environment on my machine by now...

Daniel T Chen (crimsun) on 2008-11-21
Changed in alsa-utils:
status: New → Invalid
Daniel T Chen (crimsun) on 2008-11-21
Changed in linux:
importance: Undecided → Medium
status: Incomplete → Triaged
Changed in linux:
status: Unknown → Confirmed
status: Unknown → In Progress
Changed in alsa-utils:
status: Invalid → New
Changed in pulseaudio:
status: Invalid → New
Daniel T Chen (crimsun) on 2008-11-25
Changed in linux:
importance: Medium → Undecided
status: Triaged → Invalid
Daniel T Chen (crimsun) on 2008-11-25
Changed in pulseaudio:
status: New → Invalid
Changed in alsa-utils:
assignee: nobody → crimsun
importance: Undecided → Medium
status: New → In Progress
Daniel T Chen (crimsun) on 2008-11-25
description: updated
Daniel T Chen (crimsun) on 2008-11-25
description: updated
Changed in alsa-utils:
status: In Progress → Fix Released
Martin Pitt (pitti) on 2008-11-26
Changed in linux:
status: New → Invalid
Changed in alsa-utils:
status: New → Fix Committed
Changed in network-manager:
status: New → Invalid
status: Invalid → Fix Committed
Changed in pulseaudio:
status: New → Invalid
Changed in network-manager:
status: Fix Committed → Invalid
Changed in pulseaudio:
status: Invalid → Fix Committed
Changed in network-manager:
status: Invalid → Fix Committed
status: Fix Committed → Invalid
Martin Pitt (pitti) on 2008-11-26
Changed in pulseaudio:
status: Fix Committed → Invalid

The problem seems fixed in FC10.

If somebody else had this issue and tried fc10, please report his results.

OK, marking as fixed for F10. Thanks.

Changed in linux:
status: In Progress → Fix Released
38 comments hidden view all 322 comments
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package alsa-utils - 1.0.17-0ubuntu3

---------------
alsa-utils (1.0.17-0ubuntu3) intrepid-proposed; urgency=low

  * debian/init: Set PULSE_INTERNAL=0 to prevent PulseAudio from
    being inspected for invocations of alsactl and amixer. Fixes
    hangs attempting to (re)store mixer element values as
    reported in LP: #274995.

 -- Daniel T Chen <email address hidden> Tue, 25 Nov 2008 07:56:08 -0500

Changed in alsa-utils:
status: Fix Committed → Fix Released
Robb Topolski (funchords) wrote :

@Jens -- whatever DNS server you are using while connected to VPN probably doesn't quickly return an answer for a AAAA query for "localhost," while your non-VPN DNS does. alsa-utils 1.0.17-0ubuntu3 should avoid it in all cases. Also, see below.

@kungmidas -- when I change my DNS to some bogus address, I see this delay. When I use good DNS servers, the delay is gone. alsa-utils 1.0.17-0ubuntu3 should avoid it in all cases. Also, see below.

@all, please see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/274995/comments/273 -- if you were seeing a delay -- even if it is fixed now, you probably also have or had that separate network configuration bug 301430 that allows DNS queries for localhost -- however generated -- to escape your local machine and network.

cevatcethun (cevatceyhun) wrote :

@aschuring

Sorry for the late reply. I have just updated to 8.10. The problem continues.

Have you applied the latest updates? The problem is fixed here.

2008/12/5 cevatcethun <email address hidden>

> @aschuring
>
> Sorry for the late reply. I have just updated to 8.10. The problem
> continues.
>
> --
> MASTER storing ALSA mixer element values during shutdown hangs
> nondeterministically due to internal alsa-plugins pulse check
> https://bugs.launchpad.net/bugs/274995
> You received this bug notification because you are a direct subscriber
> of the bug.
>

cevatcethun (cevatceyhun) wrote :

@Alan

No I didn't apply the updates listed as "proposed" if this is what you asked. But I did install the regular updates.

Catching up with the posts.. I added "localhost" term to my /etc/hosts file which is mentioned above (bug 301430). I'm not sure the problem is completely gone but last few restarts/shutdowns were OK.

Kurtismonger (kurtismonger) wrote :

Some of the comments suggest adding ifconfig eth0 down, which did not work for my Acer Travelmate 4500. However I found one that suggested ifconfig eth0 shutdown, which cleared up the problem after I added a line for each network interface. I don't know enough about it to know if one or both are correct (down vs shutdown), but figured somebody else might find this useful.

Kurtismonger (kurtismonger) wrote :

I spoke to soon. On the next shutdown the problem returned. I'm running a fresh install of 8.10 downloaded on 11/23. I've tried all the suggested fixes except the -proposed updates thing, as I don't know how to do that. I was going to remove PulseAudio, but doing so from Synaptic also removes Ubuntu Desktop. My alsa-utils version is 1.0.17-0ubuntu3.

Robb Topolski (funchords) wrote :

Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Kurtismonger (kurtismonger) wrote :

Ok. So I've added alsa-utils-proposed and pulseaudio-proposed and I'm still getting the acpid: exiting issue every single time I shutdown or restart.

Charles Profitt (cprofitt) wrote :

Kurtismonger

What laptop or desktop are you using? What is your hardware?

Kurtismonger (kurtismonger) wrote :

Machine Specs:
Acer TravelMate 4500/Ubuntu 8.10
Linux 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
CPU: Intel Pentium M processor 1.60GHz
Memory: 512MiB
Display: 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

Jun Inoue (jun-lambda) wrote :

I'm reopening this bug because I'm running into this problem despite the fix dated 2008-12-03. Please let me know if opening a new one is more appropriate.
I'm using the amd64 version of Xubuntu 9.0.4 (default install) on a Sony Vaio VGN-G2. The system stalls during reboot/halt. For reboot, it shows the following error message:

nm-dispatcher.action: Caught signal 15, shutting down...
acpid: exiting

nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/net_00_1a_80_d6_06_5a)
nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /oorg/freedesktop/Hal/devices/net_00_1f_3c_85_77_4a)

For halt, the message is just "acpi: exiting\n\n".

The system is still responsive in the sense that the Enter key advances the cursor, and the laptop blanks the screen after inactivity. The problem goes away if I add the link K88NetworkManager to rc0.d and rc6.d.

I got the number 88 from Debian's network-manager package.

Changed in network-manager:
status: Invalid → New
Jun Inoue (jun-lambda) wrote :

Revert. I meant to change the status for network-manager (Ubuntu), not NetworkManager.

Changed in network-manager:
status: New → Invalid

On Tue, Jun 16, 2009 at 10:17 PM, Jun Inoue<email address hidden> wrote:
> Please let me know if opening a new one is more appropriate.

Generally it is, I'd recommend that, unless someone else states
otherwise. When you do, please set this back to Invalid but feel free
to leave a comment with your new bug here for reference!

Jun Inoue (jun-lambda) wrote :

I'm reopening this bug because it reproduces with the latest release, which seems to have the fix released on 2008-12-03. I'm running a default install of Xubuntu 9.0.4 on a Sony Vaio VGN-G2.

Problem: the system hangs during reboot or halt if there is an active wireless connection. During reboot, I get the following message

 * Stopping anac(h)ronistic cron anacron
acpid: exiting

nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /or/freedesktop/Hal/devices/net_00_1a_80_d6_06_5a)
nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/net_00_1f_3c_85_77_4a)
nm-dispatcher.action: Caught signal 15, shutting down...

The first line is sometimes different, but I can't seem to get the alternative message at the moment.
The system makes no further progress. For halt, the message is just "acpid: exiting\n\n", or sometimes it's just blank.
The system is not completely frozen; the Enter key advances the cursor and the console is blanked after inactivity (and lights up again in response to a keystroke). Ctrl+Alt+Delete seems to be registering---it doesn't cause the system to make progress but after repeatedly pressing the combination, I see "init: control-alt-delete respawning too fast, stopped".

The reproducibility is not 100% although it's fairly high, well over 50% (subjectively; I didn't acutally count).

The problem goes away if I link /etc/init.d/NetworkManager from rc0.d and rc6.d. I used the prefix K88 following Debian, but perhaps a different number is more appropriate for Ubuntu.

Changed in network-manager (Ubuntu):
status: Invalid → New
Jun Inoue (jun-lambda) wrote :

Revert. I filed my report under #388291 following Michael Rooney's kind advice.
...Sorry to spam everyone with status changes.

Changed in network-manager (Ubuntu):
status: New → Invalid
Changed in linux (Gentoo Linux):
status: Confirmed → Fix Released
Changed in linux (Gentoo Linux):
importance: Unknown → Medium
Changed in linux (Fedora):
importance: Unknown → Medium
Displaying first 40 and last 40 comments. View all 322 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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