Bug 1293901

Summary:	Fedora 23 causes "Kernel panic - not syncing: Timeout: Not all cpus entered broadcast exception handler" followed by reboot
Product:	[Fedora] Fedora	Reporter:	Joe Thompson <redhat-bugs>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	23	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
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:	2016-06-24 11:53:27 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:

Description Joe Thompson 2015-12-23 12:52:45 UTC

Description of problem: Fedora 23 quickly dies with a kernel panic


Version-Release number of selected component (if applicable): 4.2.8-300.fc23.x86_64 (I think; the issue was observed both with the 23-10 Workstation live CD and a failed but functional upgrade from F22 to F23 Workstation a few days ago)


How reproducible: Always within a few minutes of boot, often within seconds


Steps to Reproduce:
1. Boot Fedora 23 on my laptop
2. Do anything moderately resource-intensive (dnf operations are usually good), or just wait

Actual results: Kernel panic


Expected results: Normal operation


Additional info: The affected laptop is a Sager NP8651, basically a rebadged Clevo P650SE.  A Clevo P650SA that I own runs Fedora 23 fine.  Notably, the affected laptop has the same CPU (Core i7-5700HQ) as the one in this report of the same kernel panic on the Arch Linux forums:

https://bbs.archlinux.org/viewtopic.php?id=203010

Comment 1 Joe Thompson 2016-02-24 10:53:51 UTC

More info from the kernel bugzilla:

https://bugzilla.kernel.org/show_bug.cgi?id=103351

This seems to be a firmware bug triggered by glibc use of certain processor features that are incorrectly advertised by the processor.  Apparently all that's needed is an early-mode firmware update.

Comment 2 Joe Thompson 2016-06-24 04:22:58 UTC

Further data point: downloading and applying the Intel firmware update package for my CPU allowed me to successfully upgrade to and use Fedora 23 (and use F23 and CoreOS virtual machines under F22 before I upgraded, which had also triggered the problem).

Comment 3 Josh Boyer 2016-06-24 11:53:27 UTC

Thanks for letting us know.