missing kernel-default-{extra,optional} after upgrade from 15.2 to 15.3
Hello, earlier today, I upgraded my workstation in the office from Leap 15.2 to 15.3 with "zypper dup". Unlike my workstation at home where the upgrade worked nicely, this machine failed to boot after the upgrade; I ended up with "give root password for maintenance" prompt and while things looked fine and most filesystems mounted, an attempt to setup networking failed due to missing D-Bus. After some experiments, I learned that the boot succeeds completely with leftover 15.2 kernel which hinted me to check if kernel-default-extra and kernel-default-optional are installed. They were not and installing them resolved the issue. After a successful boot, I checked loaded modules and found two which were not in kernel-default: jfs (JFS filesystem) sp5100_tco (TCO timer driver for SP5100/SB800 chipset) As I'm remote again, I don't want to confirm it with an experiment but my prime suspect is jfs module as the machine has one JFS filesystem mounted by default for historical reasons. Also, the sp5100_tco module has refcount of zero. But it does not really matter which module was missing, the important question is: is this outcome expected? It is IMHO rather unfortunate if a system fails to boot after an upgrade due to a missing kernel subpackage. So perhaps even more important question: can we do something about it? Michal
On Tue, 27 Jul 2021 00:36:51 +0200, Michal Kubecek wrote:
Hello,
earlier today, I upgraded my workstation in the office from Leap 15.2 to 15.3 with "zypper dup". Unlike my workstation at home where the upgrade worked nicely, this machine failed to boot after the upgrade; I ended up with "give root password for maintenance" prompt and while things looked fine and most filesystems mounted, an attempt to setup networking failed due to missing D-Bus.
After some experiments, I learned that the boot succeeds completely with leftover 15.2 kernel which hinted me to check if kernel-default-extra and kernel-default-optional are installed. They were not and installing them resolved the issue.
After a successful boot, I checked loaded modules and found two which were not in kernel-default:
jfs (JFS filesystem) sp5100_tco (TCO timer driver for SP5100/SB800 chipset)
As I'm remote again, I don't want to confirm it with an experiment but my prime suspect is jfs module as the machine has one JFS filesystem mounted by default for historical reasons. Also, the sp5100_tco module has refcount of zero.
But it does not really matter which module was missing, the important question is: is this outcome expected? It is IMHO rather unfortunate if a system fails to boot after an upgrade due to a missing kernel subpackage. So perhaps even more important question: can we do something about it?
Usually those kernel subpackages are installed via Supplements with the product Leap. Did you install without recommends? Takashi
On Tue, Jul 27, 2021 at 08:59:15AM +0200, Takashi Iwai wrote:
On Tue, 27 Jul 2021 00:36:51 +0200, Michal Kubecek wrote: [...]
After some experiments, I learned that the boot succeeds completely with leftover 15.2 kernel which hinted me to check if kernel-default-extra and kernel-default-optional are installed. They were not and installing them resolved the issue.
After a successful boot, I checked loaded modules and found two which were not in kernel-default:
jfs (JFS filesystem) sp5100_tco (TCO timer driver for SP5100/SB800 chipset)
As I'm remote again, I don't want to confirm it with an experiment but my prime suspect is jfs module as the machine has one JFS filesystem mounted by default for historical reasons. Also, the sp5100_tco module has refcount of zero.
But it does not really matter which module was missing, the important question is: is this outcome expected? It is IMHO rather unfortunate if a system fails to boot after an upgrade due to a missing kernel subpackage. So perhaps even more important question: can we do something about it?
Usually those kernel subpackages are installed via Supplements with the product Leap. Did you install without recommends?
Yes, I do; unfortunately recommends are too generous in openSUSE so that disabling them is the only way to prevent installing a lot of unwanted stuff. However, would Supplements also work for a filesystem? Also, I tried to check them for 15.3 packages and I get: mike@unicorn:~> rpm -q --supplements kernel-default-extra-5.3.18-59.16.1.x86_64 packageand(product(Leap):kernel-default_x86_64) packageand(product(SLED):kernel-default_x86_64) packageand(product(sle-we):kernel-default_x86_64) mike@unicorn:~> rpm -q --supplements kernel-default-optional-5.3.18-59.16.1.x86_64 packageand(product(Leap):kernel-default_x86_64) I thought supplements should list aliases of included modules. Am I doing something wrong or are supplements missing in these packages? Michal
On Tue, 27 Jul 2021 09:31:20 +0200, Michal Kubecek wrote:
On Tue, Jul 27, 2021 at 08:59:15AM +0200, Takashi Iwai wrote:
On Tue, 27 Jul 2021 00:36:51 +0200, Michal Kubecek wrote: [...]
After some experiments, I learned that the boot succeeds completely with leftover 15.2 kernel which hinted me to check if kernel-default-extra and kernel-default-optional are installed. They were not and installing them resolved the issue.
After a successful boot, I checked loaded modules and found two which were not in kernel-default:
jfs (JFS filesystem) sp5100_tco (TCO timer driver for SP5100/SB800 chipset)
As I'm remote again, I don't want to confirm it with an experiment but my prime suspect is jfs module as the machine has one JFS filesystem mounted by default for historical reasons. Also, the sp5100_tco module has refcount of zero.
But it does not really matter which module was missing, the important question is: is this outcome expected? It is IMHO rather unfortunate if a system fails to boot after an upgrade due to a missing kernel subpackage. So perhaps even more important question: can we do something about it?
Usually those kernel subpackages are installed via Supplements with the product Leap. Did you install without recommends?
Yes, I do; unfortunately recommends are too generous in openSUSE so that disabling them is the only way to prevent installing a lot of unwanted stuff. However, would Supplements also work for a filesystem?
Also, I tried to check them for 15.3 packages and I get:
mike@unicorn:~> rpm -q --supplements kernel-default-extra-5.3.18-59.16.1.x86_64 packageand(product(Leap):kernel-default_x86_64) packageand(product(SLED):kernel-default_x86_64) packageand(product(sle-we):kernel-default_x86_64) mike@unicorn:~> rpm -q --supplements kernel-default-optional-5.3.18-59.16.1.x86_64 packageand(product(Leap):kernel-default_x86_64)
I thought supplements should list aliases of included modules. Am I doing something wrong or are supplements missing in these packages?
It generically recommends itself when you install on Leap. The module alias or such are provided only for KMPs, AFAIK. Takashi
participants (2)
-
Michal Kubecek -
Takashi Iwai