Bug 1301739 - Machine Check exceptions related to transient temperature spikes get reported to abrt.
Summary: Machine Check exceptions related to transient temperature spikes get reported...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-25 21:21 UTC by Tom Prince
Modified: 2017-12-12 11:06 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-12 11:06:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg log from a Lenovo Thinkpas T450s (871 bytes, text/plain)
2016-01-25 21:21 UTC, Tom Prince
no flags Details

Description Tom Prince 2016-01-25 21:21:11 UTC
Created attachment 1118230 [details]
dmesg log from a Lenovo Thinkpas T450s

Description of problem:

I've got abrt regularlly reporting machine-check errors about temperature over-threshold that lasts for ~0.0011 seconds. This seems like it should be something reported via another method. It has gotten so that I just routinely ignore the abrt messages because they always seem to be this.

How reproducible:
Several times per day

Steps to Reproduce:
1. Cause the machine to heat up (this often happens running graphically intensive games).
2. Observe the MCE reported to abrt.

Actual results:
MCE reported to abrt


Expected results:
Ideally, it would be nice if the error was only reported to abrt if it wasn't transient (or perhaps for the threshold for throttling being lower than the threshold for reporting). It would also be nice if incidents were record to be able to see if the frequency of occurrence is significant.

But, I'd be happy if abrt simply ignored these errors, as I have abrt-fatigue from them.

Comment 1 Tomasz Torcz 2016-01-28 10:26:39 UTC
The messages are:
[4942478.364568] CPU3: Package temperature above threshold, cpu clock throttled (total events = 289096)
[4942478.364579] CPU0: Package temperature above threshold, cpu clock throttled (total events = 289098)
[4942478.364581] CPU1: Package temperature above threshold, cpu clock throttled (total events = 289098)
[4942478.364584] CPU2: Package temperature above threshold, cpu clock throttled (total events = 289098)
[4942478.365577] CPU3: Package temperature/speed normal
[4942478.365578] CPU2: Package temperature/speed normal
[4942478.365580] CPU0: Package temperature/speed normal
[4942478.365590] CPU1: Package temperature/speed normal

I do experience this issue on well-cooled, mostly idle desktop form-factor with Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 4.2.6-301.fc23.x86_64

Comment 2 Josh Boyer 2016-01-28 13:12:39 UTC
So there are two issues here.  The first is that the kernel is simply doing its job and is reporting the events.  That they are of an extremely short duration and kind of spammy is a downside, but it isn't incorrect.  The second issue is that abrt is triggering on them, but likely because of the mce being logged, not the temp messages themselves.

There most suitable workaround here is for abrt to not trigger on thermal events of such a short duration.  However, I doubt it is even looking at what caused the mce and it might not be easy for abrt to do that.  Will need to think so more.

Comment 3 David Gibson 2016-09-22 05:35:58 UTC
Just updating to note this is still present in Fedora 24, at least on my T460s.

(Also, hi Josh, long time no talk).

Comment 4 Justin M. Forbes 2017-04-11 14:43:29 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 5 David Gibson 2017-04-12 00:34:56 UTC
I still see these frequently with Fedora 25 and kernel-4.10.8-200.fc25.x86_64.  I'll try 4.10.9 when it arrives.

Comment 6 Fedora End Of Life 2017-11-16 19:45:19 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2017-12-12 11:06:55 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.