Bug 784429

Summary: Fedora 15 update kernel 2.6.41.9 panic at boot
Product: [Fedora] Fedora Reporter: Matthieu Araman <matzilla>
Component: dracutAssignee: dracut-maint
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dracut-maint, gansalmon, harald, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 19:50:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
kernel panic screenshot
none
yum.log
none
dracut.log
none
dracut.log for 2.6.41.10 none

Description Matthieu Araman 2012-01-24 21:56:54 UTC
Created attachment 557324 [details]
kernel panic screenshot

Description of problem:
Fedora 15
yum update install a new kernel
after reboot kernel panic !

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

How reproducible:
Always

Steps to Reproduce:
1.update F15 -> kernel is 2.6.41.9
2.reboot
3.grub screen trie to boot 2.6.41.9
  
Actual results:
panic (see screenshot)

Expected results:
boot normally

Additional info:
target 2.6.41.4 in grub (last kernel) boot ok
tried to redo a yum update but problem persist.

Comment 1 Josh Boyer 2012-01-24 23:27:44 UTC
My guess is that you don't have an initramfs generated for this kernel in /boot and/or you don't have an initrd line in the grub.conf entry for it.  We've seen a number of such issues recently with no real explanation.

Can you look for those two things, and also see if there are errors in /var/log/messages or the dracut/yum logs?

Comment 2 Matthieu Araman 2012-01-25 19:32:34 UTC
Created attachment 557506 [details]
yum.log

Comment 3 Matthieu Araman 2012-01-25 19:35:45 UTC
Created attachment 557507 [details]
dracut.log

Comment 4 Matthieu Araman 2012-01-25 19:40:22 UTC
yum.log -> I don't see any error messages.
kernel 2.6.41.9 install succesfully
dracut.log -> I don't see any error but I don't have a valid file to compare it with.

but initramfs file size doesn't look normal to me, see below so I think you were right and something has gone wrong generating this.
[mat@pluto boot]$ ls -l
total 55020
-rw-r--r--. 1 root root   124705 11 nov.  22:55 config-2.6.41.1-1.fc15.i686
-rw-r--r--. 1 root root   124704 29 nov.  13:01 config-2.6.41.4-1.fc15.i686
-rw-r--r--. 1 root root   124779 13 janv. 17:49 config-2.6.41.9-1.fc15.i686
drwxr-xr-x. 3 root root     1024  4 juin   2009 efi
-rw-r--r--. 1 root root   178436  2 juin   2011 elf-memtest86+-4.20
drwxr-xr-x. 2 root root     1024  5 juil.  2011 extlinux
drwxr-xr-x. 2 root root     1024 18 janv. 23:25 grub
-rw-r--r--. 1 root root 14809231 18 nov.  11:25 initramfs-2.6.41.1-1.fc15.i686.img
-rw-r--r--. 1 root root 14811787 26 déc.  17:14 initramfs-2.6.41.4-1.fc15.i686.img
-rw-r--r--. 1 root root  6330998 18 janv. 23:28 initramfs-2.6.41.9-1.fc15.i686.img
-rw-r--r--. 1 root root  1455096  5 juil.  2011 initrd-plymouth.img
drwx------. 2 root root    12288 11 juin   2009 lost+found
-rw-r--r--. 1 root root   176760  2 juin   2011 memtest86+-4.20
-rw-------. 1 root root  1886818 11 nov.  22:55 System.map-2.6.41.1-1.fc15.i686
-rw-------. 1 root root  1886813 29 nov.  13:01 System.map-2.6.41.4-1.fc15.i686
-rw-------. 1 root root  1811001 13 janv. 17:49 System.map-2.6.41.9-1.fc15.i686
-rwxr-xr-x. 1 root root  3969088 11 nov.  22:55 vmlinuz-2.6.41.1-1.fc15.i686
-rwxr-xr-x. 1 root root  3970176 29 nov.  13:01 vmlinuz-2.6.41.4-1.fc15.i686
-rwxr-xr-x. 1 root root  4400256 13 janv. 17:49 vmlinuz-2.6.41.9-1.fc15.i686
[mat@pluto boot]$

Comment 5 Matthieu Araman 2012-01-25 22:21:58 UTC
Created attachment 557543 [details]
dracut.log for 2.6.41.10

I upgraded to 2.6.41.10 successfully
attached is dracut.log
a diff between both log files show that was a big missing part at the end for the non working case. 
I've no idea why.

Comment 6 Dave Jones 2012-02-22 17:12:51 UTC
can you boot with rd.shell rd.debug, and stash the log files somewhere ?

(note, at this point in early boot, you'll likely have no udev running, so you might have to mknod /dev nodes by hand to access devices)

Comment 7 Harald Hoyer 2012-06-08 09:10:43 UTC
(In reply to comment #4)
> yum.log -> I don't see any error messages.
> kernel 2.6.41.9 install succesfully
> dracut.log -> I don't see any error but I don't have a valid file to compare
> it with.
> 
> but initramfs file size doesn't look normal to me, see below so I think you
> were right and something has gone wrong generating this.
...

> -rw-r--r--. 1 root root  6330998 18 janv. 23:28
> initramfs-2.6.41.9-1.fc15.i686.img

indeed, that looks fishy...

can you attach the output of
# lsinitrd initramfs-2.6.41.9-1.fc15.i686.img

Comment 8 Harald Hoyer 2012-06-08 09:11:08 UTC
oh, and attach your grub config file

Comment 9 Fedora End Of Life 2012-08-07 19:50:43 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping