Bug 707976 - Kernel Panic while using X
Summary: Kernel Panic while using X
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
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: 2011-05-26 13:25 UTC by Thomas Kallenberg
Modified: 2011-10-05 16:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-05 16:17:03 UTC
Type: ---

Attachments (Terms of Use)
Crash while using eclipse (783.34 KB, image/jpeg)
2011-05-26 13:25 UTC, Thomas Kallenberg 		no flags Details
Second crash while nobody was working on the machine (653.90 KB, image/jpeg)
2011-05-26 13:26 UTC, Thomas Kallenberg 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Thomas Kallenberg 2011-05-26 13:25:11 UTC 
Created attachment 501079 [details]
Crash while using eclipse

Description of problem: Worikng with Eclipse the Kernel suddenly paniced. No Idea what the problem is.


Version-Release number of selected component (if applicable):
2.6.38.6-27.fc15.i686

How reproducible: 


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: This happend two times. both times the system was totaly unresponsive. Both time i could take a photo. Could be two different problems.
Comment 1 Thomas Kallenberg 2011-05-26 13:26:48 UTC 
Created attachment 501081 [details]
Second crash while nobody was working on the machine
Comment 2 Josh Boyer 2011-09-27 14:40:57 UTC 
Have you seen this on the latest 2.6.40.x F15 kernel?
Comment 3 Thomas Kallenberg 2011-09-29 15:00:21 UTC 
Hi.

Sorry, cannot tell. since my laptop running on nvidia broke down.
Comment 4 Josh Boyer 2011-10-05 16:17:03 UTC 
Ok, thank you for letting us know.  We're going to close this bug out.  If you happen to see it again on a different machine, please reopen.
Note You need to log in before you can comment on or make changes to this bug.