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 10:47:31 +0000 [thread overview]
Message-ID: <bug-221569-215701-odt4i2xRNV@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 #36 from Marco Scardovi (scardracs@disroot.org) ---
Thanks for the details.
Looking at the trip points for acpitz, there are only critical, hot, and
passive thresholds, but no active trip points. This confirms that the OS
thermal subsystem has no direct control over the fan via ACPI tables; the fan
is controlled entirely by the Embedded Controller (EC) firmware.
Even with the CPU idling at 37°C, the MediaTek WiFi 7 card (mt7925) is still
running very hot at 79°C. In many modern designs, the EC will keep the fan
spinning at a minimum speed (2100 RPM in your case) if any monitored component
(like the WiFi module or NVMe) is hot, to prevent localized heat build-up.
To test if the WiFi module is indeed the one triggering the fan, you can try
this quick test:
Block/disable WiFi and Bluetooth completely:
> sudo rfkill block all
Wait a few minutes (with the system idle) to see if the mt7925 temperature
drops.
Check sensors again to see if the WiFi temp drops and if the fan under acpi_fan
slows down or turns off.
If the fan turns off, it confirms the fan is triggered by the WiFi card's idle
temperature. (You can re-enable it later with sudo rfkill unblock all).
Additionally, you can check if you have any exposed ACPI cooling devices in
sysfs:
> tail /sys/class/thermal/cooling_device*/type
> tail /sys/class/thermal/cooling_device*/cur_state
Sometimes you can read the current fan state there, though the EC usually
overrides any manual changes to cur_state.
Another suggestion I can give you, if you feel confident enough, it to open the
chassis and check for dust around the WiFi module.
--
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-06-20 10:47 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
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 [this message]
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-odt4i2xRNV@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.