Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux 4.18 kernel panic #2628

Closed
lbolla opened this issue Sep 11, 2018 · 4 comments
Closed

Linux 4.18 kernel panic #2628

lbolla opened this issue Sep 11, 2018 · 4 comments

Comments

@lbolla
Copy link

lbolla commented Sep 11, 2018

System

  • xuname:
    Void 4.17.19_1 x86_64 GenuineIntel uptodate rFFF

  • package:
    linux-4.18

Expected behavior

Kernel starts as expected

Actual behavior

I get a kernel panic on startup with message:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Starting kernel 4.17.19 works.

I noticed that Grub's /boot/grub/grub.cfg is different between 4.17 series and 4.18.
E.g.

                echo    'Loading Linux 4.17.19_1 ...'
                linux   /vmlinuz-4.17.19_1 root=/dev/mapper/pool-root ro  loglevel=4 slub_debug=P page_poison=1 rd.auto=1 cryptdevice=/dev/sda2 root=/dev/mapper/pool-root
                echo    'Loading initial ramdisk ...'
                initrd  /initramfs-4.17.19_1.img

but

                echo    'Loading Linux 4.18.6_1 ...'
                linux   /vmlinuz-4.18.6_1 root=/dev/mapper/pool-root ro single 
        }

Note the missing initrd command.
I tried to run grub-mkconfig manually and nothing changed.
/initramfs files are present in /boot for all images.

Steps to reproduce the behavior

Just xi -u the latest kernel.

@Hoshpak
Copy link
Member

Hoshpak commented Sep 11, 2018

This usually happens when /boot runs out of disk space while generating the initrd. Please check that enough disk space is available and regenerate the initrd with xbps-reconfigure -f linux4.18.

@lbolla
Copy link
Author

lbolla commented Sep 11, 2018

Thanks! That seems indeed to be the case. Is there a recommended way to drop obsolete kernel images from /boot?

@Hoshpak
Copy link
Member

Hoshpak commented Sep 11, 2018

Yes, it's the vkpurge script that comes in the base-files package. It can either remove specific kernel versions or all obsolete (= not the currently running kernel, not held by an installed linux package) kernels.

@lbolla
Copy link
Author

lbolla commented Sep 11, 2018

Thanks, that did the trick.

@lbolla lbolla closed this as completed Sep 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants