From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 203191] The fan speed reports to 65535, despite the fan is stopped
Date: Thu, 18 Mar 2021 16:39:46 +0000 [thread overview]
Message-ID: <bug-203191-215701-lHNpreJ94r@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203191-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203191
--- Comment #7 from Matthias Schiffer (mschiffer@universe-factory.net) ---
The T470 (without the 's' suffix) is affected as well. Still reproducible with
the latest BIOS 1.65 and Linux 5.11.6.
I believe the issue is not directly related to suspend/resume, as I don't use
suspend. Instead, the fan control can break any time the fan is supposed to
spin up, which may be when waking up from suspend, or simply because of
increased CPU workload.
Whenever the systems gets into the broken state:
- the fan is not spinning at all
- hwmon and /proc/acpi/ibm/fan report 65535 RPM
- manual control via /proc/acpi/ibm/fan is ignored (Note: I normally don't use
this interface, but rely on the builtin fan control)
- only a full poweroff will fix the issue. When attempting to reboot without a
poweroff, the BIOS will refuse to boot with a "Fan error" message.
As far as I remember, the issue originally started when Lenovo fixed a BIOS
issue that caused the fan to hang at 100% after suspend occasionally a few
years ago.
I'd be happy to provide any information that may help fix this issue, as I'm
seeing it pretty much daily.
--
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 parent reply other threads:[~2021-03-18 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-203191-215701@https.bugzilla.kernel.org/>
2021-03-18 16:39 ` bugzilla-daemon [this message]
2022-09-26 11:42 ` [Bug 203191] The fan speed reports to 65535, despite the fan is stopped bugzilla-daemon
2022-10-24 14:49 ` bugzilla-daemon
2022-10-24 15:16 ` bugzilla-daemon
2023-03-29 22:19 ` bugzilla-daemon
2023-04-17 20:41 ` bugzilla-daemon
2023-11-22 12:02 ` bugzilla-daemon
2023-11-22 12:33 ` bugzilla-daemon
2023-12-04 0:41 ` bugzilla-daemon
2023-12-04 0:52 ` bugzilla-daemon
2023-12-04 1:03 ` bugzilla-daemon
2024-01-04 13:47 ` bugzilla-daemon
2025-12-22 9: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-203191-215701-lHNpreJ94r@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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