booting 5.3.0-40 with encrypted disk fails

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

Bug Description

Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15.4
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Wed Feb 26 18:11:45 2020
InstallationDate: Installed on 2019-10-17 (131 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2020-02-24 17:34:11.828555
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
 None
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: al 1309 F.... pulseaudio
 /dev/snd/controlC0: al 1309 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-10-17 (137 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-29-generic N/A
 linux-backports-modules-5.3.0-29-generic N/A
 linux-firmware 1.183.4
Tags: eoan
Uname: Linux 5.3.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/16/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X512DA.305
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.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
a (rqcv1762) wrote :
affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
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 1864897

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
a (rqcv1762) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
a (rqcv1762) wrote : CRDA.txt

apport information

Revision history for this message
a (rqcv1762) wrote : CurrentDmesg.txt

apport information

Revision history for this message
a (rqcv1762) wrote : IwConfig.txt

apport information

Revision history for this message
a (rqcv1762) wrote : Lspci.txt

apport information

Revision history for this message
a (rqcv1762) wrote : Lsusb.txt

apport information

Revision history for this message
a (rqcv1762) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
a (rqcv1762) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
a (rqcv1762) wrote : ProcEnviron.txt

apport information

Revision history for this message
a (rqcv1762) wrote : ProcInterrupts.txt

apport information

Revision history for this message
a (rqcv1762) wrote : ProcModules.txt

apport information

Revision history for this message
a (rqcv1762) wrote : PulseList.txt

apport information

Revision history for this message
a (rqcv1762) wrote : RfKill.txt

apport information

Revision history for this message
a (rqcv1762) wrote : UdevDb.txt

apport information

Revision history for this message
a (rqcv1762) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
a (rqcv1762) wrote :

Kernel installed as described in https://wiki.ubuntu.com/Kernel/MainlineBuilds . First dpkg -i linux-image-unsigned-5.6.0-050600rc4-generic_5.6.0-050600rc4.202003012332_amd64.deb was terminated unsuccessfully with error messages; trying it again as last instead of third file yielded several messages but worked. The test kernel boots OK, i. e., the password for disk decryption is asked for and afterwards the user password.

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.