Boot hangs looks like stage 1 with kernel-default-4.12.14-lp150.12.19.2 on AMD and Intel

English Install/Boot/Login
1

Had to select lp150.12.16 kernel to get back online as the lp150.12.19 hangs at 4 seconds

I did updates on both my main computer AMD and my laptop Intel and both have almost the same hang - the Intel got to the Plymouth line and the AMD did not.

Did they release a kernel without testing the zypper install as the install looks normal this is the laptop log - (this had 42.1 -> 42.2 -> 42.3 -> Leap 15 upgrades via zypper dup as did all my machines).

What is the best way to remove the bad kernel - zypper rm kernel-default-4.12.14-lp150.12.19.2 seems not to be right was as it want to be reinstalled again.

zypper -n up
Retrieving repository ‘Packman 15.0 Repository’ metadata …[done]
Building repository ‘Packman 15.0 Repository’ cache …[done]
Repository ‘openSUSE-Leap-15.0-Non-Oss’ is up to date.
Repository ‘openSUSE-Leap-15.0-Oss’ is up to date.
Repository ‘openSUSE-Leap-15.0-Update’ is up to date.
Repository ‘TeamViewer - x86_64’ is up to date.
All repositories have been refreshed.
Loading repository data…
Reading installed packages…

The following 3 NEW packages are going to be installed:
kernel-default-4.12.14-lp150.12.19.2
kernel-default-devel-4.12.14-lp150.12.19.2 kernel-devel-4.12.14-lp150.12.19.1

The following 2 packages are going to be upgraded:
kernel-macros libQtWebKit4

2 packages to upgrade, 3 new.
Overall download size: 87.4 MiB. Already cached: 0 B. After the operation,
additional 359.0 MiB will be used.
Continue? [y/n/…? shows all options] (y): y
Retrieving package libQtWebKit4-4.8.7+2.3.4-lp150.2.77.x86_64
(1/5), 8.4 MiB ( 34.4 MiB unpacked)
Retrieving: libQtWebKit4-4.8.7+2.3.4-lp150.2.77.x86_64.rpm …[done (1.2 MiB/s)]
Retrieving package kernel-default-4.12.14-lp150.12.19.2.x86_64
(2/5), 56.8 MiB (298.9 MiB unpacked)
Retrieving: kernel-default-4.12.14-lp150.12.19.2.x86_64.rpm …[done (1.4 MiB/s)]
Retrieving package kernel-macros-4.12.14-lp150.12.19.1.noarch
(3/5), 2.7 MiB ( 7.0 KiB unpacked)
Retrieving: kernel-macros-4.12.14-lp150.12.19.1.noarch.rpm …[done (1.0 MiB/s)]
Retrieving package kernel-devel-4.12.14-lp150.12.19.1.noarch
(4/5), 14.2 MiB ( 56.0 MiB unpacked)
Retrieving delta: ./noarch/kernel-devel-4.12.14-lp150.12.16.1_lp150.12.19.1.noarch.drpm, 4.7 MiB
Retrieving: kernel-devel-4.12.14-lp150.12.16.1_lp150.12.19.1.n[done (1.1 MiB/s)]
Applying delta: ./kernel-devel-4.12.14-lp150.12.16.1_lp150.12.19.1.noarch.[done]
Retrieving package kernel-default-devel-4.12.14-lp150.12.19.2.x86_64
(5/5), 5.5 MiB ( 4.1 MiB unpacked)
Retrieving: kernel-default-devel-4.12.14-lp150.12.19.2.x86_[done (1021.0 KiB/s)]
Checking for file conflicts: …[done]
(1/5) Installing: libQtWebKit4-4.8.7+2.3.4-lp150.2.77.x86_64 …[done]
(2/5) Installing: kernel-default-4.12.14-lp150.12.19.2.x86_64 …[done]
Additional rpm output:
Creating initrd: /boot/initrd-4.12.14-lp150.12.19-default
dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.12.14-lp150.12.19-default 4.12.14-lp150.12.19-default
dracut: *** Including module: bash ***
dracut: *** Including module: systemd ***
dracut: *** Including module: warpclock ***
dracut: *** Including module: systemd-initrd ***
dracut: *** Including module: i18n ***
dracut: Could not find FONT_MAP none!
dracut: *** Including module: drm ***
dracut: *** Including module: plymouth ***
dracut: *** Including module: kernel-modules ***
dracut: *** Including module: resume ***
dracut: *** Including module: rootfs-block ***
dracut: *** Including module: suse-xfs ***
dracut: *** Including module: terminfo ***
dracut: *** Including module: udev-rules ***
dracut: Skipping udev rule: 40-redhat.rules
dracut: Skipping udev rule: 50-firmware.rules
dracut: Skipping udev rule: 50-udev.rules
dracut: Skipping udev rule: 91-permissions.rules
dracut: Skipping udev rule: 80-drivers-modprobe.rules
dracut: *** Including module: biosdevname ***
dracut: *** Including module: dracut-systemd ***
dracut: *** Including module: haveged ***
dracut: *** Including module: usrmount ***
dracut: *** Including module: base ***
dracut: *** Including module: fs-lib ***
dracut: *** Including module: shutdown ***
dracut: *** Including module: suse ***
dracut: *** Including modules done ***
dracut: *** Installing kernel module dependencies and firmware ***
dracut: *** Installing kernel module dependencies and firmware done ***
dracut: *** Resolving executable dependencies ***
dracut: *** Resolving executable dependencies done***
dracut: *** Hardlinking files ***
dracut: *** Hardlinking files done ***
dracut: *** Stripping files ***
dracut: *** Stripping files done ***
dracut: *** Generating early-microcode cpio image ***
dracut: *** Constructing GenuineIntel.bin ****
dracut: *** Store current command line parameters ***
dracut: Stored kernel commandline:
dracut: resume=UUID=613013a7-895c-4b31-8e2a-35d5a08b3c01
dracut: root=UUID=2c998170-c85c-4923-8f7d-bc8f3187dfa2 rootfstype=ext4 rootflags=rw,relatime,stripe=32753,data=ordered
dracut: *** Creating image file ‘/boot/initrd-4.12.14-lp150.12.19-default’ ***
dracut: *** Creating initramfs image file ‘/boot/initrd-4.12.14-lp150.12.19-default’ done ***

