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: Fri, 27 Feb 2026 10:20:16 +0000 [thread overview]
Message-ID: <bug-220639-215701-yXrNUUGb8v@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 #17 from Enderlava (Jie7172585@gmail.com) ---
(In reply to Krishna Chomal from comment #16)
> Hi Enderlava,
>
> Thanks for the detailed report and EC dump.
>
> Since this bug specifically tracks support for board 8BAB (OMEN 16-wf0xxx),
> and your system uses board 8C76 (OMEN 16-wf1xxx), please open a new Bugzilla
> entry so the two boards can be tracked independently.
>
> In the new report, please include:
> - A clear description of what is not working
> - Errors from dmesg
> - Hardware details (dmidecode)
> - EC dump (xxd /sys/kernel/debug/ec/ec0/io)
> - If possible, the OMEN Gaming Hub logs from Windows:
>
> C:\Users\<USERNAME>\AppData\Local\Packages\AD2F1837.
> OMENCommandCenter_v10z8vjag6ke6\LocalCache\Local\HPOMEN\HPOMENBG_<timestamp>.
> log
>
> Once filed, I will take a look.
>
> Thanks.
Hi,
As requested, I have opened a new bug report specifically for the OMEN
16-wf1xxx (Board 8C76) here:
https://bugzilla.kernel.org/show_bug.cgi?id=221149
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 prev parent reply other threads:[~2026-02-27 10:20 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
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 [this message]
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-yXrNUUGb8v@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.