Bug 751232 - Init fails to load with 2.6.40 kernel
Summary: Init fails to load with 2.6.40 kernel
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-04 00:01 UTC by John Gray
Modified: 2012-06-08 08:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-08 08:44:37 UTC
Type: ---


Attachments (Terms of Use)
Kernel messages captured via serial console (23.85 KB, text/plain)
2011-11-04 00:01 UTC, John Gray
no flags Details

Description John Gray 2011-11-04 00:01:21 UTC
Created attachment 531674 [details]
Kernel messages captured via serial console

Description of problem:

System displays a panic (unable to load init) when using initramfs which matches kernel version. Worked OK with kernel 2.6.38.8-35, which I'm still having to boot from, but not with any version of 2.6.40.


Version-Release number of selected component (if applicable):2.6.40.4-5, 2.6.40.6-0


How reproducible:


Steps to Reproduce:
1. Power on system, select 2.6.40 kernel from Grub menu
2.
3.
  
Actual results:
Kernel panic:
[   10.525076] Failed to execute /init
[   10.567098] Kernel panic - not syncing: No init found.  Try passing init= opt
ion to kernel. See Linux Documentation/init.txt for guidance.
[   10.716284] Pid: 1, comm: swapper Not tainted 2.6.40.4-5.fc15.x86_64 #1
[   10.795590] Call Trace:
[   10.825035]  [<ffffffff8147f3df>] panic+0x91/0x19c
[   10.882532]  [<ffffffff8147d195>] init_post+0xc5/0xc5
[   10.943174]  [<ffffffff81b66ce9>] kernel_init+0x153/0x153
[   11.007957]  [<ffffffff8104fb0d>] ? schedule_tail+0x27/0x6c
[   11.074837]  [<ffffffff8148f964>] kernel_thread_helper+0x4/0x10
[   11.145859]  [<ffffffff81b66b96>] ? start_kernel+0x3d5/0x3d5
[   11.213780]  [<ffffffff8148f960>] ? gs_change+0x13/0x13



Expected results:
System should boot normally


Additional info: Attached results of hooking up a serial console to capture the boot messages

Although the messages are for the earlier kernel version, the same thing happens with the newer one - it's just a pain to get the serial console set up that I haven't captured a newer set.

Grub.conf (relevant entries):
default=0
timeout=5
splashimage=(hd0,3)/boot/grub/splash.xpm.gz

title Fedora (2.6.40.6-0.fc15.x86_64)
        root (hd0,3)
        kernel /boot/vmlinuz-2.6.40.6-0.fc15.x86_64 ro root=UUID=1bd6a92b-ff47-4bcb-8002-074ade339266 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=uk
        initrd /boot/initramfs-2.6.40.6-0.fc15.x86_64.img

title Fedora (2.6.38.8-35.fc15.x86_64)
        root (hd0,3)
        kernel /boot/vmlinuz-2.6.38.8-35.fc15.x86_64 ro root=UUID=1bd6a92b-ff47-4bcb-8002-074ade339266 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=uk
        initrd /boot/initramfs-2.6.38.8-35.fc15.x86_64.img

