From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002123]: Power Management is broken following changes from 1.0.10 to 1.0.11.x versions
Date: Sun, 14 May 2006 00:27:59 +0200 [thread overview]
Message-ID: <3ed240604ed0534136b53bfc0a1bf7b0@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2123>
======================================================================
Reported By: jovial
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 2123
Category: PCI - hda-intel
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Distribution: gentoo
Kernel Version: 2.6.16
======================================================================
Date Submitted: 05-13-2006 17:37 CEST
Last Modified: 05-14-2006 00:27 CEST
======================================================================
Summary: Power Management is broken following changes from
1.0.10 to 1.0.11.x versions
Description:
I had linux kernel 2.6.15 on my machine (with alsa version 1.0.10).
I could place my laptop on standby while playing music, and onced resumed
the playback would also continue..... proper functionality and power
management.
following an upgrade to kernel 2.6.16 with latest patches (includes alsa
1.0.11-rc4), the power management does not function correctly.
basically, i have to restart the alsasound service after resume to have
any sound again.
======================================================================
----------------------------------------------------------------------
jovial - 05-14-06 00:11
----------------------------------------------------------------------
I installed kernel 2.6.17-rc4, but now my standby feature is broken.
is there anyway to test the alsa driver's power management scheme without
actually doing the standby procedure??
----------------------------------------------------------------------
rlrevell - 05-14-06 00:27
----------------------------------------------------------------------
It sounds like an upstream kernel bug. What are the exact symptoms (dmesg
output, etc) when you try to suspend?
Issue History
Date Modified Username Field Change
======================================================================
05-13-06 17:37 jovial New Issue
05-13-06 17:37 jovial Distribution => gentoo
05-13-06 17:37 jovial Kernel Version => 2.6.16
05-13-06 17:41 jovial Note Added: 0009797
05-13-06 18:27 rlrevell Note Added: 0009798
05-14-06 00:11 jovial Note Added: 0009801
05-14-06 00:27 rlrevell Note Added: 0009802
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-05-13 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 22:27 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-22 20:49 [ALSA - driver 0002123]: Power Management is broken following changes from 1.0.10 to 1.0.11.x versions bugtrack
2006-05-15 11:15 bugtrack
2006-05-15 10:11 bugtrack
2006-05-14 3:16 bugtrack
2006-05-14 0:42 bugtrack
2006-05-14 0:32 bugtrack
2006-05-13 22:11 bugtrack
2006-05-13 16:27 bugtrack
2006-05-13 15:41 bugtrack
2006-05-13 15:37 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ed240604ed0534136b53bfc0a1bf7b0@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.