Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Joseph C. Sible" <josephcsible@gmail.com>
Cc: Kailang <kailang@realtek.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, 09 Jun 2023 10:34:59 +0200	[thread overview]
Message-ID: <874jnhc9u4.wl-tiwai@suse.de> (raw)
In-Reply-To: <878rctcavz.wl-tiwai@suse.de>

On Fri, 09 Jun 2023 10:12:16 +0200,
Takashi Iwai wrote:
> 
> On Fri, 09 Jun 2023 09:34:37 +0200,
> Joseph C. Sible wrote:
> > 
> > On Fri, Jun 9, 2023 at 3:04 AM Kailang <kailang@realtek.com> wrote:
> > >
> > > 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.
> > 
> > I ran that command under the kernel with my patch and then got an
> > alsa-info dump again, and it still said "Invalid AFG subtree". The
> > full result is attached as alsa-info-1.txt.
> > 
> > I then added snd_hda_intel.power_save=0 to the kernel command line and
> > tried under the kernel with your patches again. No change here either:
> > still "Invalid AFG subtree", and upon a warm boot, it still breaks.
> > Attached from this test are alsa-info-2.txt (cold boot) and
> > alsa-info-3.txt (warm boot).
> 
> Thanks.  It's puzzling.
> 
> The power setting of AFG looks already unusual:
> 
> State of AFG node 0x01:
>   Power states:  D0 D2 (null) (null) (null) (null) (null) (null) (null)
>   Power: setting=UNKNOWN, actual=D0, Clock-stop-OK, Setting-reset
> 
> So apparently the codec isn't ready yet for accessing.
> 
> But, the fact that the codec got parsed (hence you see the parsed
> results in dmesg) means that this subtree call could succeed at the
> beginning.
> 
> When you load snd-hda-intel module with "model=,generic" option (the
> command is intentional), does the codec content show up?

Also, assuming it being some timing issue, adding the delay forcibly
like below has any influence on the AFG error?


Takashi

--- a/sound/pci/hda/hda_proc.c
+++ b/sound/pci/hda/hda_proc.c
@@ -792,6 +792,7 @@ static void print_codec_info(struct snd_info_entry *entry,
 	snd_iprintf(buffer, "State of AFG node 0x%02x:\n", fg);
 	print_power_state(buffer, codec, fg);
 
+	msleep(100); // XXX
 	nodes = snd_hda_get_sub_nodes(codec, fg, &nid);
 	if (! nid || nodes < 0) {
 		snd_iprintf(buffer, "Invalid AFG subtree\n");

  reply	other threads:[~2023-06-09  8:36 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
2023-06-09  7:34                                                   ` Joseph C. Sible
2023-06-09  8:12                                                     ` Takashi Iwai
2023-06-09  8:34                                                       ` Takashi Iwai [this message]
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=874jnhc9u4.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bagasdotme@gmail.com \
    --cc=josephcsible@gmail.com \
    --cc=kailang@realtek.com \
    --cc=perex@perex.cz \
    --cc=regressions@lists.linux.dev \
    --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