Failure to boot on linux-image-5.3.0-40-generic

[Paul]

I installed Ubuntu on the laptop, rebooted and everything was fine. I did an upgrade to all packages and found that when I rebooted, it fails to load.

I found out that a workaround is to select linux-image-5.3.0-18-generic in grub which leads me to think that the issue is related to the upgrade of the linux-image 5.3.0 package.

To be clear, linux-image-5.3.0-18-generic works but linux-image-5.3.0-40-generic does not.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-40-generic 5.3.0-40.32
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: paul 2027 F.... pulseaudio
 /dev/snd/controlC0: paul 2027 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 10 18:25:57 2020
InstallationDate: Installed on 2020-03-09 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-18-generic N/A
 linux-backports-modules-5.3.0-18-generic N/A
 linux-firmware 1.183.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X512DA.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X512DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[You-Sheng Yang (vicamo)]

Hi, by "failed to boot", could you give some more details about what happened? Could you try to edit kernel boot parameters at grub, remove "quiet splash", and add:

  ignore_loglevel debug initcall_debug log_buf_len=32M earlycon=efifb

And attach the screenshot and/or dmesg of that 5.3.0-40-generic kernel boot?

[Paul (happypaul55)]

Hi, I've uploaded a video to Youtube, see youtu.be/3jdXe3i3Ox0 , of what it does and also what I do to make it work. I hope this is what you're after. I've attached dmesg but I had to restart as you saw in the video so not sure if it's as useful. Happy to run any other tests or what.

[Paul (happypaul55)]

The link in my previous comment is the second half, the first half is here youtu.be/zuj4Sb9sxlI

[You-Sheng Yang (vicamo)]

Hi, both dmesg logs you attached are of 5.3.0-18-generic, not 5.3.0-40-generic. Could you try to locate your last boot of 5.3.0-40-generic by:

  $ journalctl -k -b <num>

where <num> is -1 for last boot, -2 for the second last boot and so on. Save full output with:

  $ journalctl -k -b <num> | tee dmesg.5.3.0-40-generic

And, could you also try to boot 5.3.0-40-generic without "quiet splash" but with "3", which will send you into console mode if successful. No need to append other debug parameters. It seems kernel has successfully booted and we may need to diagnose GUI environment rather than linux kernel. So let's try booting into no GUI mode. If that works, you should try:

  1. booting with 5.3.0-40-generic normally (with "quiet splash" removed) again,
  2. wait for a few minutes after screen turns blank,
  3. force power off
  4. use `journalctl -b -1` to dump *all* syslog messages and attach them here.

[Paul (happypaul55)]

Hi, I ran the steps as requested. After a few minutes of the blank screen I noticed the fan turns on so I guess something is happening. I don't see anything on the screen after it goes blank. I've attached the logs as requested

[Paul (happypaul55)]

Another log file

[Paul (happypaul55)]

Add a photo of what the screen shows, not much help but I want to be as complete as possible

[Paul (happypaul55)]

I upgraded/updated to `5.3.0-42-generic` and now it boots without me having to change anything in grub.

I've attached `journalctl -b` in case this is of help.

All the best
Paul