From: Michael Catanzaro <mcatanzaro@redhat.com>
To: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Harsha Priya <harshapriya.n@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: [REGRESSION] "ALSA: HDA: Early Forbid of runtime PM" broke my laptop's internal audio
Date: Thu, 28 Jan 2021 16:39:50 -0600 [thread overview]
Message-ID: <EM1ONQ.OL5CFJTBEBBW@redhat.com> (raw)
Hi,
On my System76 Gazelle Pro (gazp9) laptop, internal audio broke after
upgrading to kernel 5.10.
The laptop's speakers produce no sound. Audio from headphones still
works fine. A quick test is to visit GNOME System Settings -> Sound ->
Output, select Test, click Front Left or Front Right and notice there
is no sound. I tested a mainline kernel revision from yesterday
(5.11-rc5+) and the regression is not yet fixed. I bisected the
regression to "ALSA: HDA: Early Forbid of runtime PM":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0645daf16101bb9a6d87598c17e9a8b7bd60ea7
I created a downstream bug report here, including some bits from dmesg
that may or may not be relevant in comment #2:
https://bugzilla.redhat.com/show_bug.cgi?id=1918933
Audio devices:
$ lspci | grep -i audio
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset
High Definition Audio Controller (rev 05)
OS: Fedora 33
I'm happy to provide any additional required info or test patches if
you CC me, since I'm not a kernel developer and am not subscribed to
these lists. Thanks.
next reply other threads:[~2021-01-29 15:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 22:39 Michael Catanzaro [this message]
2021-01-29 1:37 ` [REGRESSION] "ALSA: HDA: Early Forbid of runtime PM" broke my laptop's internal audio N, Harshapriya
2021-01-29 1:37 ` N, Harshapriya
2021-01-29 8:19 ` Takashi Iwai
2021-01-29 15:02 ` Michael Catanzaro
2021-01-29 15:06 ` Takashi Iwai
2021-01-29 15:27 ` Michael Catanzaro
2021-01-29 15:30 ` Michael Catanzaro
2021-01-29 16:12 ` Michael Catanzaro
2021-01-29 16:17 ` Takashi Iwai
2021-01-29 16:17 ` Takashi Iwai
2021-01-29 17:24 ` Michael Catanzaro
2021-01-29 17:24 ` Michael Catanzaro
2021-01-29 18:56 ` Takashi Iwai
2021-01-29 18:56 ` Takashi Iwai
2021-08-14 14:02 ` 藍挺瑋
2021-08-14 14:02 ` 藍挺瑋
2021-08-15 9:20 ` Takashi Iwai
2021-08-15 9:20 ` Takashi Iwai
2021-08-16 16:57 ` 藍挺瑋
2021-08-16 16:57 ` 藍挺瑋
2021-08-17 5:25 ` Takashi Iwai
2021-08-17 5:25 ` Takashi Iwai
2021-02-01 4:24 ` Erich Ritz
2021-02-01 4:24 ` Erich Ritz
2021-02-01 13:57 ` Greg KH
2021-02-01 13:57 ` Greg KH
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=EM1ONQ.OL5CFJTBEBBW@redhat.com \
--to=mcatanzaro@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=harshapriya.n@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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.