Bug 819624

Summary: System does not boot - Kernel Panic
Product: [Fedora] Fedora Reporter: Szymon Gruszczynski <sz.gruszczynski>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: fedora-bugzilla, gansalmon, itamar, jonathan, kernel-maint, kzak, madhu.chinakonda, me, pwouters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-14 20:53:05 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:
Attachments:
Description Flags
a photo of it (sorry for quality) none

Description Szymon Gruszczynski 2012-05-07 19:00:22 UTC 
Created attachment 582763 [details]
a photo of it (sorry for quality)

Description of problem:
Hi! 
After I've installed F17 (beta), 64 bit version, after update to the newest available packages on default repos, and after I've rebooted machine into the newest (default) kernel, i got that kernel panic error:

Loading Fedora (3.3.4-4.fc17.x86_64)
Loading initial ramdisk ...
[ 2.892504] Kernel panic - not syncing: stack-protector: Kernel stack corrupted in: ffffffff81b14c7e
[ 2.892506]
[ 2.892872] [<ffffffff815e226b>] panic+0xba/0x1c6
[ 2.892961] [<ffffffff81b14c7e>] ? printk_all_paritions+0x259/0x26xb
[ 2.893057] [<ffffffff810566bb>] __stack_chk_fail+0x1b/0x20
[ 2.893147] [<ffffffff81b15c7e>] printk_all_paritions+0x259/0x26xb
[ 2.893244] [<ffffffff81aedfe0>] mount_block_root+0x1bc/0x27f
[ 2.893336] [<ffffffff81aee0fa>] mount_root+0x57/0x5b
[ 2.893425] [<ffffffff81aee23b>] prepare_namespace+0x13d/0x176
[ 2.893522] [<ffffffff8107eec0>] ? release_tgcred.isra.4+0x330/0x30
[ 2.893616] [<ffffffff81aedd60>] kernel_init+0x155/0x15a
[ 2.893708] [<ffffffff81087b97>] ? schedule_tail+0x27/0xb0
[ 2.893800] [<ffffffff815f4d24>] kernel_thread_helper+0x5/0x10
[ 2.893893] [<ffffffff81aedc0b>] ? start_kernel+0x3c5/0x3c5
[ 2.893984] [<ffffffff815f4d20>] ? gs_change+0x13/0x13
_

Version-Release number of selected component (if applicable):
kernel-3.3.4-4.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1. press the power button
2. select that kernel
3. press enter
  
Actual results:
boot hangs

Expected results:
boot does not hangs

Additional info:
http://wklej.org/id/747841/

lspci -v
Comment 1 Dave Jones 2012-05-07 20:19:16 UTC 
what does the partition table look like on this machine ?
Comment 2 Szymon Gruszczynski 2012-05-07 21:19:13 UTC 
http://imageshack.us/photo/my-images/535/snapshot1kj.png/
I hope it will help :)
Comment 3 Szymon Gruszczynski 2012-05-07 21:21:33 UTC 
Ah, I just wanted to add: that's all (i.e. the error I wrote in first post)- there is nothing more apart from the stuff I've written.
Comment 4 Dave Jones 2012-05-07 22:33:33 UTC 
hmm, doesn't look too unusual.  What does parted -l say ?
Comment 5 Dave Jones 2012-05-07 22:34:58 UTC 
I noticed also that Fedora is on /dev/sdb.  It might be that it's getting confused by something on another drive, so the parted output will show all connected drives.
Comment 6 Szymon Gruszczynski 2012-05-07 23:19:35 UTC 
http://wklej.org/id/748085/
yes, F17 is installed on /dev/sdb, altogether with grub (installed in mbr of that drive), that's the first device to boot from in bios (uefi). It also happens when / (with exception of /boot) is on LVM (if that matters)
Comment 7 Szymon Gruszczynski 2012-05-07 23:33:28 UTC 
btw, any ideas why neither cfdisk, or parted recognised filetype on /dev/sdc? its the same drive as /dev/sda, with one rather large NTFS partition o.O (used mostly for backup of system + data)
Comment 8 Matthew Gillen 2012-05-30 05:27:21 UTC 
I had this kernel panic with the Fedora 17 release (DVD via NFS upgrade from Fedora 16).

Grub2 spits out some error message right before it displays the grub menu (I assume the error message is about not finding the background image or something).  There is a fedora 17 entry as the default.  Choosing that got me a kernel panic.  The 'advanced' menu was all my Fedora 16 kernels (luckily they were still there).  I booted one of those and it worked fine.  Did a "yum install kernel" since "rpm -q kernel" told me I didn't have any f17 kernels installed (which is odd, because I had a grub2 entry for it from the installer).  After that, booting the default F17 kernel from grub worked fine.

So it seems somehow the F17 kernel didn't install correctly.  I did have the rpmfusion nvidia drivers installed in F16, but usually the install/upgrade process will do a force upgrade of core system stuff like the kernel.
Comment 9 Catalin BOIE 2012-05-31 06:20:46 UTC 
Just upgraded to Fedora 17 and get this panic with 3.3.7-1. Using Fedora _16_ kernel 3.3.7-1 does not generate this panic. Strange.
Comment 10 Paul Wouters 2012-07-12 19:45:20 UTC 
I have this with kernel 3.4.4-4, but not with 3.4.4-2 on f16

photo of panic: http://twitpic.com/a6uxiy

Note that system performed an selinux relabel once it booted in 3.4.4-2. Not sure if that is related.
Comment 11 Josh Boyer 2013-01-08 16:12:26 UTC 
Are people still seeing this with the 3.6.10 or newer kernel updates?
Comment 12 Matthew Gillen 2013-01-08 16:21:08 UTC 
I've done a few 'preupgrade'-based upgrades recently (from F16 -> F17) and have not had this problem.  3.6.10 was the version that preupgrade started my recent F17 install with, so it's possible that version fixed it.

When I had this problem back in May (see comment #8), it was on a single-disk laptop (with a separate /boot partition).  When I had success last week, it was on a multi-disk RAID server-class machine, also with a separate /boot partition.