(3/5) Installing: kernel-macros-4.12.14-lp150.12.19.1.noarch …[done]
(4/5) Installing: kernel-devel-4.12.14-lp150.12.19.1.noarch …[done]
Additional rpm output:
Changing symlink /usr/src/linux from linux-4.12.14-lp150.12.16 to linux-4.12.14-lp150.12.19

(5/5) Installing: kernel-default-devel-4.12.14-lp150.12.19.2.x86_64 …[done]
Additional rpm output:
Changing symlink /usr/src/linux-obj/x86_64/default from …/…/linux-4.12.14-lp150.12.16-obj/x86_64/default to …/…/linux-4.12.14-lp150.12.19-obj/x86_64/default

There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run ‘zypper ps -s’ to list these programs.

2

It appears to go back you need to remove the old kernel and install -f the previous kernel to fix all the links in the /boot file system. I did a force grub2-mkconfig to clean the grub menu.

zypper rm kernel-default-4.12.14-lp150.12.19.2

zypper in -f kernel-default-4.12.14-lp150.12.16.1

grub2-mkconfig -o /boot/grub2/grub.cfg

Is there a better way?


PC113:~ # zypper rm kernel-default-4.12.14-lp150.12.19.2 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following package is going to be REMOVED:
  kernel-default-4.12.14-lp150.12.19.2

1 package to remove.
After the operation, 298.9 MiB will be freed.
Continue? [y/n/...? shows all options] (y): 
(1/1) Removing kernel-default-4.12.14-lp150.12.19.2.x86_64 ...............[done]
There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run 'zypper ps -s' to list these programs.
PC113:~ # zypper in -f kernel-default-4.12.14-lp150.12.16.1 
Loading repository data...
Reading installed packages...
Forcing installation of 'kernel-default-4.12.14-lp150.12.16.1.x86_64' from repository 'openSUSE-Leap-15.0-Update'.
Resolving package dependencies...

