From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220639] New: [BUG] hp-wmi: OMEN 16-wf0xxx (board 8BAB) – fans stuck at 0 RPM, Boost/WMI queries rejected (hp_wmi: query 0x4c error 0x6)
Date: Wed, 08 Oct 2025 04:30:11 +0000 [thread overview]
Message-ID: <bug-220639-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220639
Bug ID: 220639
Summary: [BUG] hp-wmi: OMEN 16-wf0xxx (board 8BAB) – fans stuck
at 0 RPM, Boost/WMI queries rejected (hp_wmi: query
0x4c error 0x6)
Product: Drivers
Version: 2.5
Kernel Version: 6.16.10-arch1-1
Hardware: Intel
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: juanm4morales@gmail.com
Regression: No
Created attachment 308774
--> https://bugzilla.kernel.org/attachment.cgi?id=308774&action=edit
hp-wmi diagnostics: logs + ACPI tables (OMEN 16-wf0xxx, board 8BAB)
Hardware:
• Laptop: “OMEN by HP Gaming Laptop 16-wf0xxx”
• DMI board-id: 8BAB
• BIOS: F.28 (2025-07-16)
Software:
• Distro: Arch Linux (Hyprland)
• Kernel: 6.16.10-arch1-1
• power-profiles-daemon installed; platform_profile set to “performance” has
no effect on fans
Problem summary:
• The hp-wmi driver exposes hwmon nodes (name=hp, fan1_input, fan2_input,
pwm1_enable) but fans remain at 0 RPM and the “Boost” write does nothing.
• Writing “0” to pwm1_enable (Boost) immediately reverts to “2” (auto). No
audible fan ramp; RPMs remain 0.
• dmesg shows: “hp_wmi: query 0x4c returned error 0x6”.
• /sys/class/thermal/cooling_device[0-4]: type=Fan, max_state=1, cur_state
stays at 0.
Expected behavior:
• On HP Omen models with working hp-wmi, “Boost” (pwm1_enable=0) briefly
ramps fans and RPM becomes non-zero; rpm values are readable via sensors
hp-isa-0000. (ArchWiki documents this expected behavior for Omen 16 models.)
Reproducer:
1) Boot into 6.16.10 (Arch kernel).
2) sensors: fan1/fan2 show 0 RPM.
3) echo 0 > /sys/devices/platform/hp-wmi/hwmon/hwmon*/pwm1_enable
→ value reverts to 2; no fan ramp; dmesg logs “hp_wmi: query 0x4c error
0x6”.
4) cooling_device[0..4] report Fan (max_state=1) but cur_state stays 0.
What I tried:
• Verified AC adapter online.
• Tried platform_profile=performance and power-profiles-daemon.
• Collected ACPI tables (acpidump -b) and full logs.
Hypothesis:
• This board-id (8BAB) might not be covered by current hp-wmi DMI allow-lists
or uses different HPWMI method IDs on newer firmwares; the firmware rejects
0x4c here. Guidance on traces/patch to test alternate query paths would be
appreciated.
Attachments:
• Tarball with: dmesg, journalctl -b, lsmod, modinfo hp_wmi, sensors, hp-wmi
hwmon listings, cooling devices/thermal zones, dmidecode (serial/UUID
redacted), ACPI tables (acpidump -b).
I’m happy to run debug builds, provide disassembled DSDT/SSDT snippets around
WMI devices, and test patches. Thanks!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-10-08 4:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 4:30 bugzilla-daemon [this message]
2025-10-08 6:29 ` [Bug 220639] [BUG] hp-wmi: OMEN 16-wf0xxx (board 8BAB) – fans stuck at 0 RPM, Boost/WMI queries rejected (hp_wmi: query 0x4c error 0x6) bugzilla-daemon
2025-10-08 20:10 ` bugzilla-daemon
2025-10-20 23:32 ` bugzilla-daemon
2025-11-09 14:00 ` bugzilla-daemon
2026-02-12 13:43 ` bugzilla-daemon
2026-02-12 20:05 ` bugzilla-daemon
2026-02-13 13:51 ` bugzilla-daemon
2026-02-14 5:00 ` bugzilla-daemon
2026-02-14 5:00 ` bugzilla-daemon
2026-02-14 5:01 ` bugzilla-daemon
2026-02-14 5:09 ` bugzilla-daemon
2026-02-14 5:17 ` bugzilla-daemon
2026-02-14 5:26 ` bugzilla-daemon
2026-02-14 6:28 ` bugzilla-daemon
2026-02-14 10:35 ` bugzilla-daemon
2026-02-16 7:33 ` bugzilla-daemon
2026-02-26 7:23 ` bugzilla-daemon
2026-02-27 7:07 ` bugzilla-daemon
2026-02-27 10:20 ` bugzilla-daemon
2026-02-27 10:45 ` bugzilla-daemon
2026-03-30 15:20 ` bugzilla-daemon
2026-03-30 16: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-220639-215701@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.