Date:   Wed, 12 Jan 2022 10:45:46 +0100
Message-ID: <s5ho84h9tit.wl-tiwai@suse.de>
From:   Takashi Iwai <tiwai@suse.de>
To:     Alexander Sergeyev <sergeev917@gmail.com>
Cc:     Jeremy Szu <jeremy.szu@canonical.com>, tiwai@suse.com,
        "moderated list:SOUND" <alsa-devel@alsa-project.org>,
        Kailang Yang <kailang@realtek.com>,
        open list <linux-kernel@vger.kernel.org>,
        Huacai Chen <chenhuacai@kernel.org>,
        Jian-Hong Pan <jhp@endlessos.org>,
        Hui Wang <hui.wang@canonical.com>,
        PeiSen Hou <pshou@realtek.com>
Subject: Re: [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8
In-Reply-To: <20220111195229.a77wrpjclqwrx4bx@localhost.localdomain>
References: <20210519170357.58410-1-jeremy.szu@canonical.com>
        <20220111195229.a77wrpjclqwrx4bx@localhost.localdomain>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

On Tue, 11 Jan 2022 20:52:29 +0100,
Alexander Sergeyev wrote:
> 
> Hello,
> 
> On Thu, May 20, 2021 at 01:03:53AM +0800, Jeremy Szu wrote:
> >The HP EliteBook 855 G8 Notebook PC is using ALC285 codec which needs
> >ALC285_FIXUP_HP_MUTE_LED fixup to make it works. After applying the
> >fixup, the mute/micmute LEDs work good.
> 
> I've recently got HP EliteBook 855 G8 and it happens that neither
> micmute LED nor speakers work (except rare cases, more on that later)
> in 5.16.0. The corresponding ALC285_FIXUP_HP_MUTE_LED fixup is
> definitely applied (verified by adding a printk into
> alc285_fixup_hp_mute_led).
> 
> What is the most interesting, both micmute LED and speakers do work on
> rare boots. I've written some scripts to pick up sound from speakers
> using a known-good USB microphone. Out of 709 boots today only 16
> ended up with working micmute LED and speakers.
> 
> Is there anything I can do to help with debugging of this problem?
> 
> Initially reported at https://bugzilla.kernel.org/show_bug.cgi?id=215466

The problem is about the built-in drivers, or do you see the very same
problem even with modules?  AFAIK, quite a few AMD platforms tend to
have some issues with various devices showing initialization problems
at the early boot.  Just reloading / rebinding the device later often
helps.


Takashi