From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [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)
Date: Thu, 12 Feb 2026 13:43:42 +0000 [thread overview]
Message-ID: <bug-220639-215701-fm520ykTAM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220639-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220639
--- Comment #4 from Krishna Chomal (krishna.chomal108@gmail.com) ---
Hi,
As Edip Hazuri mentioned, this happens because your Board ID (8BAB) is
not present in the hp-wmi driver's thermal profile lists.
As per Noah Provenzano's unmerged patch:
https://lore.kernel.org/platform-driver-x86/20250731213529.27378-1-noahpro@gmail.com
The entry should go in victus_s_thermal_profile_boards[]. However, recent
patches by me (8ca7515d3c76 and eeeb4c9874bb), currently in the pdx86
for-next branch, refactor this list into a DMI System ID table to
account for quirks.
To build the patch, I need to identify the EC register for the thermal
state. Please provide the output of:
$ sudo modprobe ec_sys
$ sudo xxd /sys/kernel/debug/ec/ec0/io
This should be sufficient to build the patch.
--
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 prev parent reply other threads:[~2026-02-12 13:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 4:30 [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) bugzilla-daemon
2025-10-08 6:29 ` [Bug 220639] " 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 [this message]
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-fm520ykTAM@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