X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221569] Laptop fan too loud (spinning nearly always) hp-wmi 7.1-rc4 kerenel
Date: Sat, 20 Jun 2026 09:24:50 +0000	[thread overview]
Message-ID: <bug-221569-215701-85p9ib7Qij@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221569-215701@https.bugzilla.kernel.org/>

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

--- Comment #30 from Marco Scardovi (scardracs@disroot.org) ---
Regarding the message: hp_wmi: Unknown event_id - 131073 - 0x0

This event ID (131073 is 0x20001 in hex) is a standard notification sent by the
HP ACPI firmware during power state transitions (such as waking up from
suspend/hibernation or plugging/unplugging a USB-C charger). Since the hp-wmi
driver doesn't have a specific handler for this event, it falls back to
printing this diagnostic message. It is harmless log noise and can be safely
ignored.

As for the GPU hangs (amdgpu), they are unrelated to this WMI event. As said
before WMI events are handled entirely within the platform driver space,
whereas the GPU hangs are driver/firmware issues inside the amdgpu stack (often
related to power management or dynamic power states on newer AMD platforms).

-- 
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:[~2026-06-20  9:24 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-24 15:46 [Bug 221569] New: Laptop fan too loud (spinning nearly always) hp-wmi 7.1-rc4 kerenel bugzilla-daemon
2026-05-25 13:18 ` [Bug 221569] " bugzilla-daemon
2026-05-26 15:19 ` bugzilla-daemon
2026-05-27  5:24 ` bugzilla-daemon
2026-05-27  5:25 ` bugzilla-daemon
2026-05-31  9:05 ` bugzilla-daemon
2026-05-31  9:06 ` bugzilla-daemon
2026-05-31  9:07 ` bugzilla-daemon
2026-06-01  5:59 ` bugzilla-daemon
2026-06-01  7:54 ` bugzilla-daemon
2026-06-01  8:23 ` bugzilla-daemon
2026-06-01  8:31 ` bugzilla-daemon
2026-06-01  8:38 ` bugzilla-daemon
2026-06-01  8:40 ` bugzilla-daemon
2026-06-01  8:43 ` bugzilla-daemon
2026-06-01  8:48 ` bugzilla-daemon
2026-06-01  8:52 ` bugzilla-daemon
2026-06-01  9:58 ` bugzilla-daemon
2026-06-01 10:11 ` bugzilla-daemon
2026-06-01 15:02 ` bugzilla-daemon
2026-06-01 18:29 ` bugzilla-daemon
2026-06-12 18:36 ` bugzilla-daemon
2026-06-19 22:19 ` bugzilla-daemon
2026-06-20  6:34 ` bugzilla-daemon
2026-06-20  7:21 ` bugzilla-daemon
2026-06-20  7:54 ` bugzilla-daemon
2026-06-20  8:10 ` bugzilla-daemon
2026-06-20  8:18 ` bugzilla-daemon
2026-06-20  8:44 ` bugzilla-daemon
2026-06-20  9:16 ` bugzilla-daemon
2026-06-20  9:24 ` bugzilla-daemon [this message]
2026-06-20  9:32 ` bugzilla-daemon
2026-06-20  9:38 ` bugzilla-daemon
2026-06-20  9:45 ` bugzilla-daemon
2026-06-20  9:50 ` bugzilla-daemon
2026-06-20  9:55 ` bugzilla-daemon
2026-06-20 10:47 ` bugzilla-daemon
2026-06-20 11:42 ` bugzilla-daemon
2026-06-20 11:48 ` bugzilla-daemon
2026-06-20 12:01 ` bugzilla-daemon
2026-06-20 12:15 ` bugzilla-daemon
2026-06-20 12:22 ` bugzilla-daemon
2026-06-20 12:23 ` bugzilla-daemon
2026-06-20 13:07 ` bugzilla-daemon
2026-06-20 17:55 ` 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-221569-215701-85p9ib7Qij@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