The following package is going to be reinstalled:
  kernel-default-4.12.14-lp150.12.16.1

1 package to reinstall.
Overall download size: 56.0 MiB. Already cached: 0 B. No additional space will
be used or freed after the operation.
Continue? [y/n/...? shows all options] (y): 
Retrieving package kernel-default-4.12.14-lp150.12.16.1.x86_64
                                           (1/1),  56.0 MiB (298.8 MiB unpacked)
Retrieving: kernel-default-4.12.14-lp150.12.16.1.x86_64.rpm ..[done (3.0 MiB/s)]
Checking for file conflicts: .............................................[done]
(1/1) Installing: kernel-default-4.12.14-lp150.12.16.1.x86_64 ............[done]
Additional rpm output:
Creating initrd: /boot/initrd-4.12.14-lp150.12.16-default
dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.12.14-lp150.12.16-default 4.12.14-lp150.12.16-default
dracut: *** Including module: bash ***
dracut: *** Including module: systemd ***
dracut: *** Including module: warpclock ***
dracut: *** Including module: systemd-initrd ***
dracut: *** Including module: i18n ***
dracut: *** Including module: drm ***
dracut: *** Including module: plymouth ***
dracut: *** Including module: kernel-modules ***
dracut: *** Including module: resume ***
dracut: *** Including module: rootfs-block ***
dracut: *** Including module: suse-xfs ***
dracut: *** Including module: terminfo ***
dracut: *** Including module: udev-rules ***
dracut: Skipping udev rule: 40-redhat.rules
dracut: Skipping udev rule: 50-firmware.rules
dracut: Skipping udev rule: 50-udev.rules
dracut: Skipping udev rule: 91-permissions.rules
dracut: Skipping udev rule: 80-drivers-modprobe.rules
dracut: *** Including module: biosdevname ***
dracut: *** Including module: dracut-systemd ***
dracut: *** Including module: haveged ***
dracut: *** Including module: usrmount ***
dracut: *** Including module: base ***
dracut: *** Including module: fs-lib ***
dracut: *** Including module: shutdown ***
dracut: *** Including module: suse ***
dracut: *** Including modules done ***
dracut: *** Installing kernel module dependencies and firmware ***
dracut: *** Installing kernel module dependencies and firmware done ***
dracut: *** Resolving executable dependencies ***
dracut: *** Resolving executable dependencies done***
dracut: *** Hardlinking files ***
dracut: *** Hardlinking files done ***
dracut: *** Stripping files ***
dracut: *** Stripping files done ***
dracut: *** Generating early-microcode cpio image ***
dracut: *** Constructing GenuineIntel.bin ****
dracut: *** Store current command line parameters ***
dracut: Stored kernel commandline:
dracut:  resume=UUID=8ed94f7f-0ac0-499d-803c-7d85217500ac
dracut:  root=UUID=7769c2b0-0d11-4a82-a2d2-b83589722347 rootfstype=ext4 rootflags=rw,noatime,data=ordered
dracut: *** Creating image file '/boot/initrd-4.12.14-lp150.12.16-default' ***
dracut: *** Creating initramfs image file '/boot/initrd-4.12.14-lp150.12.16-default' done ***


PC113:~ # grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-4.12.14-lp150.12.16-default
Found initrd image: /boot/initrd-4.12.14-lp150.12.16-default
Found linux image: /boot/vmlinuz-4.12.14-lp150.12.13-default
Found initrd image: /boot/initrd-4.12.14-lp150.12.13-default
Found linux image: /boot/vmlinuz-4.4.104-18.44-default
Found initrd image: /boot/initrd-4.4.104-18.44-default
done
PC113:~ #
3

Probably not. Actually, the forced kernel reinstall should have update “grub.cfg”, so that last step may not have been necessary. But it doesn’t hurt to play it safe.

I’ll note that “kernel-default-4.12.14-lp150.12.19.2” seems to be working fine here. I normally don’t see the “plymouth” splash screen, but I tried a boot with that splash screen and it went fine. However, I only have Intel graphics. I’m not sure if a graphics card issue is related to your problem.

4

