6.2.0-19 won't boot (partition UUID not found), 6.2.0-18 runs fine

Bug #2015651 reported by Ramses Rodriguez Martinez
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

6.2.0-19 won't boot (grub error says partition UUID not found), but 6.2.0-18 runs fine with the same config

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-19-generic 6.2.0-19.19
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ramses 2692 F.... wireplumber
 /dev/snd/seq: ramses 2690 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDmesg:
 Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized

 This incident has been reported.
Date: Sat Apr 8 22:20:01 2023
InstallationDate: Installed on 2017-06-21 (2116 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0
 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet nouveau.noaccel=1 splash acpi_rev_override=5 pci=noaer security=selinux selinux=0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-18-generic N/A
 linux-backports-modules-6.2.0-18-generic N/A
 linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to lunar on 2023-04-02 (5 days ago)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
---
ProblemType: Bug
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ramses 2692 F.... wireplumber
 /dev/snd/seq: ramses 2690 F.... pipewire
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 23.04
InstallationDate: Installed on 2017-06-21 (2116 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0
 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet nouveau.noaccel=1 splash acpi_rev_override=5 pci=noaer security=selinux selinux=0
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-18-generic N/A
 linux-backports-modules-6.2.0-18-generic N/A
 linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
Tags: lunar
Uname: Linux 6.2.0-18-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to lunar on 2023-04-02 (5 days ago)
UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
_MarkForUpload: False
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote :
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 2015651

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
Ramses Rodriguez Martinez (ramses-harpago) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : CRDA.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : IwConfig.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : Lspci.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : Lspci-vt.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : Lsusb-t.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : Lsusb-v.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : PaInfo.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : ProcModules.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : RfKill.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : UdevDb.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : WifiSyslog.txt

apport information

Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote : acpidump.txt

apport information

Chris Guiver (guiverc)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Ramses Rodriguez Martinez (ramses-harpago) wrote :

also happening in 6.2.0-20

Revision history for this message
Wirehead (jeffrey-5) wrote :

Same issue on Lenovo Legion 5 15ARH05.
Happening on 6.2.0-20 and 6.2.0-19.
On 6.2.0-18 - it's booting correctly.

Revision history for this message
Wirehead (jeffrey-5) wrote :

What fixed it for me - I had set apparmor=0 on my kernel boot args.
-Edit /etc/default/grub
-remove apparmor=0
-update-grub

-> Possible issue with apparmor changes introduced in 6.2.0-19

Revision history for this message
Bjorn Helgaas (bjorn-helgaas) wrote :

Original report mentions "pci=noaer". If this is needed, it most likely is working around a kernel defect, and I'd like to fix the defect.

If "pci=noaer" is needed, PLEASE report it to <email address hidden>. Then we can try to fix the underlying problem so the parameter is not needed for future kernels.

It's helpful if you can include a complete dmesg log from the most recent kernel you have (ideally an upstream kernel) and the output of "sudo lspci -vv". The <email address hidden> mailing list only accepts plain-text email and limits the message size, so it may be easiest to open a report at https://bugzilla.kernel.org and include the URL in your email.

Revision history for this message
Ivan Yosifov (iyosifov) wrote :

I'm also affected by this, and I don't use pci=noaer. My entire current (so apparmor=0 removed) /proc/cmdline is:

BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=PARTUUID=f00c0c08-7570-4270-9514-1a2dd27b7b92 ro ipv6.disable=1 nomodeset video=vesa:off vga=normal ignore_rlimit_data pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier mitigations=off

Really - it's the apparmor=0 that is causing this.

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.