Kernel panic at boot after upgrading to linux-3.15.8-1

Giacomo Ritucci · 2014-08-03 22:12:23

After upgrading to linux-3.15.8-1 arch panics at boot.

Using linux-lts-3.14.15-1 I can boot correctly.

This is the panic I get (click to enlarge)

http://i.imgur.com/u2qE7iF.jpg

Does it happens to anyone else?

-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

ewaller · 2014-08-03 22:15:44

What file systems are you using?

anatolik · 2014-08-03 23:11:50

Your log says "junk in compressed initramfs". I suggest you to boot from USB live image, arch-chroot into your current installation and then recreate the initramfs with "mkinitcpio -p linux".

Giacomo Ritucci · 2014-08-05 18:22:10

I'm using ext4:

$ mount
...
/dev/sdb1 on / type ext4 (rw,relatime,data=ordered)
...

I booted from live image and recreated initramfs, also using "cat" as compression option in "/etc/mkinitcpio.conf", but still no luck: same panic message.

Last edited by Giacomo Ritucci (2014-08-05 18:23:00)

anatolik · 2014-08-05 18:46:27

Giacomo Ritucci wrote:

but still no luck: same panic message.

What bootloader are you using? Post its config file. Does it use correct path to your *.img file?

Post us output of mkinitcpio when you regenerate the image.

If you have multiple disks/partitions make sure you mount correct partition. Make sure that correct /boot/*.img (or whatever location you use for initrd) files are updated. Check its modification date with 'ls -l'. Show us output of lsblk (when you run from Live USB).

Giacomo Ritucci · 2014-08-07 21:25:37

I'm using grub:

[gcm@arch ~]$ pacman -Qi grub
Name           : grub
Version        : 1:2.02.beta2-4
...

/boot/grub/grub.conf: http://pastie.org/pastes/9453698/text?k … rdkt1mnhew
/etc/default/grub: http://pastie.org/pastes/9453847/text?k … nphmftpujw

Images: linux is the one that fails, linux-lts works:

[gcm@arch ~]$ ls -l /boot/                                                                                                                                              
total 86404
drwxr-xr-x 6 root root     4096  4 ago 01.39 grub
-rw-r--r-- 1 root root 51813888  4 ago 01.46 initramfs-linux-fallback.img
-rw-r--r-- 1 root root  8667136  5 ago 20.20 initramfs-linux.img
-rw-r--r-- 1 root root 16993951  3 ago 23.26 initramfs-linux-lts-fallback.img
-rw-r--r-- 1 root root  3190799  3 ago 23.26 initramfs-linux-lts.img
-rw-r--r-- 1 root root  3917152  5 ago 20.20 vmlinuz-linux
-rw-r--r-- 1 root root  3880528  1 ago 00.43 vmlinuz-linux-lts

Image generation output:

[gcm@arch ~]$ sudo mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.15.8-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.15.8-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

This is the lsblk output (booting from linux-lts)

[gcm@arch ~]$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 232,9G  0 disk 
├─sda1   8:1    0   100M  0 part 
├─sda2   8:2    0 203,6G  0 part 
└─sda3   8:3    0  29,2G  0 part 
sdb      8:16   0 931,5G  0 disk 
└─sdb1   8:17   0 931,5G  0 part /

sda is the internal hard drive (windows, for my wife) sdb is the external usb drive with my arch linux installation

Thanks for looking into this.

anatolik · 2014-08-07 21:44:14

hmm.. if initramfs fails to load but initramfs-lts is loaded fine then it sounds like initramfs is corrupted. Could you please run
lsinitcpio /boot/initramfs-linux.img
to check the archive content?

The grub config looks fine, but I can say it for sure as I use syslinux bootloader.

One more thing to try - try to unplug the external drive and boot with LTS and non-LTS kernels. Is the result same as before?

Giacomo Ritucci · 2014-08-09 11:25:15

I just found out that the image generated by the last mkinitcpio -p linux (the one I run just to post the output) works and I don't know why.

If you think that it's worth to investigate further, I'll try to reproduce the problem.

Thanks for your time antolik.

Giacomo Ritucci · 2014-08-13 16:59:29

Happened again, after upgrading to linux-3.16-2

I booted from a live SDHC, mounted my system, entered into a chroot and run mkinicpio -p linux and now I can boot correctly from linux-3.16-2

It seems that sometimes the image is not correctly generated and I need to generate it again.

My arch is installed on an external usb disk, can this be related to these failures?

Maybe when I reboot after a kernel upgrade, image data is not fully written to disk yet?

This is the command line I use to reboot the system:

sudo sync && sudo shutdown -r +1 && exit

mischa · 2014-08-24 12:29:03

I had the same problem: Unbootable system after kernel update. Sometimes there had been errors in output of mkinitcpio, sometimes not. It seems, the error messages (like described here: https://bbs.archlinux.org/viewforum.php?id=185265) may have nothing to do with the broken image.
I downgraded to mkinitcpio version 17-1 and since then I had no problems.

Last edited by mischa (2014-08-24 12:39:15)

Giacomo Ritucci · 2014-08-26 20:55:58

Yes, this maybe is a mkinitcpio problem. On my arch installation I have mkinitcpio 18 installed and it creates corrupted images, on the "live" recovery system I have mkinitcpio 17 and it works fine.

Diff between mkinitcpio versions 17 and 18: http://pastie.org/9504961

I see a lot of changes about drivers/usb/storage and my system boots from external usb disk.

I absolutely don't know if this is related, but when I have some spare time I'd like to roll back those changes and see if the issue remains.

Arch Linux

#1 2014-08-03 22:12:23

Kernel panic at boot after upgrading to linux-3.15.8-1

#2 2014-08-03 22:15:44

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#3 2014-08-03 23:11:50

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#4 2014-08-05 18:22:10

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#5 2014-08-05 18:46:27

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#6 2014-08-07 21:25:37

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#7 2014-08-07 21:44:14

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#8 2014-08-09 11:25:15

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#9 2014-08-13 16:59:29

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#10 2014-08-24 12:29:03

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

#11 2014-08-26 20:55:58

Re: Kernel panic at boot after upgrading to linux-3.15.8-1

Board footer