From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature
Date: Fri, 09 Apr 2021 17:01:56 +0000 [thread overview]
Message-ID: <bug-210457-215701-27SS80QlhS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210457-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210457
--- Comment #10 from Daniel T. (pterion@gmail.com) ---
(In reply to Hans de Goede from comment #9)
> (In reply to cfr from comment #8)
> > On my machine, the issue seems to have been caused by a firmware bug, which
> > only manifested in symptoms with the kernel update. That is, the firmware
> > was the same for 3+ years with no issue, the new kernel triggered the bug,
> > but a firmware update seems to have resolved it.
>
> Thank you.
>
> Can the other reporters of this bug please also see if the latest BIOS
> resolves this? ThinkPad BIOS updates are available on lvfs, so they can be
> done under Linux through fwupdmgr.
The situation is NOT resolved / the same for me after the recent firmware /
BIOS update.
--
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:[~2021-04-09 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-210457-215701@https.bugzilla.kernel.org/>
2021-03-10 19:24 ` [Bug 210457] Fan sporadically maxed on wake-up due to unavailable sensor temperature bugzilla-daemon
2021-03-10 19:31 ` bugzilla-daemon
2021-03-10 19:48 ` bugzilla-daemon
2021-03-10 19:54 ` bugzilla-daemon
2021-03-21 15:41 ` bugzilla-daemon
2021-03-22 13:23 ` bugzilla-daemon
2021-04-07 10:36 ` bugzilla-daemon
2021-04-09 17:01 ` bugzilla-daemon [this message]
2021-06-24 12:53 ` 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-210457-215701-27SS80QlhS@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 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.