Bug 847396

Summary: KERNEL PANIC - Some CPUs didn't answer in sychronization
Product: [Fedora] Fedora Reporter: Marc-Andre Laverdiere <marcandre.laverdiere>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda, wenfeng.liu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-02 13:22:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Picture of the output on the screen none

Description Marc-Andre Laverdiere 2012-08-10 20:40:05 UTC
Created attachment 603630 [details]
Picture of the output on the screen

Description of problem:
System crashes with kernel panic output message displayed.

The message states:
CPU 2: Machine check exception: 5 bank 4: B2000000110040...
TSC 2607ec463a12
Processor 0:206a7 TIME 1344618342 Socket 0 APIC 2 microco...
Run the above through 'mcelog --ascii'
Some CPUs didn't answer in synchronization
Machine check: Invalid
Kernel panic - not syncing: Fatal machine check on current CPU
RIP !INEXACT! 33:<00000038e1599024>
Shutting down CPUs with NMI
panic occured, switching back to text console
Rebooting in 30 seconds
ACPI MEMORY or I/O RESET_REG

Version-Release number of selected component (if applicable):

How reproducible:
This happened twice when running big compilation loads so far.

Steps to Reproduce:
(unsure steps)
1. Update the LibreOffice source from git
2. Run nice -n19 make
3. Let it happen
(I didn't re-test it)

Actual results:
Crash.

Expected results:
No crash.

Additional info:
Kernel version: kernel-3.5.0-2.fc17.x86_64

Comment 1 Dave Jones 2012-08-14 21:31:23 UTC
this sounds like a hardware problem of some kind.

Comment 2 Marc-Andre Laverdiere 2012-08-15 09:38:43 UTC
That is possible. But it hasn't happened in other kernels...

Comment 3 Justin M. Forbes 2012-09-06 19:25:03 UTC
Is this still happening with 3.5.3? If so, can you boot into the last 3.4 kernel and see if it reproduces there?