platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220246] Dell Latitude 5400: Mic Mute key stopped to work in v6.15
Date: Wed, 18 Jun 2025 21:18:09 +0000	[thread overview]
Message-ID: <bug-220246-215701-OZLJNSR1KZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220246-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220246

--- Comment #9 from Kurt Borja (kuurtb@gmail.com) ---
On Wed Jun 18, 2025 at 4:42 PM -03, bugzilla-daemon wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220246
>
> --- Comment #6 from Dmytro Bagrii (dimich.dmb@gmail.com) ---
> Full dmesg output attached:
> https://bugzilla.kernel.org/attachment.cgi?id=308287
>
> dmesg output after single Mic Mute key press in 6.15:
>
> dell_wmi: Received WMI event (00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00)

Yep, this is the problem. Can you please bisect the WMI core commits
from this cycle? This should do the trick:

$ git bisect start v6.15 v6.14 -- drivers/platform/x86/wmi.c

You are using Arch so you can use

$ make localmodconfig
$ make -j$(nproc) pacman-pkg

to compile.

Maybe (Cc+) Armin Wolf can give us some insight too.

>
> Compare to 6.14.10:
>
> dell_wmi: Received WMI event (02 00 10 00 50 01 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00)
> dell_wmi: Process buffer (02 00 10 00 50 01)
> dell_wmi: Key with type 0x0010 and code 0x0150 pressed

@Armin JFYI:

I have this exact event in my system (Alienware x15 r1) but I can't
reproduce the bug. The WMI event is received just fine.

I also tried upstream v6.15 and v6.16 and this event still works fine.

>
> Also I noted difference in loaded modules. `lsmod | grep dell` In 6.15:
>
> dell_pc                12288  0
> platform_profile       16384  1 dell_pc
> dell_rbtn              20480  0
> dell_laptop            45056  0
> dell_smm_hwmon         28672  0
> dell_wmi               28672  1 dell_laptop
> dell_smbios            36864  3 dell_wmi,dell_pc,dell_laptop
> dell_wmi_sysman        61440  0
> firmware_attributes_class    12288  1 dell_wmi_sysman
> dcdbas                 20480  1 dell_smbios
> dell_wmi_descriptor    20480  2 dell_wmi,dell_smbios
> dell_lis3lv02d         16384  0
> dell_smo8800           16384  0
> rfkill                 45056  9
> iwlmvm,bluetooth,dell_laptop,dell_rbtn,cfg80211
> sparse_keymap          12288  2 intel_hid,dell_wmi
> video                  81920  3 dell_wmi,dell_laptop,i915
> wmi                    32768  7
>
> dell_wmi_sysman,video,dell_wmi,wmi_bmof,dell_smm_hwmon,dell_smbios,dell_wmi_descriptor
>
> Compare to 6.14.10:
>
> dell_pc                12288  0
> platform_profile       16384  1 dell_pc
> dell_rbtn              20480  0
> dell_laptop            45056  0
> dell_smm_hwmon         28672  0
> dell_wmi               28672  1 dell_laptop
> dell_smbios            36864  3 dell_wmi,dell_pc,dell_laptop
> dcdbas                 20480  1 dell_smbios
> dell_wmi_sysman        61440  0
> dell_lis3lv02d         16384  0
> firmware_attributes_class    12288  1 dell_wmi_sysman
> dell_wmi_descriptor    20480  2 dell_wmi,dell_smbios
> rfkill                 40960  9
> iwlmvm,bluetooth,dell_laptop,dell_rbtn,cfg80211
> dell_smo8800           16384  0
> sparse_keymap          12288  2 intel_hid,dell_wmi
> video                  81920  3 dell_wmi,dell_laptop,i915
> i8042                  57344  1 dell_laptop
> wmi                    32768  7
>
> dell_wmi_sysman,video,dell_wmi,wmi_bmof,dell_smm_hwmon,dell_smbios,dell_wmi_descriptor
>
> Note in "good" case i8042 is loaded and used by dell_laptop module, in "bad"
> case it isn't.
> I modprobed i8042 in 6.15 just in case. Expectedly, it had no effect.

Yes, as you already mentioned the i8042 module is unrelated to this bug.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-06-18 21:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 16:58 [Bug 220246] New: Dell Latitude 5400: Mic Mute key stopped to work in v6.15 bugzilla-daemon
2025-06-18 17:07 ` [Bug 220246] " bugzilla-daemon
2025-06-18 17:31 ` bugzilla-daemon
2025-06-18 17:58 ` bugzilla-daemon
2025-06-18 18:05 ` bugzilla-daemon
2025-06-18 18:42 ` bugzilla-daemon
2025-06-18 19:32 ` bugzilla-daemon
2025-06-18 19:42 ` bugzilla-daemon
2025-06-18 20:25 ` bugzilla-daemon
2025-06-18 20:46 ` bugzilla-daemon
2025-06-18 21:18 ` bugzilla-daemon [this message]
2025-06-18 21:30 ` bugzilla-daemon
2025-06-18 21:36 ` bugzilla-daemon
2025-06-18 21:37 ` bugzilla-daemon
2025-06-18 21:43 ` bugzilla-daemon
2025-06-18 21:46 ` bugzilla-daemon
2025-06-18 22:04 ` bugzilla-daemon
2025-06-19  0:17 ` bugzilla-daemon
2025-06-19  0:52 ` bugzilla-daemon
2025-06-19 19:51 ` bugzilla-daemon
2025-06-19 21:39 ` bugzilla-daemon
2025-06-19 22:10 ` bugzilla-daemon
2025-06-24 15:07 ` bugzilla-daemon
2025-06-26 17:04 ` bugzilla-daemon
2025-07-06  3:06 ` bugzilla-daemon
2025-07-06  3:07 ` bugzilla-daemon

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=bug-220246-215701-OZLJNSR1KZ@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).