Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ruslan Nikolaev <nruslan_devel@yahoo.com>
To: "kailang@realtek.com" <kailang@realtek.com>,
	Takashi Iwai <tiwai@suse.de>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"tiwai@suse.com" <tiwai@suse.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"sashal@kernel.org" <sashal@kernel.org>,
	"perex@perex.cz" <perex@perex.cz>
Subject: Re: [Bug 220109] New: Audio disappears on HP 15-fc000 after warm boot again (ALC256 code path)
Date: Tue, 13 May 2025 04:36:40 +0000 (UTC)	[thread overview]
Message-ID: <946767975.787038.1747111000631@mail.yahoo.com> (raw)
In-Reply-To: <87o6vxuauk.wl-tiwai@suse.de>

Takashi and Kailang,

I did a few additional experiments. Here is what I found:

1. If I connect headphones and ALWAYS keep them connected, then sound does not disappear even after a warm reboot.

2. The moment I disconnect headphones and do a warm reboot, sound is not going to come back. At that point, connecting or disconnecting headphones, rebooting is not going to change anything (i.e., recover the sound) until I fully power off the computer.

3. After reverting the commit, the above problems disappear for speakers, and no additional issues with headphones are observed.

4. Whether I revert or do not revert the above-mentioned commit, the headphones are sometime flaky if I already have an application running that uses sound. I have to close that application, disconnect and connect headphones again. Otherwise, the speaker does not get disconnected.
The headphones seem to be even more flaky when NOT reverting the above commit - unless I booted the system with the headphones connected, the speaker will never get disconnected.

Sincerely,
Ruslan








On Monday, May 12, 2025 at 11:07:02 AM EDT, Takashi Iwai <tiwai@suse.de> wrote: 





On Mon, 12 May 2025 16:56:17 +0200,

Ruslan Nikolaev wrote:
> 
> Hi,
> 
> Forwarding my regression bug report for HP 15-fc000 / ALC236 (ALC256 code path).
> 
> #regzbot introduced: v6.12.2
> https://bugzilla.kernel.org/show_bug.cgi?id=220109
> 
> Sincerely,
> Ruslan
> 
> Forwarded Message (see logs in the bug report above):
> 
> There was a similar bug in the past (Bug 217440), which was fixed for this laptop. (I believe the code path is for ALC256, see below.) The same issue is occurring again as of kernel v.6.12.2. The symptoms are very similar - initially audio works but after a warm reboot, the audio completely disappears until the computer is powered off (there is no audio output at all).
> 
> The issue is caused by a different change now. By bisecting different kernel versions, I found that reverting cc3d0b5dd989d3238d456f9fd385946379a9c13d in patch_realtek.c ( see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/sound/pci/hda/patch_realtek.c?h=v6.12.2&id=4ed7f16070a8475c088ff423b2eb11ba15eb89b6 ) restores the sound and it works fine after the reboot.


It's the commit cc3d0b5dd989d3238d456f9fd385946379a9c13d
Author: Kailang Yang <kailang@realtek.com>
Date:  Thu Nov 14 15:21:09 2024 +0800

    ALSA: hda/realtek: Update ALC256 depop procedure
    
    Old procedure has a chance to meet Headphone no output.
    
    Fixes: 4a219ef8f370 ("ALSA: hda/realtek - Add ALC256 HP depop function")
    Signed-off-by: Kailang Yang <kailang@realtek.com>
    Link: https://lore.kernel.org/463c5f93715d4714967041a0a8cec28e@realtek.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

and it modified alc256_init() sequence.

Kailang, could you check this regression?


And, Ruslan, it's the case without the headphone, right?
Is the sound still lost when you connect the headphone and apply the
same procedure?


thanks,

Takashi

  reply	other threads:[~2025-05-15  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1064773772.509063.1747061777318.ref@mail.yahoo.com>
2025-05-12 14:56 ` Fwd: [Bug 220109] New: Audio disappears on HP 15-fc000 after warm boot again (ALC256 code path) Ruslan Nikolaev
2025-05-12 15:06   ` Takashi Iwai
2025-05-13  4:36     ` Ruslan Nikolaev [this message]
2025-11-06  9:34       ` Thorsten Leemhuis
2025-11-06 15:11         ` Sasha Levin

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=946767975.787038.1747111000631@mail.yahoo.com \
    --to=nruslan_devel@yahoo.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kailang@realtek.com \
    --cc=perex@perex.cz \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --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