https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c66 Julio Gonz�lez Gil <jgonzalez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jgonzalez@suse.com --- Comment #66 from Julio Gonz�lez Gil <jgonzalez@suse.com> --- (In reply to Andreas Schleth from comment #28)
(In reply to Larry Rainey from comment #12)
for those that want to remove the bad kernel - here is a script to remove and lock the kernel - run as root or add sudo to the commands.
zypper rm -y kernel-default-5.14.21-150400.24.49.3 zypper al kernel-default kernel-default-extra kernel-default-optional zypper ll cd /boot rm initrd rm vmlinuz ln -s initrd-5.14.21-150400.24.46-default initrd ln -s vmlinuz-5.14.21-150400.24.46-default vmlinuz ls -la /boot
to undo
zypper rl kernel-default kernel-default-extra kernel-default-optional zypper ll
Thanks! This script saved me a lot of grief. Both our Intel-PCs were affected.
As this affected kernel packages were retracted, there's no need to lock any packages, and no need to unlock them later. Running:
zypper rm -y kernel-default-5.14.21-150400.24.49.3 cd /boot rm initrd rm vmlinuz ln -s initrd-5.14.21-150400.24.46-default initrd ln -s vmlinuz-5.14.21-150400.24.46-default vmlinuz ls -la /boot
Is enough to make 5.14.21-150400.24.46 the default kernel again, and as soon as a new kernel update is released (including a fix for this bug), everyone will get it (otherwise probably a lot of people will not remember about unlocking the packages). -- You are receiving this mail because: You are on the CC list for the bug.