Bug 879972 - Machine check: Processor context corrupt
Summary: Machine check: Processor context corrupt
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-25 18:37 UTC by William Shore
Modified: 2016-11-15 19:35 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-28 15:05:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Photo of error message(s) (3.55 MB, image/jpeg)
2012-11-25 18:37 UTC, William Shore
no flags Details

Description William Shore 2012-11-25 18:37:19 UTC
Created attachment 651609 [details]
Photo of error message(s)

Booting 3.6.7-4.fc17.x86_64 randomly fails. Tried disabling various CPU features in BIOS without success. BIOS is Phoenix SecureCore Tiano. Processor is Intel Core i7-3517U @1.9GHz (4 core) and 8GB ram. Graphics: Intel Ivybridge Mobile.

Fails on power-on and/or on restart.

Booting 3.3.4-5.fc17_x86_64 always succeeds.

Comment 1 Dave Jones 2012-11-27 18:39:41 UTC
that 3.3 survives is curious, because if you run that message through mcelog as it suggests, you get this...

Hardware event. This is not a software error.
CPU 1 BANK 6 TSC fa6044417 
RIP !INEXACT! 10:ffffffff8114aac9
MISC 3880014086 ADDR fe400 
TIME 1353865842 Sun Nov 25 12:50:42 2012
MCG status:RIPV MCIP 
MCi status:
Uncorrected error
Error enabled
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 be2000000003110a MCGSTATUS 5
CPUID Vendor Intel Family 6 Model 58


which seems to suggest an L2 cache failure. No idea tbh. We've not had any similar reports that I can recall, which lends credence to the notion that this may be a fault unique to your particular setup.

Comment 2 William Shore 2012-11-29 01:38:50 UTC
I was doubtful bugzilla was the right spot for this issue, but I figured I'd give it a shot since I wasn't able to find much online. I only googled 1 other person with the issue (I think their distro was Debian) and they were able to resolve it by mucking with their BIOS settings.

If it is just a hardware issue it's a part of the hardware that neither Windows 8 (laptop shipped with) nor the 3.3 kernel uses. My best guess would be it's a driver/BIOS conflict. Though I admit I'm totally guessing there. 

I'm happy using the older kernel until hopefully a future BIOS update or kernel update works.

In any case, thank you for looking into it.

Comment 3 Josh Boyer 2013-03-11 20:16:23 UTC
We've still not had any similar reports that I'm aware of.  Are you still seeing this with 3.7.9 or 3.8.2?

Comment 4 Josh Boyer 2013-03-28 15:05:27 UTC
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.

Comment 5 NILESH ALHAT 2016-11-15 19:35:50 UTC
I am facing same issue with following output:
[root@oscar ~]# mcelog 
Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 6 
MISC 78a0000086 ADDR fef87380 
TIME 1479222023 Tue Nov 15 20:30:23 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
[root@oscar ~]#


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