Before kernel 5.3.18-lp152.72.1, i.e. with 69 or 66, I had kernel-syms being istalled, without kernel-preempt kernel.
I don’t want to install kernel-preempt.
This is a bug or a feature?
Report as a bug, and see what response you get.
That is an excellent advice, because we are many that would like to get an explanation for this phenomenon of the kernel-preempt suddenly appearing and taking over the system.
It first began a few months ago when virtualbox went to 6.14 and erroneously provoked the installation of that unwanted kernel.
After that, we had to remove the kernel but what could not be removed because dkms needed it was the smaller kernel-preempt-devel - and as you know, without dkms you cannot have virtualbox running.
A few months of peace followed … until today, when a number of users suddenly saw that full kernel-preempt reappearing and taking over their systems again.
Same with me today with the update. Suddenly kernel-preempt got installed, where until now only kernel-preempt-devel was there, required by dkms to make virtualbox run.
I did sometimes try to do away with that kernel-preempt-devel, but yast warned me not to do that because dkms needed it.
And now today, suddenly, the whole kernel-preempt reappeared and took over my system. Just for a few minutes, because I immediately took action.
What I did is: UNINSTALL virtualbox-kmp-preempt AND kernel-preempt AND kernel-syms AND kernel-preempt-devel ; for the latter two, an older version remains installed.
Trying to actualize kernel-syms does not work because in that case, yast wants me to reinstall the unwanted kernel-preempt …
I have no idea why this kernel-preempt resurfaced just today.
I am running Leap 15.2 and I don’t have VirtualBox installed.
Kernel: 5.3.18-lp152.69-default x86_64
Distro: openSUSE Leap 15.2
After doing
sudo zypper up
I get this:
Loading repository data...
Reading installed packages...
The following package update will NOT be installed:
gstreamer-plugins-bad-lang
The following 7 NEW packages are going to be installed:
kernel-default-5.3.18-lp152.72.1 kernel-default-devel-5.3.18-lp152.72.1 kernel-devel-5.3.18-lp152.72.1 kernel-preempt kernel-preempt-devel-5.3.18-lp152.72.1 kernel-source-5.3.18-lp152.72.1 kernel-syms-5.3.18-lp152.72.1
The following 7 packages are going to be upgraded:
kernel-macros libnuma1 numactl steam steam-devices tcsh tcsh-lang
The following 2 packages require a system reboot:
kernel-default-5.3.18-lp152.72.1 kernel-preempt
7 packages to upgrade, 7 new.
Overall download size: 299.4 MiB. Already cached: 0 B. After the operation, additional 1.6 GiB will be used.
Note: System reboot required.
Continue? [y/n/v/...? shows all options] (y): v
I chose v to view all the options:
The following package update will NOT be installed:
gstreamer-plugins-bad-lang 1.16.2-pm152.4.1
The following 7 NEW packages are going to be installed:
kernel-default 5.3.18-lp152.72.1
kernel-default-devel 5.3.18-lp152.72.1
kernel-devel 5.3.18-lp152.72.1
kernel-preempt 5.3.18-lp152.72.1
kernel-preempt-devel 5.3.18-lp152.72.1
kernel-source 5.3.18-lp152.72.1
kernel-syms 5.3.18-lp152.72.1
The following 7 packages are going to be upgraded:
kernel-macros 5.3.18-lp152.69.1 -> 5.3.18-lp152.72.1
libnuma1 2.0.11-lp152.4.6 -> 2.0.14-lp152.5.3.1
numactl 2.0.11-lp152.4.6 -> 2.0.14-lp152.5.3.1
steam 1.0.0.69-lp152.2.18.1 -> 1.0.0.70-lp152.2.21.1
steam-devices 1.0.0.69-lp152.2.18.1 -> 1.0.0.70-lp152.2.21.1
tcsh 6.20.00-lp152.7.1 -> 6.20.00-lp152.8.3.1
tcsh-lang 6.20.00-lp152.7.1 -> 6.20.00-lp152.8.3.1
The following 2 packages require a system reboot:
kernel-default 5.3.18-lp152.72.1
kernel-preempt 5.3.18-lp152.72.1
7 packages to upgrade, 7 new.
Overall download size: 299.4 MiB. Already cached: 0 B. After the operation, additional 1.6 GiB will be used.
Note: System reboot required.
Continue? [y/n/v/...? shows all options] (y): n
sudo zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | URI
---+-----------------------------+------------------------------------+---------+-----------+---------+---------------------------------------------------------------------------------------------
1 | Packman Repository | Packman Repository | Yes | (r ) Yes | Yes | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.2/
2 | SoftMaker_Office_Repository | SoftMaker Office Repository | Yes | (r ) Yes | Yes | https://shop.softmaker.com/repo/rpm
3 | openSUSE-Leap-15.2-1 | openSUSE-Leap-15.2-1 | No | ---- | ---- | hd:/?device=/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C413A8CB02119870117-0:0-part2
4 | repo-debug | Debug Repository | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.2/repo/oss/
5 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.2/repo/non-oss/
6 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.2/oss/
7 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.2/non-oss/
8 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.2/repo/non-oss/
9 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.2/repo/oss/
10 | repo-source | Source Repository | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.2/repo/oss/
11 | repo-source-non-oss | Source Repository (Non-OSS) | No | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.2/repo/non-oss/
12 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.2/oss
13 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.2/non-oss/
14 | snappy | snappy | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.2
How can I not let preempt to be installed? What should I do?
Thank you in advance.
Well, since kernel-syms is the OP’s issue, you may choose to wait for the result of the bug report - if you need it. Or delete it, if you don’t need it.
kernel-syms needs kernel-default-devel and kernel-preempt-devel (and more).
After Update to kernel version 5.3.18-lp152.72:
kernel-default-devel needs kernel-default (and more).
kernel-preempt-devel needs kernel-preempt (and more).
So deleting all kernel-syms and all kernel-preempt(-devel) packages should be enough for the moment.
This is so confusing. Is this preempt thing something that causes problem? Why does it have to be so difficult.
Does anybody know why there are there to start with? Have I installed something that ended up installing kernel-syms and/or kernel-preempt(-devel) packages?
Under the description for kernel-syms it says:
| kernel-sysms - Kernel Symbol Versions (modversions)|
|
Kernel symbols, such as functions and variables, have version information attached to them. This package contains the symbol versions for the standard kernels.
This package is needed for compiling kernel module packages with proper package dependencies.
Would deleting kernel-syms break anything?
I ended up deleting kernel-syms and kernel-preempt-devel and then did a zypper up
After the update, I rebooted the system.
Now I get this:
uname -a
Linux SimorghSUSE 5.3.18-lp152.69-default #1 SMP Tue Apr 6 11:41:13 UTC 2021 (d532e33) x86_64 x86_64 x86_64 GNU/Linux
It did not update to 72-default? Even though it said it did before I rebooted.
Any ideas?
It is me again. After further examination I see this:
ls -la /boot/vmlinuz-5.3.18-lp152.*
-rw-r--r-- 1 root root 9048240 Apr 7 11:34 /boot/vmlinuz-5.3.18-lp152.69-default
-rw-r--r-- 1 root root 9048240 Apr 15 11:03 /boot/vmlinuz-5.3.18-lp152.72-default
But:
uname -a
Linux SimorghSUSE 5.3.18-lp152.69-default #1 SMP Tue Apr 6 11:41:13 UTC 2021 (d532e33) x86_64 x86_64 x86_64 GNU/Linux
Does it mean that the 72 update didn’t update the GRUB? because the grub still loads /boot/vmlinuz-5.3.18-lp152.69-default
Has deleting the kernel-syms and kernel-preempt-devel screwd with the system?
Would appreciate help.
Thanks.
You can try running (as root)
grub2-mkconfig -o /boot/grub2/grub.cfg
I normally do not install “kernel-syms”. I do install “kernel-devel”. And kernel-preempt was not pulled in here.
However, when I saw this post yesterday, I went to Yast Software Management and selected “kernel-syms”. And yes, that wanted to pull in “kernel-preempt”. I aborted that Yast session without actually installing anything.
Thank you for your reply.
I also have kernel-devel installed:
No update candidate for 'kernel-devel-5.3.18-lp152.72.1.noarch'. The highest available version is already installed.
This is what I got after configuring grub:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-5.3.18-lp152.72-default
Found initrd image: /boot/initrd-5.3.18-lp152.72-default
Found linux image: /boot/vmlinuz-5.3.18-lp152.69-default
Found initrd image: /boot/initrd-5.3.18-lp152.69-default
Found openSUSE Tumbleweed on /dev/mapper/system-root
done
I have Tumbleweed on another drive.
I restarted the system and at the grub menu I saw that 69 is going to load. After the system was up, this is what is loaded:
uname -a
Linux SimorghSUSE 5.3.18-lp152.69-default #1 SMP Tue Apr 6 11:41:13 UTC 2021 (d532e33) x86_64 x86_64 x86_64 GNU/Linux
Any ideas?
Thanks in advance.
You can change the deafult in Yast2—System----Bootloader—Bootloader Options
Thank you for replying.
By doing so, will the next kernel update write over it and fix itself or do I have to it manually every time?
Thanks.
Bug filed: https://bugzilla.opensuse.org/show_bug.cgi?id=1185113
I decided to uninstall kernel-syms to avoid installation of any preempt stuff.
System works with kernel 5.3.18-lp152.72-default now.
Thank you for reporting the bug.
I also uninstalled kernel-syms and running kernel 5.3.18-lp152.72-default
THESE ARE THE STEPS TO CLEAN UP ALL THOSE UNWANTED “PREEMPTS”:
In Yast, you first UNINSTALL virtualbox-kmp-preempt AND kernel-preempt AND kernel-preempt-devel (with this last one, you choose the third alternative: “keep kernel-syms with broken capacities”)
THEN YOU REBOOT
Then, in Yast again, you put a TABU option (with right mouse) on these three: virtualbox-kmp-preempt AND kernel-preempt AND kernel-preempt-devel ; that way these three won’t bother you anymore, never: they’re “tabu” now.
THEN YOU REBOOT AGAIN
Then, in Yast again, you UPDATE kernel-syms (with this, you choose the third alternative option: “keep kernel-syms with broken capacities”) Don’t bother about those “broken capacities”: they refer to the unwanted preempts.
THEN YOU REBOOT AGAIN
And now your computer works fine, your kernel-default updates will not prompt you anymore to install those ********** “preempts”, and your VirtualBox (or what it was that pulled in those “preempts”) works like a charm.
The first reboot is needed so that you can put the “tabu” option on the three “preempts”;
the second reboot is needed so that the three tabus are fixed and so that you can update your kernel-syms with the right version;
the third reboot is needed to finalize all the steps you’ve taken and to clean up your computer for good.
Have a nice day!
I don’t know if I should open a new thread or continue this one.
I do not have virtualbox installed, but kernel-preempt-devel 5.3.18-lp152.87.1 wants to install when I do a zypper up.
Don’t know if I should let it or is it a bug still?
The kernel-syms is back again, and if I uninstall it, then it says it will break dkms-2.3
Any ideas?
Would appreciate guidance.
Thank you in advance.
dkms requires kernel-syms:
rpm -q --requires dkms | grep kernel
kernel-syms
kernel-syms requires:
rpm -q --requires kernel-syms | grep kernel
kernel-default-devel = 5.3.18-59.19
kernel-devel = 5.3.18-59.19
kernel-preempt-devel = 5.3.18-59.19
qed