lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 19 Jan 2022 10:12:43 +0100
From:   Takashi Iwai <>
To:     Alexander Sergeyev <>
Cc:     Jeremy Szu <>,,
        "moderated list:SOUND" <>,
        Kailang Yang <>,
        open list <>,
        Huacai Chen <>,
        Jian-Hong Pan <>,
        Hui Wang <>,
        PeiSen Hou <>
Subject: Re: [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8

On Sat, 15 Jan 2022 16:22:15 +0100,
Alexander Sergeyev wrote:
> On Sat, Jan 15, 2022 at 08:55:28AM +0100, Takashi Iwai wrote:
> > > This patch solved the BUG problem. But after unbind/bind micmute LED
> > > stopped working. Speakers and mute LED are fine though.
> > Does the corresponding sysfs entry exist in /sys/class/leds/*?
> Yes.
> > And can you control LED over there?
> After "out of range cmd" messages the sysfs entry remains present, but writing 
> ones to the brightness file stops to produce any effect.
> Actually, the timing issues are present here as well. Sometimes unbind & bind 
> works fine. But fails on the second round.

Here "fails" means the kernel Oops / crash?  If yes, the back trace
would be helpful.



Powered by blists - more mailing lists