From: Valdis.Kletnieks@vt.edu
To: Hui Wang <hui.wang@canonical.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] linux-next - strange audio bug
Date: Thu, 02 Apr 2015 22:21:40 -0400 [thread overview]
Message-ID: <4518.1428027700@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 03 Apr 2015 08:44:12 +0800." <551DE25C.6020201@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Fri, 03 Apr 2015 08:44:12 +0800, Hui Wang said:
> It sounds like the suspend or resume of power management introduces this
> problem. Probably you could reproduce this problem very soon just
> repeatedly suspend and resume the system.
I don't do suspend on this laptop, I poweroff and reboot when I get
wherever I'm going.
However... device-level power management? Hmm.. I *do* remember that
each time I found it dead, I was coming back to my laptop from doing something
else, so the sound would have been idle....
commit c4c2533f802d6877803c4d778def43d8a122f27b
Author: Takashi Iwai <tiwai@suse.de>
Date: Tue Mar 3 17:22:12 2015 +0100
ALSA: hda - Fix possible runtime PM refcount unbalance
That landed in next-20150324 - which is broken for me.
Looks worth trying a revert before I bisect, thanks for the hint, will
report back (probably tomorrow) on what happens...
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2015-04-03 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 0:34 linux-next - strange audio bug Valdis Kletnieks
2015-04-03 0:44 ` Hui Wang
2015-04-03 2:21 ` Valdis.Kletnieks [this message]
2015-04-04 12:37 ` Takashi Iwai
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=4518.1428027700@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=alsa-devel@alsa-project.org \
--cc=hui.wang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox