Bug 1082211

Created attachment 880074 [details]
ABRT's proc_modules

In case the problem lies in some module.

Here's a problem report that MIGHT be related:

http://forums.fedoraforum.org/showthread.php?t=297456

http://h30434.www3.hp.com/t5/Notebook-Hardware/HP-Pavilion-Laptop-Machine-Check-Error-on-Linux-when-Waking/m-p/3589867/highlight/false#M121333

Maybe also this Ubuntu report:

http://ubuntuforums.org/showthread.php?t=2189035&page=3&p=12876018#post12876018

(Possible common factor: the notebook in this second report and my Yoga 2 pro have Intel Wireless N 7260 cards that only started working with the latest firmware.  I don't know about the computer in the first report.)

I have a similar issue (I raised the HP issue in comment #2 above).  My problem is on a HP Pavilion with an Intel i5 CPU but not the Intel Wireless N7260 card.  The laptop came with a horrible Realtek item which was quite temperamental.  I've had a different Intel wireless card and now an Atheros 9K card and all seem to show the MCE error in the log.

Created attachment 880194 [details]
dmesg output captured by ABRT

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  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 experience different issues, please open a new bug report for those.

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Still happening with 3.17.3-300.fc21.x86_64

# journalctl -b -u mcelog
-- Logs begin at Fri 2014-11-21 17:05:25 MST, end at Tue 2014-11-25 11:08:13 MST. --
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: Hardware event. This is not a software error.
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: MCE 0
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: CPU 0 BANK 6
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: MISC 38a0000086 ADDR ffb07640
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: TIME 1416934657 Tue Nov 25 09:57:37 2014
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: MCG status:
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: MCi status:
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: Uncorrected error
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: MCi_MISC register valid
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: MCi_ADDR register valid
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: Processor context corrupt
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: MCA: corrected filtering (some unreported errors i
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: Generic CACHE Level-2 Generic Error
Nov 25 09:57:40 moa.cora.nwra.com mcelog[553]: STATUS ae0000000040110a MCGSTATUS 0

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.18.7-100.fc20.  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 21, and are still experiencing this issue, please change the version to Fedora 21.

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

I still see it with 3.18.7-200.fc21.x86_64, can't speak to F20.

I saw it wit F20 and I see it with F21.

Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCG status:
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCi status:
Apr 11 21:35:42 localhost.localdomain mcelog[862]: Uncorrected error
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCi_MISC register valid
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCi_ADDR register valid
Apr 11 21:35:42 localhost.localdomain mcelog[862]: Processor context corrupt
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCA: corrected filtering (some unreported errors in same region)
Apr 11 21:35:42 localhost.localdomain mcelog[862]: Generic CACHE Level-2 Generic Error
Apr 11 21:35:42 localhost.localdomain mcelog[862]: STATUS ae0000000040110a MCGSTATUS 0
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCGCAP c07 APICID 0 SOCKETID 0
Apr 11 21:35:42 localhost.localdomain mcelog[862]: CPUID Vendor Intel Family 6 Model 69
Apr 11 21:45:23 localhost.localdomain mcelog[862]: Hardware event. This is not a software error.
Apr 11 21:45:23 localhost.localdomain mcelog[862]: MCE 0
Apr 11 21:45:23 localhost.localdomain mcelog[862]: CPU 0 BANK 5
Apr 11 21:45:23 localhost.localdomain mcelog[862]: MISC f8a0000086 ADDR ffb03900

Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCG status:
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCi status:
Apr 11 21:35:42 localhost.localdomain mcelog[862]: Uncorrected error
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCi_MISC register valid
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCi_ADDR register valid
Apr 11 21:35:42 localhost.localdomain mcelog[862]: Processor context corrupt
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCA: corrected filtering (some unreported errors in same region)
Apr 11 21:35:42 localhost.localdomain mcelog[862]: Generic CACHE Level-2 Generic Error
Apr 11 21:35:42 localhost.localdomain mcelog[862]: STATUS ae0000000040110a MCGSTATUS 0
Apr 11 21:35:42 localhost.localdomain mcelog[862]: MCGCAP c07 APICID 0 SOCKETID 0
Apr 11 21:35:42 localhost.localdomain mcelog[862]: CPUID Vendor Intel Family 6 Model 69
Apr 11 21:45:23 localhost.localdomain mcelog[862]: Hardware event. This is not a software error.
Apr 11 21:45:23 localhost.localdomain mcelog[862]: MCE 0
Apr 11 21:45:23 localhost.localdomain mcelog[862]: CPU 0 BANK 5
Apr 11 21:45:23 localhost.localdomain mcelog[862]: MISC f8a0000086 ADDR ffb03900

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is 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 21 kernel bugs.

Fedora 21 has now been rebased to 3.19.5-200.fc21.  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 22, and are still experiencing this issue, please change the version to Fedora 22.

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

Happens with Fedora 22 and kernel 4.0.4. On every resume from suspend to RAM. My laptop is Acer Aspire VN7-591G.

Might be related to not being able to resume sometimes. I haven't hit this on F22 yet but happened on F21 after several suspend-resume cycles.

I also have the same problem on my Yoga 2 Pro.  At least the system log is extraordinarily similar.

I am running Fedora 21 with vmlinuz-4.0.4-202.fc21.x86_64.  It also appears that the problem only occurs on resume from suspend.

I see this too, running kernel-4.1.5-200.fc22.x86_64 on a Lenovo B50-70. Happens every time I suspend and resume. I tried disabling legacy USB and Wireless LAN in the BIOS, and it made no difference.

I am experiencing this problem as well on Lenovo Y50-70, kernel 4.1.6-201.fc22.x86_64. Exactly same behavior as described in the original post.

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is 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 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  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 23, and are still experiencing this issue, please change the version to Fedora 23.

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

This is still happening with Fedora 23, kernel 4.2.5-300.fc23.x86_64

The information seen on the system log is still the same.

I don't think that I can change the version.

Issue observed on ultrabook Lenovo Ideapad U430p, i5 4200U CPU.

The last 20 mcelog lines of system log are:
==========================================
May 13 20:21:05 localhost mcelog: STATUS ee0000000040110a MCGSTATUS 0
May 13 20:21:05 localhost mcelog: MCGCAP c07 APICID 0 SOCKETID 0
May 13 20:21:05 localhost mcelog: CPUID Vendor Intel Family 6 Model 69
May 13 20:21:05 localhost mcelog: Hardware event. This is not a software error.
May 13 20:21:05 localhost mcelog: MCE 1
May 13 20:21:05 localhost mcelog: CPU 0 BANK 6
May 13 20:21:05 localhost mcelog: MISC 38a0000086 ADDR fef81a40
May 13 20:21:05 localhost mcelog: TIME 1463163664 Fri May 13 20:21:04 2016
May 13 20:21:05 localhost mcelog: MCG status:
May 13 20:21:05 localhost mcelog: MCi status:
May 13 20:21:05 localhost mcelog: Error overflow
May 13 20:21:05 localhost mcelog: Uncorrected error
May 13 20:21:05 localhost mcelog: MCi_MISC register valid
May 13 20:21:05 localhost mcelog: MCi_ADDR register valid
May 13 20:21:05 localhost mcelog: Processor context corrupt
May 13 20:21:05 localhost mcelog: MCA: corrected filtering (some unreported errors in same region)
May 13 20:21:05 localhost mcelog: Generic CACHE Level-2 Generic Error
May 13 20:21:05 localhost mcelog: STATUS ee0000000040110a MCGSTATUS 0
May 13 20:21:05 localhost mcelog: MCGCAP c07 APICID 0 SOCKETID 0
May 13 20:21:05 localhost mcelog: CPUID Vendor Intel Family 6 Model 69

Still happening on 4.6.3-300.fc24.x86_64

So we all have the same bug. And similar  (Intel) hardware. Even though it logs it as "Uncorrected error", nothing nasty has been reported by anyone so far, including me.

My machine:

Lenovo Yoga 2 13.
With: Realtek Wifi Card.

Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 6 
MISC 38a0000086 ADDR fef81780 
TIME 1471502624 Thu Aug 18 12:13:44 2016
MCG status:
MCi status:
Uncorrected error
MCi_MISC register valid
MCi_ADDR register valid
Processor context corrupt
MCA: corrected filtering (some unreported errors in same region)
Generic CACHE Level-2 Generic Error
STATUS ae0000000040110a MCGSTATUS 0
MCGCAP c07 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 6 Model 69
Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 6 
MISC 38a0000086 ADDR fef81780 
TIME 1471506843 Thu Aug 18 13:24:03 2016
MCG status:
MCi status:
Uncorrected error
MCi_MISC register valid
MCi_ADDR register valid
Processor context corrupt
MCA: corrected filtering (some unreported errors in same region)
Generic CACHE Level-2 Generic Error
STATUS ae0000000040110a MCGSTATUS 0
MCGCAP c07 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 6 Model 69



I did a search, again, today and am reporting on this bug report because I've had one report on debian-kernel list of a user, who is getting MCE Errors resulting in Machine Halt. Interestingly, the user did not have this issue with older kernel. I've asked him again if reverting back to old kernel avoids the bug.

In that case, it'll be another software bug camouflaged otherwise.

*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is 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 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

I just updated and it is still happening.  This is on Fedora 24, but I don't see how to update the version as this is not my bug.

Linux idefix.nuance.com 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


Sep 23 07:11:37 idefix mcelog: Generic CACHE Level-2 Generic Error
Sep 23 07:11:37 idefix mcelog: STATUS ae0000000040110a MCGSTATUS 0
Sep 23 07:11:37 idefix mcelog: MCGCAP c07 APICID 0 SOCKETID 0
Sep 23 07:11:37 idefix mcelog: CPUID Vendor Intel Family 6 Model 69
Sep 23 13:19:40 idefix mcelog: Hardware event. This is not a software error.
Sep 23 13:19:40 idefix mcelog: MCE 0
Sep 23 13:19:40 idefix mcelog: CPU 0 BANK 6
Sep 23 13:19:40 idefix mcelog: MISC 38a0000086 ADDR ffb03840
Sep 23 13:19:40 idefix mcelog: TIME 1474661978 Fri Sep 23 13:19:38 2016
Sep 23 13:19:40 idefix mcelog: MCG status:
Sep 23 13:19:40 idefix mcelog: MCi status:
Sep 23 13:19:40 idefix mcelog: Uncorrected error
Sep 23 13:19:40 idefix mcelog: MCi_MISC register valid
Sep 23 13:19:40 idefix mcelog: MCi_ADDR register valid
Sep 23 13:19:40 idefix mcelog: Processor context corrupt
Sep 23 13:19:40 idefix mcelog: MCA: corrected filtering (some unreported errors in same region)
Sep 23 13:19:40 idefix mcelog: Generic CACHE Level-2 Generic Error
Sep 23 13:19:40 idefix mcelog: STATUS ae0000000040110a MCGSTATUS 0
Sep 23 13:19:40 idefix mcelog: MCGCAP c07 APICID 0 SOCKETID 0
Sep 23 13:19:40 idefix mcelog: CPUID Vendor Intel Family 6 Model 69

I updated from Fedora 23 to 24 just to check for this bug.

It is still present.

*********** 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.

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.

This bug is still experienced with Fedora 25.

I just deleted over 200 ABRT reports of the bug, rebooted, and had two fresh ones.

I'm using 4.10.13-200.

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.

This still happens in Fedora 27

Can confirm this too.

Yep.. same shit on FC27 notebook-model: 20FQ003YRT

Random MCE errors, and resume after suspend always stuck.
BUT! this happens only in case of lagacy boot mode (aka BIOS)
After I've switched boot to UEFI mode and reinstalled fedora everying works fine (at least for now :) ) 
Probably this is Lenovo's firmware bug. Most people not see is simply because they use UEFY, probably legacy boot was not tested at all. 
So guys try to switch to UEFI mode.

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  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 experience different issues, please open a new bug report for those.

The bug still shows up in 4.15.3-300.fc27.x86_64.
In fact, it seems to show up during normal booting in addition to during wakeup.

It was happening for me on Fedora 27, after update to F28 still the same problem.

$ uname -r
4.16.4-300.fc28.x86_64

As someone else previously mentioned, I also have Intel Wireless 7260.
$ lspci |fgrep -i wireless
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)

My computer is Lenovo Ideapad Y50-70.

$ systemctl status mcelog
● mcelog.service - Machine Check Exception Logging Daemon
   Loaded: loaded (/usr/lib/systemd/system/mcelog.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2018-04-29 18:48:11 CEST; 1 day 1h ago
 Main PID: 1185 (mcelog)
    Tasks: 1 (limit: 4915)
   Memory: 500.0K
   CGroup: /system.slice/mcelog.service
           └─1185 /usr/sbin/mcelog --ignorenodev --daemon --foreground

dub 30 16:56:18 arrow mcelog[1185]: MCi_MISC register valid
dub 30 16:56:18 arrow mcelog[1185]: MCi_ADDR register valid
dub 30 16:56:18 arrow mcelog[1185]: Processor context corrupt
dub 30 16:56:18 arrow mcelog[1185]: MCA: corrected filtering (some unreported errors in same region)
dub 30 16:56:18 arrow mcelog[1185]: Generic CACHE Level-2 Generic Error
dub 30 16:56:18 arrow mcelog[1185]: STATUS ee0000000040110a MCGSTATUS 0
dub 30 16:56:18 arrow mcelog[1185]: MCGCAP c09 APICID 0 SOCKETID 0
dub 30 16:56:18 arrow mcelog[1185]: CPUID Vendor Intel Family 6 Model 60
dub 30 16:56:18 arrow mcelog[1185]: mcelog: warning: 8 bytes ignored in each record
dub 30 16:56:18 arrow mcelog[1185]: mcelog: consider an update

$ journalctl -b -u mcelog
https://paste.fedoraproject.org/paste/Qrt9h32SsYJDIcB0VY0N0w

One more additional problem that may or may not be related. When I wake the computer from suspend state, the network is acting weirdly (testing multiple times, everytime the same result). The ethernet stops working completely and cannot be detected, the wireless connection works over IPv4 but stops working on IPv6. Restarting NetworkManager doesn't help. Running ifdown/ifup scripts on the ethernet device doesn't help - the ifup script fails.

I debugged the behaviour of the ifup script, it runs OK until calling:
+ nmcli con up uuid <hidden by author>
Error: Connection activation failed: No suitable device found for this connection.

Running "nmcli con up" manually on the ethernet device produces same error message. Restarting the computer solves these network issues.

In the Yoga 2 Pro's firmware ("BIOS") setup screen, under "boot" tab, I disabled "Lenovo fast boot".  In the several times that I've had my machine boot or awaken, no machine checks!

As I understand it, "fast boot" causes the firmware to initialize a fewer things before booting the OS.

Since fast boot and slow boot seem to take about the same time, this work-around isn't much of a burden.

Darn.  I spoke too soon.  I got another machine check on a resume.

*********** 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 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  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 28, and are still experiencing this issue, please change the version to Fedora 28.

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

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

this still happens in Fedora 28

We apologize for the inconvenience.  There is 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 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  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 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Still happens on 4.18.10.

this still happens with kernel 4.18.10-200.fc28.  I know that's not -300, but it is the latest that "sudo dnf update" gets me.

Happens on every Fedora I tried since 23 (latest F28), but does not happen on Ubuntu (last on Kubuntu 18.04).
Laptop Lenovo IdeaPad U430p, Intel Core i5 4200U.

*********** 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 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  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 29, and are still experiencing this issue, please change the version to Fedora 29.

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

I just tested on Fedora 29 with kernel 4.20.4 -20.fc29.x86_64

The Yoga 2 pro now seems to always or at least frequently get the machine check on boot.

I tested a couple of short sleeps and did not get the machine check.  I would guess that it happens sometimes.

Still an issue on Fedora 30 fresh install and also after update (kernel-5.1.8-300).

Lenovo Ideapad U430p, i5 4200U CPU, GeForce 730M

(In reply to Monakhov Dmitriy from comment #32)
> Yep.. same shit on FC27 notebook-model: 20FQ003YRT
> 
> Random MCE errors, and resume after suspend always stuck.
> BUT! this happens only in case of lagacy boot mode (aka BIOS)
> After I've switched boot to UEFI mode and reinstalled fedora everying works
> fine (at least for now :) ) 
> Probably this is Lenovo's firmware bug. Most people not see is simply
> because they use UEFY, probably legacy boot was not tested at all. 
> So guys try to switch to UEFI mode.

Tried. Didn't change a thing. Thanks for the tip anyway ;)

*********** 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 30 kernel bugs.

Fedora 30 has now been rebased to 5.2.9-200.fc30.  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 31, and are still experiencing this issue, please change the version to Fedora 31.

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

I just tested with kernel 5.2.8-200.fc30x86_64.

- the problem persists

- dnf update does not get me 5.2.9-200 so I did not test with it

- Fedora 31 is not available so I haven't tested with it

*********** 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 30 kernel bugs.

Fedora 30 has now been rebased to 5.5.7-100.fc30.  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 31, and are still experiencing this issue, please change the version to Fedora 31.

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

I just updated my Lenovo Yoga 2 Pro.  It has been running Fedora 31.  It is now on kernel 5.5.7-200.fc31x86_64.

ABRT still reports:

 Unexpected system error
  The system has encountered a problem and recovered.

 Name: kernel-core
 version 5.5.7-200.fc31x86_64
 First Detected: 36 seconds ago
 Reported: cannot be reported

 The kernel log indicates that hardware errors were detected.
 This is most likely not a software problem.

All this is because of a Machine Check Event.

My best guess is that some hardware probing of a device driver is provoking this.  I have no idea how to debug it.

Here's an extract of dmesg output:

[    0.012118] smpboot: CPU0: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz (family: 0x6, model: 0x45, stepping: 0x1)
[    0.012229] mce: [Hardware Error]: Machine check events logged
[    0.012234] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae0000000040110a
[    0.012238] mce: [Hardware Error]: TSC 0 ADDR ffb07640 MISC 78a0000086 
[    0.012243] mce: [Hardware Error]: PROCESSOR 0:40651 TIME 1583254826 SOCKET 0 APIC 0 microcode 25
[    0.012300] Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver.

(In reply to D. Hugh Redelmeier from comment #52)
> I just updated my Lenovo Yoga 2 Pro.  It has been running Fedora 31.  It is
> now on kernel 5.5.7-200.fc31x86_64.
> 
> ABRT still reports:
> 
>  Unexpected system error
>   The system has encountered a problem and recovered.
> 
>  Name: kernel-core
>  version 5.5.7-200.fc31x86_64
>  First Detected: 36 seconds ago
>  Reported: cannot be reported
> 
>  The kernel log indicates that hardware errors were detected.
>  This is most likely not a software problem.
> 
> All this is because of a Machine Check Event.
> 
> My best guess is that some hardware probing of a device driver is provoking
> this.  I have no idea how to debug it.
> 
> Here's an extract of dmesg output:
> 
> [    0.012118] smpboot: CPU0: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
> (family: 0x6, model: 0x45, stepping: 0x1)
> [    0.012229] mce: [Hardware Error]: Machine check events logged
> [    0.012234] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6:
> ae0000000040110a
> [    0.012238] mce: [Hardware Error]: TSC 0 ADDR ffb07640 MISC 78a0000086 
> [    0.012243] mce: [Hardware Error]: PROCESSOR 0:40651 TIME 1583254826
> SOCKET 0 APIC 0 microcode 25
> [    0.012300] Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR,
> full-width counters, Intel PMU driver.

I also experienced this error in hp notebook running fedora 31. Have you tried fedora 32?? Is this bug still present in fedora 32????

I still get this bug in Fedora 32.

This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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.

I just checked again.  The problem persists on my Lenovo Yoga 2 Pro.  I am running Fedora 32 with kernel-core-5.8.16-200.fc32

This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-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 '32'.

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 32 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.

This 7 year old Yoga 2 Pro laptop, from the original report, still has this problem.  Tested with Fedora 32, kernel-core 5.11.17-300.fc34-x86_64

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

I updated fo Fedora 36 via DNF.  I *think* that my Yoga 2 pro still had the problem.

The update didn't work properly -- grub could only find Fedora 35 kernels.  So I did a mostly clean install of Fedora 36 (I preserved /home).

After the clean install, I no longer see the machine check.  Unfortunately I cannot say what fixed the problem.

It came back shortly after my report.  So: present in Fedora 36 and 37.