[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aSr16ek8PFuT3vPG@smile.fi.intel.com>
Date: Sat, 29 Nov 2025 15:32:25 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Anton Khirnov <anton@...rnov.net>
Cc: Corentin Chary <corentin.chary@...il.com>,
"Luke D. Jones" <luke@...nes.dev>,
Denis Benato <benato.denis96@...il.com>,
Hans de Goede <hansg@...nel.org>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Jian-Hong Pan <jian-hong@...lessm.com>,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] platform/x86: asus-wmi: use brightness_set_blocking()
for kbd led
On Sat, Nov 29, 2025 at 11:13:08AM +0100, Anton Khirnov wrote:
> kbd_led_set() can sleep, and so may not be used as the brightness_set()
> callback.
>
> Otherwise using this led with a trigger leads to system hangs
> accompanied by:
> BUG: scheduling while atomic: acpi_fakekeyd/2588/0x00000003
> CPU: 4 UID: 0 PID: 2588 Comm: acpi_fakekeyd Not tainted 6.17.9+deb14-amd64 #1 PREEMPT(lazy) Debian 6.17.9-1
> Hardware name: ASUSTeK COMPUTER INC. ASUS EXPERTBOOK B9403CVAR/B9403CVAR, BIOS B9403CVAR.311 12/24/2024
> Call Trace:
> <TASK>
> [...]
> schedule_timeout+0xbd/0x100
> __down_common+0x175/0x290
> down_timeout+0x67/0x70
> acpi_os_wait_semaphore+0x57/0x90
> [...]
> asus_wmi_evaluate_method3+0x87/0x190 [asus_wmi]
> led_trigger_event+0x3f/0x60
> [...]
FWIW,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists