Bug 825925 - kernel panic on all kernel fedora17
Summary: kernel panic on all kernel fedora17
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: 0xFFFF
Version: 17
Hardware: Unspecified
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: 2012-05-29 06:09 UTC by brullek
Modified: 2012-06-25 09:46 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-25 09:46:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description brullek 2012-05-29 06:09:40 UTC 
Description of problem:
Don't boot kernel of Fedora 17.

Version-Release Fedora 17 :


Steps to Reproduce:
1. Boot kernel in grub
  
Actual results:
kernel panic or reboot

Screenshots:
1. http://itmages.ru/image/view/521227/059c1d84
2. http://itmages.ru/image/view/521228/6bd02b1b
Comment 1 brullek 2012-05-29 06:27:33 UTC 
proc: http://fpaste.org/ok3s/
mothenboard: gygabyte h77m-d3h
Comment 2 brullek 2012-05-29 11:09:03 UTC 
The problem manifests itself even in the kernel 3.3.7-1.fc17.x86_64
Comment 3 yangqi89 2012-05-30 06:24:50 UTC 
The same problems!

I munually changed all fc16 into fc17 in grub2

then I yum removed kernel-xxx.fc16. I thought now fc17 kernel is working.

it shuts down quite smoothly.

But no linux kernel in grub2 now!
Comment 4 brullek 2012-05-30 07:15:33 UTC 
Photo booting in singlemode:
http://itmag.es/3MmaG
http://itmag.es/31NAV
http://itmages.ru/image/view/534314/d681a168
http://itmag.es/3zPqO
http://itmag.es/207mv
http://itmag.es/4l0O
http://itmag.es/5EtHX
Comment 5 brullek 2012-05-30 10:18:14 UTC 
My hardware:
http://www.smolts.org/client/show/pub_0146a087-d427-42df-829b-d02ea1571815
Comment 6 brullek 2012-05-30 11:15:29 UTC 
The problem manifests itself even in
Fedora-17-x86_64-Live-KDE.iso
<http://mirror.yandex.ru/fedora/linux/releases/17/Live/x86_64/Fedora-17-x86_64-Live-KDE.iso>
Comment 7 brullek 2012-06-11 07:34:42 UTC 
The problem manifests itself even in the kernel 3.4.0-1.fc17.x86_64
1. http://itmag.es/2YIQp
2. http://itmag.es/6onIV
Comment 8 brullek 2012-06-18 08:18:46 UTC 
The problem manifests itself even in the kernel-3.4.2-4.fc17.x86_64
1. http://itmag.es/4Ax2K
2. http://itmag.es/3FVvi
Comment 9 brullek 2012-06-20 10:47:16 UTC 
The problem manifests itself even in the kernel-3.4.2-1.fc16.x86_64
Comment 10 brullek 2012-06-22 10:28:40 UTC 
The problem manifests itself even in the kernel-3.4.3-1.fc17.x86_64
1. http://itmag.es/2Ktgw
2. http://itmag.es/FXyB
Comment 11 Josh Boyer 2012-06-22 12:48:53 UTC 
Please run memtest86+ overnight.  From the little information we can see, it looks like something is either severely corrupting kernel memory or you might possibly have some bad hardware.
Comment 12 brullek 2012-06-25 09:46:56 UTC 
Thank you. The problem is solved. One of the four modules of RAM was corrupted. Replacing the RAM solved the problem.
Note You need to log in before you can comment on or make changes to this bug.