Bug 825925

Summary: kernel panic on all kernel fedora17
Product: [Fedora] Fedora Reporter: brullek <brullek>
Component: 0xFFFFAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dwmw2, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, vascom2, yangqi89
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-25 09:46:56 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:
Embargoed:

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 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.