From: Kailang <kailang@realtek.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Joseph C. Sible" <josephcsible@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: RE: Fwd: [Bug 217440] New: ALC236 audio disappears from HP 15z-fc000 on warm boot
Date: Fri, 9 Jun 2023 07:04:15 +0000 [thread overview]
Message-ID: <0990300d759846d890de9c92fcad9a9d@realtek.com> (raw)
In-Reply-To: <87h6rhcef2.wl-tiwai@suse.de>
Hi Joseph,
echo 0 > /sys/module/snd_hda_intel/parameters/power_save
Could you give it a try? Then got dump also.
If it passed, please test my two patches also. Then get dump again.
This was AMD chipset. I hadn't seen this issue on INTEL platform.
Thanks.
> -----Original Message-----
> From: Takashi Iwai <tiwai@suse.de>
> Sent: Friday, June 9, 2023 2:56 PM
> To: Kailang <kailang@realtek.com>
> Cc: Joseph C. Sible <josephcsible@gmail.com>; Bagas Sanjaya
> <bagasdotme@gmail.com>; regressions@lists.linux.dev; perex@perex.cz;
> tiwai@suse.com; alsa-devel@alsa-project.org
> Subject: Re: Fwd: [Bug 217440] New: ALC236 audio disappears from HP
> 15z-fc000 on warm boot
>
>
> External mail.
>
>
>
> On Fri, 09 Jun 2023 05:04:29 +0200,
> Kailang wrote:
> >
> > Hi Takashi,
> >
> > ALC236 works normally.
> > But codec register can't show it. (it shows "Invalid AFG subtree")
> > Could you know why?
>
> It's the call of snd_hda_get_subnodes(), i.e. snd_hdac_get_subnodes(), which
> simply reads the raw parameter value (uncached)
> AC_PAR_NODE_COUNT:
>
> int snd_hdac_get_sub_nodes(struct hdac_device *codec, hda_nid_t nid,
> hda_nid_t *start_id) {
> unsigned int parm;
>
> parm = snd_hdac_read_parm_uncached(codec, nid,
> AC_PAR_NODE_COUNT);
> if (parm == -1) {
> *start_id = 0;
> return 0;
> }
> *start_id = (parm >> 16) & 0x7fff;
> return (int)(parm & 0x7fff);
> }
>
> So it means the read of this parameter failed.
>
> I suppose this is under the power-save, and it might be some timing issue?
> What if you disable the codec power saving? The easiest way would be to
> pass
> echo 0 > /sys/module/snd_hda_intel/parameters/power_save
>
>
> thanks,
>
> Takashi
>
> >
> > BR,
> > Kailang
> > > -----Original Message-----
> > > From: Joseph C. Sible <josephcsible@gmail.com>
> > > Sent: Thursday, June 8, 2023 10:43 PM
> > > To: Kailang <kailang@realtek.com>
> > > Cc: Takashi Iwai <tiwai@suse.de>; Bagas Sanjaya
> > > <bagasdotme@gmail.com>; regressions@lists.linux.dev; perex@perex.cz;
> > > tiwai@suse.com; alsa-devel@alsa-project.org
> > > Subject: Re: Fwd: [Bug 217440] New: ALC236 audio disappears from HP
> > > 15z-fc000 on warm boot
> > >
> > >
> > > External mail.
> > >
> > >
> > >
> > > On Thu, Jun 8, 2023 at 2:32 AM Kailang <kailang@realtek.com> wrote:
> > > >
> > > > Could you use your patch to dump codec info again?
> > > > I want to check it will also show "invalid AFG subtree".
> > >
> > > Okay, here's the same command's output again, this time from under
> > > the kernel with my patch that does fix the problem. It does also
> > > show "invalid AFG subtree".
> > >
> > > Thanks,
> > >
> > > Joseph C. Sible
> > >
> > > ------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2023-06-09 7:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-217440-225600@https.bugzilla.kernel.org/>
2023-05-13 19:52 ` Fwd: [Bug 217440] New: ALC236 audio disappears from HP 15z-fc000 on warm boot Joseph C. Sible
2023-05-14 5:41 ` Bagas Sanjaya
2023-05-14 6:46 ` Joseph C. Sible
2023-05-14 7:35 ` Takashi Iwai
2023-05-14 21:48 ` Joseph C. Sible
2023-05-15 2:23 ` Bagas Sanjaya
2023-05-15 3:03 ` Joseph C. Sible
2023-05-15 13:39 ` Takashi Iwai
2023-05-18 5:44 ` Kailang
2023-05-24 10:16 ` Takashi Iwai
2023-05-25 9:21 ` Kailang
2023-05-25 10:17 ` Takashi Iwai
2023-05-26 8:09 ` Kailang
2023-05-26 14:58 ` Joseph C. Sible
2023-06-05 7:14 ` Takashi Iwai
2023-06-06 6:02 ` Joseph C. Sible
2023-06-06 6:54 ` Kailang
2023-06-07 5:47 ` Joseph C. Sible
2023-06-07 7:05 ` Kailang
2023-06-07 18:36 ` Joseph C. Sible
2023-06-08 2:48 ` Kailang
2023-06-08 4:08 ` Joseph C. Sible
2023-06-08 6:28 ` Kailang
2023-06-08 6:32 ` Kailang
2023-06-08 14:43 ` Joseph C. Sible
2023-06-09 3:04 ` Kailang
2023-06-09 6:56 ` Takashi Iwai
2023-06-09 7:04 ` Kailang [this message]
2023-06-09 7:34 ` Joseph C. Sible
2023-06-09 8:12 ` Takashi Iwai
2023-06-09 8:34 ` Takashi Iwai
2023-06-09 16:47 ` Joseph C. Sible
2023-06-10 7:09 ` Takashi Iwai
2023-06-10 17:41 ` Joseph C. Sible
2023-06-11 7:36 ` Takashi Iwai
2023-06-24 1:36 ` Joseph C. Sible
2023-06-25 9:42 ` Takashi Iwai
2023-07-04 8:38 ` Kailang
2023-07-04 8:45 ` Takashi Iwai
2023-07-13 8:25 ` Kailang
2023-07-14 1:11 ` Joseph C. Sible
2023-07-14 2:46 ` Kailang
2023-07-14 5:58 ` Takashi Iwai
2023-07-31 16:14 ` Takashi Iwai
2023-08-04 14:34 ` Joseph C. Sible
2023-08-15 8:08 ` Kailang
2023-08-15 9:08 ` Takashi Iwai
2023-08-16 12:22 ` Takashi Iwai
2023-08-02 10:49 ` Linux regression tracking #update (Thorsten Leemhuis)
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=0990300d759846d890de9c92fcad9a9d@realtek.com \
--to=kailang@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=bagasdotme@gmail.com \
--cc=josephcsible@gmail.com \
--cc=perex@perex.cz \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.com \
--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