For those running openSUSE as VM guest, user kitman has identified an issue probably due to ‘virtualbox-guest-kmp-default’ missing for the new kernel version.

https://forums.opensuse.org/showthread.php/533393-Virtualbox-VM-fails-to-boot-after-update?p=2882749#post2882749

5

Thanks.

I’ll note that the newer kernel is working fine for me on a KVM virtual machine (and also on real hardware with another computer). So it appears to be specifically a “virtualbox” issue for now.

6

It is definitely any OpenSUSE 15 VM that is using OpenSUSE repos for VirtualBox Guest Additions.

I support a lot of old Dell D620 and D820 computers that have the cpu upgraded to 64 bit processors - I got some cheap 2.0 ghz processors for a dollar each a few years ago and updated the laptops from 32 bit to 64 bit and raided a bunch of old laptops for memory to get 3gb or 4gb in each computer. The are slow as can be so I shut them down and pull the drive run them as a guest VM on a USB 3.0 IDE adapter on an Gen 7 Intel I7 laptop and boot them up and do the zypper -n up on the fast machine with 4 cpus on the virtual machine - a tough update on the D620 running native can take 3 hours but as a VM on the I7 it take 3 or 4 minutes. These machines are with people that cannot afford anything else. Fortunately parts to keep D620 and D820’s are inexpensive and plentiful. What other laptop computer can you get a new battery for $10.00 or a new keyboard for $5.00 or a wifi adapter for $3.00? only the batteries are not interchangeable between the D620 and the D820. Keyboard, Wi-fi cards, memory, cpu’s are. Not bad for machines I picked up cheap for seniors that could not afford much more than $25 for a machine.

I hope they add the virtualbox-guest-kmp-default-lp150.12.19.2 soon as the virtualbox-guest-kmp-default-lp150.12.16.1 does not work unless it is on the 16.1 kernel.

7

Yup,
Out of curiosity, I updated a LEAP 15 guest I don’t care about, and unlike others it hung straight away at “Starting Show Plymouth Boot Screen”

I don’t see that anyone has opened an openSUSE bug report… just discussed in Forum threads.
Am I right about this?
Although I’m sure Larry should have heard about this issue by now…

Although I doubt is important, I’ve saved the stdout generated that describes the modules re-built for the new default kernel.

I guess I’m less concerned about those who updated and can reboot to the previous kernel,
Am more concerned about new installs which might have installed with online repos, without actually doing such an install I don’t know if that kind of install might not have a fallback kernel.

TSU

8

I am seeing a bug report: Bug 1111076

9

Deleting the guest Packages will also boot with the new kernel, but…

10

Again, in Virtualbox…

  1. You can boot into an older kernel, remove the virtualbox kernel packages with the following command and then boot into that most recent kernel. Note that when you remove the virtualbox packages, when they remove kernel modules and try to return to a virtualbox-less kernel state, more than kernel modules are missing, including the virtualbox additions service.
zypper rm virtualbox-kernel*
  1. I tried building the Virtualbox Guest additions using the Oracle Virtualbox Additions ISO,
    And it fails miserably.

So,
It seems that there were major changes to the kernel’s interfaces and not because of any changes by Virtualbox.

TSU

11

I also posted for help on the Oracle VirtualBox site.

I wonder what changed in the kernel that breaks the VirtualBox Guest Additions.

I only go online in a virtual machine to protect from computer attacks. So I an stuck with the 16.1 kernel instead of the 19.2 kernel.

12

Without proper investigation, I think that won’t bring much. The Vbox packages all need to match the running kernel. If for some reason they don’t you have no other option than to stick with the current kernel until these packages do get built and served.

13

I succeeded with the VBoxGuestAdditions_5.2.97-125744.iso from the development builds from here https://www.virtualbox.org/wiki/Testbuilds

that worked perfectly.

for those wanting to do this.

boot up in 16.1 and zypper rm virualbox-guest*

reboot into 19.2 and zypper in kernel-default-devel

insert the downloaded iso above and put in the virtual CD drive.

run the install then reboot. (my virtual machine screen went south as it installed but the home (right ctrl) and f1 allowed me to login as root and reboot.

14

You may want to add comment to bug 1111076