[Unstable Update] 2019-05-18

Just updated my Manjaro KDE unstable and after rebooting I was thrown into a root shell.
At the end of the pacman.log file I see this:

[2019-05-18 05:38] [ALPM] transaction completed
[2019-05-18 05:38] [ALPM] running '60-linux419.hook'...
[2019-05-18 05:39] [ALPM] running '90-linux419.hook'...
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default'
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64.img
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Starting build: 4.19.44-1-MANJARO
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64.img
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Image generation successful
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback'
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Starting build: 4.19.44-1-MANJARO
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2019-05-18 05:39] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64-fallback.img
[2019-05-18 05:39] [ALPM-SCRIPTLET] ==> Image generation successful
[2019-05-18 05:39] [ALPM] running '99-grub.hook'...
[2019-05-18 05:39] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2019-05-18 05:39] [ALPM-SCRIPTLET] Found theme: /usr/share/grub/themes/manjaro/theme.txt
[2019-05-18 05:39] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-5.1-x86_64
[2019-05-18 05:39] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.1-x86_64.img
[2019-05-18 05:39] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-5.1-x86_64-fallback.img
[2019-05-18 05:39] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.19-x86_64
[2019-05-18 05:39] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
[2019-05-18 05:39] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
[2019-05-18 05:39] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2019-05-18 05:39] [ALPM-SCRIPTLET] done
[2019-05-18 05:39] [ALPM] running 'detect-old-perl-modules.hook'...
[2019-05-18 05:39] [ALPM] running 'gdk-pixbuf-query-loaders.hook'...
[2019-05-18 05:39] [ALPM] running 'gtk-update-icon-cache.hook'...
[2019-05-18 05:39] [ALPM] running 'systemd-daemon-reload.hook'...
[2019-05-18 05:39] [ALPM] running 'systemd-sysusers.hook'...
[2019-05-18 05:39] [ALPM] running 'systemd-tmpfiles.hook'...
[2019-05-18 05:39] [ALPM] running 'systemd-udev-reload.hook'...
[2019-05-18 05:39] [ALPM] running 'systemd-update.hook'...
[2019-05-18 05:39] [ALPM] running 'texinfo-install.hook'...
[2019-05-18 05:39] [ALPM] running 'update-ca-trust.hook'...
[2019-05-18 05:39] [ALPM] running 'update-desktop-database.hook'...
[2019-05-18 05:39] [ALPM] running 'update-mime-database.hook'...
[2019-05-18 05:43] [PACMAN] Running '/usr/bin/pacman -U /tmp/trizen-jan/vivaldi/vivaldi-2.5.1525.43-1-x86_64.pkg.tar.xz'
[2019-05-18 05:43] [ALPM] transaction started
[2019-05-18 05:43] [ALPM] upgraded vivaldi (2.5.1525.41-1 -> 2.5.1525.43-1)
[2019-05-18 05:43] [ALPM] transaction completed
[2019-05-18 05:43] [ALPM] running 'gtk-update-icon-cache.hook'...
[2019-05-18 05:43] [ALPM] running 'systemd-update.hook'...
[2019-05-18 05:43] [ALPM] running 'update-desktop-database.hook'...
[2019-05-18 05:43] [PACMAN] Running 'pacman -Scc'

To me it all looks fine.
Still I got this when rebooting:


I writes about hibernation, something I never use.
Am now running from a live USB. What should I do to make the system work again, where do I look?
Thanks.

have you tried running fallback kernel from advanced menu in grub.

No, I did not. Have to change grub first cause the timer to show the menu is set to zero.
Will do, thank you for your answer.

I booted using the Grub menu and received the exact same error using the fallback line (2nd line in the Grub menu)
Then I booted into the 4.19 kernel and this works fine. I did receive a 5.1 kernel update this morning so I guess something is wrong with it.
Thank you again for pointing me into the right direction.

Seems some issue with linux51 and resume hook. We might fix it on Monday.

Thanks Phil, will use 4.19 till then.

Please try with revision 2 again.
https://lists.manjaro.org/pipermail/manjaro-packages/Week-of-Mon-20190513/022739.html

2 Likes

@philm, kernel 5.1.3-2 works fine. Laptop boots up just fine.
Thanks for the fast help.

Seems to wipe out modules directories for kernel 5.0 & kernel 5.2 for me.

I have no idea where to find these modules, but here everything is just working fine so if I need those modules they can't be gone. If I don't need them (anymore): good riddance.

Occasionally a kernel update will cause other kernels issues by deleting their modules?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.