Bug 703677

Summary:	Crash on Atom processor
Product:	[Fedora] Fedora	Reporter:	eric
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	15	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-30 17:04:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description eric 2011-05-11 00:55:17 UTC

Description of problem: Computer crashes at least once during start up and at random times while computer is being used.  Some of these crashes occur seemingly at random.

Seems to occur most often before the LUKS password request on startup.  The 2.6.35.13-91.fc14.i686 version let me get to the GNOME sign-in screen and then crashed twice.  Had to revert to 2.6.35.12-88.fc14.i686


Version-Release number of selected component (if applicable):
2.6.35.13-91.fc14.i686
and
2.6.35.12-90.fc14.i686

Seems to be okay under 2.6.35.12-88.fc14.i686


How reproducible: Randomly but often


Steps to Reproduce:
1. Boot computer
2. Hold breath and hope the computer doesn't crash
3. Crash
  
Actual results:
Crash

Expected results:
Not crash

Additional info:
I tried to gleam any useful information from /var/log/messages but I'm not finding anything consistent.

Comment 1 Josh Boyer 2011-08-24 14:45:09 UTC

Is this still happening with kernel-2.6.35.14-95.fc14

Comment 2 eric 2011-08-25 11:44:02 UTC

This is still happening with 2.6.40-4.fc15.

This may be a hardware issue but it seems to be quite random.  I, too, have not been able to gleam any useful information from the logs.

Comment 3 Chuck Ebbert 2011-08-29 21:38:10 UTC

We really need to see an oops report to diagnose this problem.

Comment 4 Dave Jones 2011-09-01 18:50:19 UTC

might be worth running memtest86 overnight on it if you suspect it might be hardware.