NB If I edit the 2.6.40 grub entry to load the 2.6.38.8 initramfs, init loads (though the drivers are wrong and therefore the system doesn't find the root device, it is capable of dropping me to a shell)

Comment 1 Dave Jones 2011-11-07 17:25:09 UTC
does /boot/initramfs-2.6.40.6-0.fc15.x86_64.img exist ?
Is it roughly the same size as the other initramfs files ?

Try recreating it with dracut /boot/initramfs-2.6.40.6-0.fc15.x86_64.img 2.6.40.6-0.fc15.x86_64

Comment 2 John Gray 2011-11-08 20:33:48 UTC
Thanks for the reply. The 2.6.40 initramfs is smaller than the 2.6.38 one:

# ls /boot/initramfs*

-rw-r--r--. 1 root root 14445734 Jul 16 08:48 /boot/initramfs-2.6.38.8-35.fc15.x86_64.img
-rw-r--r--. 1 root root 11629993 Oct  9 22:38 /boot/initramfs-2.6.40.6-0.fc15.x86_64.img

# dracut --force /boot/initramfs-2.6.40.6-0.fc15.x86_64.img
W: Possible missing firmware "ql2400_fw.bin" for kernel module "qla2xxx.ko"
W: Possible missing firmware "ql2322_fw.bin" for kernel module "qla2xxx.ko"
W: Possible missing firmware "ql2300_fw.bin" for kernel module "qla2xxx.ko"
W: Possible missing firmware "ql2200_fw.bin" for kernel module "qla2xxx.ko"
W: Possible missing firmware "ql2100_fw.bin" for kernel module "qla2xxx.ko"
W: Possible missing firmware "cbfw_fc.bin" for kernel module "bfa.ko"
W: Possible missing firmware "ctfw_cna.bin" for kernel module "bfa.ko"
W: Possible missing firmware "ctfw_fc.bin" for kernel module "bfa.ko"
W: Possible missing firmware "aic94xx-seq.fw" for kernel module "aic94xx.ko"

# ls /boot/initramfs*
-rw-r--r--. 1 root root 14445734 Jul 16 08:48 /boot/initramfs-2.6.38.8-35.fc15.x86_64.img
-rw-r--r--. 1 root root 10990984 Nov  8 20:19 /boot/initramfs-2.6.40.6-0.fc15.x86_64.img

 - and no improvement unfortunately. It's possible I may have tried running dracut before while troubleshooting, so the previous 2.6.40 initramfs may not be the distributed one.

I can make the initramfs file available somewhere if that is useful?

Comment 3 Chuck Ebbert 2011-11-29 08:46:53 UTC
Do you have all the fedora updates installed, including dracut and lvm2? Also, the current kernel is now 2.6.41, have you tried that?

Comment 4 John Gray 2011-12-15 00:17:45 UTC
I have tried the most recent kernel (2.6.41.5-1) and the issue remains (I have now grabbed another set of kernel messages for that, but they are not really different).

dracut & lvm:

# rpm -q dracut
dracut-009-12.fc15.noarch 

# lvm version
  LVM version:     2.02.84(2) (2011-02-09)
  Library version: 1.02.63 (2011-02-09)
  Driver version:  4.19.1
# rpm -q lvm2
lvm2-2.02.84-4.fc15.x86_64

I believe that all my updates are in order - I did a yum update today and plenty of new stuff appeared.

Comment 5 Sami Farin 2012-02-29 11:19:37 UTC
I have this problem with dracut-016. 014 works in booting, but in rebooting it tries to unmount /usr and predictably it fails; then it says /shutdown: line 97: reboot: command not found; then kernel panic, attempted to kill init.  

cmdline is
rw root=LABEL=wd1root rootfstype=xfs i915.modeset=1 vga=6 noisapnp enforcing=0 selinux=0 printk.time=1 log_buf_len=512k nodmraid nompath raid=noautodetect random_debug=0 processor.max_cstate=0 usbhid.mousepoll=1 memtest=0 rd.dm=0 rd.md=0 rd.lvm=0 rd.luks=0 rd.info plymouth.enable=0 vconsole.keymap=fi-latin9 vconsole.font=lat9w-08 SYSFONTACM=iso15 LANG=en_US.UTF-8

Comment 6 Harald Hoyer 2012-06-07 17:44:46 UTC
(In reply to comment #4)
> I have tried the most recent kernel (2.6.41.5-1) and the issue remains (I
> have now grabbed another set of kernel messages for that, but they are not
> really different).
> 
> dracut & lvm:
> 
> # rpm -q dracut
> dracut-009-12.fc15.noarch 
> 
> # lvm version
>   LVM version:     2.02.84(2) (2011-02-09)
>   Library version: 1.02.63 (2011-02-09)
>   Driver version:  4.19.1
> # rpm -q lvm2
> lvm2-2.02.84-4.fc15.x86_64
> 
> I believe that all my updates are in order - I did a yum update today and
> plenty of new stuff appeared.

you can try: https://admin.fedoraproject.org/updates/dracut-009-15.fc15

Comment 7 Harald Hoyer 2012-06-07 17:50:50 UTC
(In reply to comment #5)
> I have this problem with dracut-016. 014 works in booting, but in rebooting
> it tries to unmount /usr and predictably it fails; then it says /shutdown:
> line 97: reboot: command not found; then kernel panic, attempted to kill
> init.  
> 
> cmdline is
> rw root=LABEL=wd1root rootfstype=xfs i915.modeset=1 vga=6 noisapnp
> enforcing=0 selinux=0 printk.time=1 log_buf_len=512k nodmraid nompath
> raid=noautodetect random_debug=0 processor.max_cstate=0 usbhid.mousepoll=1
> memtest=0 rd.dm=0 rd.md=0 rd.lvm=0 rd.luks=0 rd.info plymouth.enable=0
> vconsole.keymap=fi-latin9 vconsole.font=lat9w-08 SYSFONTACM=iso15
> LANG=en_US.UTF-8

please open a seperate bug for that.

Comment 8 Sami Farin 2012-06-07 18:05:21 UTC
(In reply to comment #7)

I don't have this problem anymore.

Comment 9 John Gray 2012-06-07 19:21:17 UTC
> 
> you can try: https://admin.fedoraproject.org/updates/dracut-009-15.fc15

I have now upgraded to F16 and the problem went away with the upgrade, so I'm afraid I can't comment on whether that fixes it, sorry!


Note You need to log in before you can comment on or make changes to this bug.