Bug 921516 - 3.8.2-206.fc18.x86_64 crash
Summary: 3.8.2-206.fc18.x86_64 crash
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-14 11:06 UTC by vikram goyal
Modified: 2013-07-13 11:36 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-13 11:36:27 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
screen photo through mobile. (1.97 MB, image/jpeg)
2013-03-14 11:06 UTC, vikram goyal 		no flags Details
screen photo 2 through mobile (2.10 MB, image/jpeg)
2013-03-14 11:10 UTC, vikram goyal 		no flags Details
View All

Description vikram goyal 2013-03-14 11:06:08 UTC 
Created attachment 709975 [details]
screen photo through mobile.

Description of problem:
Two times my system has suddenly frozen under the same kernel version with CapsLock & ScrollLock blinking & crash log displayed on the screen.

I have captured the screen with my mobile & want to share it.

Hope it is readable.

Thanks

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


How reproducible:


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


Expected results:


Additional info:
Comment 1 vikram goyal 2013-03-14 11:10:56 UTC 
Created attachment 709976 [details]
screen photo 2 through mobile
Comment 2 Josh Boyer 2013-07-02 19:48:06 UTC 
Unfortunately that only captures the secondary oops.  Have you seen this again on a 3.9.y kernel?
Comment 3 vikram goyal 2013-07-13 08:43:35 UTC 
I am currently running following kernel version:

Linux localhost.localdomain 3.9.9-201.fc18.i686 #1 SMP Fri Jul 5 17:42:49 UTC 2013 i686 i686 i386 GNU/Linux

The problem did not reappear else I would have reported it.

Thanks
Comment 4 Josh Boyer 2013-07-13 11:36:27 UTC 
Great, thank you for letting us know.
Note You need to log in before you can comment on or make changes to this bug.