Kernel 4.15.0-118 doen't get active after 4.15.0-112 updating

Bug #1896884 reported by Volodymyr Honcharov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

In Mint Cinnamon 19.1-64 kernel 4.15.0-118 doesn't get active after 4.15.0-112 updating (intermediary kernel updates were skipped). Kernel 4.15.0-112 stays active, 4.15.0-118 is only installed. Even after several restarting and removing 4.15.0-118 with second kernel update.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: waldi 1268 F.... pulseaudio
 /dev/snd/controlC0: waldi 1268 F.... pulseaudio
 /dev/snd/controlC1: waldi 1268 F.... pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19.1
HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2
InstallationDate: Installed on 2019-02-27 (574 days ago)
InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217
IwConfig:
 enp5s0 no wireless extensions.

 lo no wireless extensions.

 enp6s0 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-112-generic N/A
 linux-backports-modules-4.15.0-112-generic N/A
 linux-firmware 1.173.19
RfKill:

Tags: tessa
Uname: Linux 4.15.0-112-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX2
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1896884

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected tessa
description: updated
Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : CRDA.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : Lspci.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : Lsusb.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : ProcEnviron.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : ProcModules.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : PulseList.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : UdevDb.txt

apport information

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote :

There are two Mints on my desktop on different HDs 19.1 and 19.3 (I tried the last but I didn't like it too much - longer booting, worse and harder interface settings). I guess bootloader defines kernel version to run. Bootloader from 19.3 run 4.15.0-112 kernel in LM 19.1, recent kernel for that moment. Probably that's why I cannot activate 4.15.0-118 kernel in 19.1. Now I updated kernel in 19.3 upto 5.4.0-48, it has not helped. So, I cannot activate 4.15.0-118 in my LM 19.1 anymore, it's stay only installed.

Revision history for this message
Volodymyr Honcharov (waldi.ua) wrote :

Solved! Problem was in Grub2 I used one from newer version of LM19.3 Cinnamon. I deleted Grub-customizer in my good old LM19.1, installed Grub2 there, deleted old Vmlinuz. To see other OSs installed os-prober, modified boot-menu's view via /etc/default/grub. There is only problem now - doubled entries in boot menu, both second Linux and Wins. But it's an oldest bug of Grub2. Maximum is possible - correcting manually /boot/grub/grub.cfg, but it's working till next update-grub only. I am shocked - the Grub2's bug - doubled entries in boot menu is from very beginning!!!!! And boot menu of newest version of Grub2 in LM19.1 looks great in resolution 640x480(!), I'm really shocked. Even in 2012 it looked junk! Nevertheless, I can update my kernel now, boot in any OS. Problem is solved.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.