Bug 25683

Summary: Why I cannot boot kernel 5.1.18 while I can boot 5.1.20 and 5.1.14
Product: Mageia Reporter: U <25u>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: lewyssmith
Version: 7Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kernel-desktop-5.1.18-1.mga7 CVE:
Status comment:

Description U 2019-11-12 08:30:19 CET
I have few problems with kernels. I installed Mageia 7 with kernel-desktop-5.1.14-1.mga7 - Linux Kernel for desktop use with x86_64​. It upgraded without problems to kernel-desktop-5.1.20-2.mga7.
Now, however I cannot boot any other kernel I tried. Most surprising kernel-desktop-5.1.18-1.mga7
My error: kernel panic screen, first line is: [ 0.992589] WARNING: CPU 3 PID:1 at arch/x86/kernel/smp.c:128 native_smp_send_reshedule+0x34/0x40 , list line is: [  1.002656] ---[end trace 896c333be5ac61b2 ]---
My hardware: Dell Inspiron 7786
My setup: dualboot Windows-Mageia. Mageia has encrypted partitions.
Possible troublemaker: some time earlier I ran mageia-prime-install, reboot and mageia-prime-uninstall 
How to diagnose the problem?
Comment 1 Lewis Smith 2019-11-12 21:51:35 CET
I am running Mageia 7 with the desktop x64 kernel, currently the last in this list, which shows several (but not all) previous kernels; I clear them out periodically:
 kernel-desktop-5.1.18-1.mga7-1-1.mga7
 kernel-desktop-5.1.20-2.mga7-1-1.mga7
 kernel-desktop-5.2.10-1.mga7-1-1.mga7
 kernel-desktop-5.2.13-2.mga7-1-1.mga7
 kernel-desktop-5.2.16-2.mga7-1-1.mga7
 kernel-desktop-5.2.7-1.mga7-1-1.mga7
 kernel-desktop-5.3.2-1.mga7-1-1.mga7
 kernel-desktop-5.3.6-2.mga7-1-1.mga7
 kernel-desktop-5.3.7-4.mga7-1-1.mga7
 kernel-desktop-latest-5.3.7-4.mga7
[I got this list with $ rpm -qa | grep kernel-desktop | sort ]

If your latest kernel-desktop-5.1.20-2.mga7 works, why does it matter that an earlier one does not?
And why are you so out-of date with the kernel? Please at least update your system. And be sure to keep 5.1.20-2 since you know that works, and you should be able to choose it from the Grub2 'advanced' boot sub-menu if the latest kernel does not work.

Please report back.
------------------
For my info: these two are in the mageia-prime package:
 /usr/sbin/mageia-prime-install
 /usr/sbin/mageia-prime-uninstall

CC: (none) => lewyssmith
Keywords: (none) => NEEDINFO

Comment 2 U 2019-11-13 22:26:29 CET
Thank you very much for the answer.
I will fill another bug report about problems with newer kernels. I thought this case was easier to diagnose.
My boot partition is small, so I have to uninstall some kernels to try new.
After some initial computer setup, that including running scripts from mageia-prime package, I cannot boot any other kernel then the ones I had at start (5.1.20 and 5.1.14).
Comment 3 Lewis Smith 2019-11-14 20:40:07 CET
It would have been better to continue this bug, which I am closing as a duplicate of the newer bug 25692, since that one is more relevant.

*** This bug has been marked as a duplicate of bug 25692 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE