mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: Mo Jun <royclark086@gmail.com>
Cc: "Salvatore Bonaccorso" <carnil@debian.org>,
	1146124@bugs.debian.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	"Denis Benato" <denis.benato@linux.dev>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Corentin Chary" <corentin.chary@gmail.com>,
	"Hans de Goede" <hansg@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: asus-laptop: Fn hotkeys no longer work on ThinkPad SL400 after 378500dc1313 ("platform/x86: asus-laptop: Register ACPI notify handler directly")
Date: Mon, 31 Aug 2026 21:24:15 +0200	[thread overview]
Message-ID: <897b6ce4-dca0-467c-b414-c9c2144a40f9@gmx.de> (raw)
In-Reply-To: <86edbe0c-21d6-4e63-bd14-8921ca866b91@gmx.de>

Am 30.08.26 um 23:42 schrieb Armin Wolf:

> Am 30.08.26 um 16:41 schrieb Mo Jun:
>
>> Hi Armin Wolf,
>>
>> On Sun, Aug 30, 2026 at 9:26 PM Mo Jun <royclark086@gmail.com> wrote:
>>> Hi Armin Wolf,
>>>
>>> On Sun, Aug 30, 2026 at 7:59 PM Armin Wolf <W_Armin@gmx.de> wrote:
>>>> [...]
>>>>
>>>> I think i found the culprit, could you please test the attached patch?
>>> Build the module with the patch(only "make -C .
>>> M=drivers/platform/x86") and load the built
>>> drivers/platform/x86/asus-laptop.ko, now the Fn hotkeys works again.
>> I found that after rmmod the built module, it can not be insmod again.
>> Also the system experienced NULL pointer dereferences in
>> acpi_bus_generate_netlink_event() which may related to the built
>> module.
>>
>> I guess these was caused that the patch only change calling to
>> acpi_dev_install_notify_handler(), not
>> acpi_dev_remove_notify_handler().
>> After change ACPI_DEVICE_NOTIFY to ACPI_ALL_NOTIFY in calling to
>> acpi_dev_remove_notify_handler()(see attached patch), now the module
>> can be insmod again after once rmmod.
>>
>> Regards,
>> Jun MO
>
> Good catch, i will send the fixed patch soon.
>
> Thanks,
> Armin Wolf 

Alright, the patch got accepted upstream and will likely land
with the stable kernels in a couple of weeks.

Thanks,
Armin Wolf


      reply	other threads:[~2026-08-31 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <178806598504.23591.11490486941444891398.reportbug@localhost>
2026-08-30  8:42 ` Salvatore Bonaccorso
2026-08-30 11:58   ` Armin Wolf
2026-08-30 13:26     ` Mo Jun
2026-08-30 14:41       ` Mo Jun
2026-08-30 21:42         ` Armin Wolf
2026-08-31 19:24           ` Armin Wolf [this message]

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=897b6ce4-dca0-467c-b414-c9c2144a40f9@gmx.de \
    --to=w_armin@gmx.de \
    --cc=1146124@bugs.debian.org \
    --cc=carnil@debian.org \
    --cc=corentin.chary@gmail.com \
    --cc=denis.benato@linux.dev \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=royclark086@gmail.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

all inboxes | Powered by JetHome®