ubuntustudio-bugs team mailing list archive

[Bug Watch Updater <274995@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 24 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=203930.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2006-08-24T15:56:52+00:00 Davide wrote:

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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/0

------------------------------------------------------------------------
On 2006-09-05T15:56:02+00:00 David wrote:

Changing to proper owner, kernel-maint.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/1

------------------------------------------------------------------------
On 2006-10-16T21:11:48+00:00 Dave wrote:


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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/2

------------------------------------------------------------------------
On 2006-10-17T12:43:34+00:00 Davide wrote:

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).

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/3

------------------------------------------------------------------------
On 2007-10-29T18:52:51+00:00 Stefan wrote:

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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/4

------------------------------------------------------------------------
On 2007-12-31T03:39:42+00:00 Jon wrote:

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?

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/5

------------------------------------------------------------------------
On 2007-12-31T03:40:19+00:00 Jon wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/6

------------------------------------------------------------------------
On 2008-01-08T13:57:35+00:00 Davide wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/7

------------------------------------------------------------------------
On 2008-01-16T20:43:47+00:00 Christopher wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/8

------------------------------------------------------------------------
On 2008-01-17T13:33:23+00:00 Davide wrote:

Created attachment 291992
dmidecode, lspci and dmesg output

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/9

------------------------------------------------------------------------
On 2008-01-17T13:34:53+00:00 Davide wrote:

Comment on attachment 291992
dmidecode, lspci and dmesg output

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/10

------------------------------------------------------------------------
On 2008-01-17T15:28:40+00:00 Christopher wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/11

------------------------------------------------------------------------
On 2008-01-18T11:11:15+00:00 Davide wrote:

Created attachment 292123
lsmod

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/12

------------------------------------------------------------------------
On 2008-01-18T11:12:41+00:00 Davide wrote:

Created attachment 292124
/etc/modprobe.conf

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/13

------------------------------------------------------------------------
On 2008-01-18T11:21:02+00:00 Davide wrote:

(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.


Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/274995/comments/14

------------------------------------------------------------------------
On 2008-01-18T12:10:38+00:00 Christopher wrote:

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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/15

------------------------------------------------------------------------
On 2008-01-18T13:48:22+00:00 Davide wrote:

(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... :)


Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/274995/comments/16

------------------------------------------------------------------------
On 2008-05-18T10:25:13+00:00 Davide wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/17

------------------------------------------------------------------------
On 2008-11-04T17:09:22+00:00 Jaroslav wrote:

Created attachment 322450
Add reboot notifier to intel8x0 driver

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/180

------------------------------------------------------------------------
On 2008-11-04T17:11:16+00:00 Jaroslav wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/181

------------------------------------------------------------------------
On 2008-11-04T18:20:57+00:00 Davide wrote:

Better to get a full kernel if you can.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/182

------------------------------------------------------------------------
On 2008-11-06T14:49:40+00:00 Davide wrote:

(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...

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/191

------------------------------------------------------------------------
On 2008-11-29T15:12:55+00:00 Davide wrote:

The problem seems fixed in FC10.

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/294

------------------------------------------------------------------------
On 2008-11-29T22:03:50+00:00 Jaroslav wrote:

OK, marking as fixed for F10. Thanks.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/274995/comments/296


** Changed in: linux (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to alsa-utils in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/274995

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

Status in NetworkManager:
  Invalid
Status in alsa-utils package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid
Status in alsa-utils source package in Intrepid:
  Fix Released
Status in linux source package in Intrepid:
  Invalid
Status in network-manager source package in Intrepid:
  Invalid
Status in pulseaudio source package in Intrepid:
  Invalid
Status in linux package in Fedora:
  Fix Released
Status in linux package in Gentoo Linux:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/274995/+subscriptions