From: Takashi Iwai <tiwai@suse.de>
To: Scott Branden <scott.branden@broadcom.com>
Cc: perex@perex.cz, tiwai@suse.com,
ranjani.sridharan@linux.intel.com, broonie@kernel.org,
kai.vehmanen@linux.intel.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, regressions@leemhuis.info
Subject: Re: 5.15 Linux Regression in sound hda
Date: Wed, 10 Nov 2021 15:33:08 +0100 [thread overview]
Message-ID: <s5hpmr86py3.wl-tiwai@suse.de> (raw)
In-Reply-To: <063e2397-7edb-5f48-7b0d-618b938d9dd8@broadcom.com>
On Tue, 09 Nov 2021 22:12:30 +0100,
Scott Branden wrote:
>
> I'm reporting a new WARN_ON in sound/hda/hdac_bus.c that was not
> present in 5.15. Sorry, I don't have time to bisect this right now
> but report is below.
>
> dmesg in 5.14 kernel was:
> snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops 0xffffffffaa2ac520)
> GACT probability on
> Mirror/redirect action on
> Simple TC action Loaded
> u32 classifier
> Performance counters on
> input device check on
> Actions configured
> hdaudio hdaudioC0D0: Unable to bind the codec
> hdaudio hdaudioC0D2: Unable to bind the codec
>
> dmesg in 5.15 kernel produces WARN_ON in sound/hda/hdac_bus.c
> snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops 0xffffffffad8b02a0)
> GACT probability on
> Mirror/redirect action on
> Simple TC action Loaded
> u32 classifier
> Performance counters on
> input device check on
> Actions configured
> snd_hda_intel 0000:00:1f.3: Cannot probe codecs, giving up
> Initializing XFRM netlink socket
> ------------[ cut here ]------------
> NET: Registered PF_INET6 protocol family
> WARNING: CPU: 14 PID: 186 at sound/hda/hdac_bus.c:73
This indicates the leftover codecs on the bus, and it's likely
triggered by the recent change to allow retrying the codec probes.
Did this HD-audio stuff work at all before 5.15? The codec bind error
itself shouldn't be brought by that change.
The warning itself can be solved by the patch below, I suppose
(note: totally untested!)
thanks,
Takashi
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -2327,7 +2327,8 @@ static int azx_probe_continue(struct azx *chip)
out_free:
if (err < 0) {
- azx_free(chip);
+ pci_set_drvdata(pci, NULL);
+ snd_card_free(chip->card);
return err;
}
next prev parent reply other threads:[~2021-11-10 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 21:12 Scott Branden
2021-11-10 14:33 ` Takashi Iwai [this message]
2021-11-10 18:53 ` Scott Branden
2021-11-10 19:45 ` 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=s5hpmr86py3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=ranjani.sridharan@linux.intel.com \
--cc=regressions@leemhuis.info \
--cc=scott.branden@broadcom.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome