Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo

[PlantDaddy]

After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error message stating
"Error: out of memory
Press any key to continue..."

After pressing a key, nothing changed. I left the room and came back to see that there was a kernel panic. I'll attach picture as I couldn't copy/paste the console output.

Description: Ubuntu 19.10
Release: 19.10

linux-image-5.3.0-19-generic

I expect the kernel to load without a panic.
The kernel panicked.

After rebooting and selecting an older kernel, I was able to boot and load the old kernel without issue (5.0.0-32-generic)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-19-generic 5.3.0-19.20
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lost 1947 F.... pulseaudio
CurrentDesktop: XFCE
Date: Mon Oct 28 00:52:26 2019
HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626
InstallationDate: Installed on 2016-06-17 (1227 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5510
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-32-generic N/A
 linux-backports-modules-5.0.0-32-generic N/A
 linux-firmware 1.183.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.0
dmi.board.name: 0WVDX2
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5510
dmi.product.sku: 06E5
dmi.sys.vendor: Dell Inc.

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

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc5/

[PlantDaddy (plantdaddy)]

Still panics. Looks like the same panic

[PlantDaddy (plantdaddy)]

Using: linux-image-unsigned-5.4.0-050400rc5-generic

[Kai-Heng Feng (kaihengfeng)]

Can you please run fsck on your root partition?

[PlantDaddy (plantdaddy)]

Ran fsck from a bootable linux, no issues (this is a LUKS encrypted volume):

root@kali:~# fsck /dev/mapper/xubuntu--vg-root
fsck from util-linux 2.34
e2fsck 1.45.4 (23-Sep-2019)
/dev/mapper/xubuntu--vg-root: clean, 1139039/30162944 files, 77548819/120621056 blocks
root@kali:~# echo $?
0

[Kai-Heng Feng (kaihengfeng)]

Would it be possible for you to do a kernel bisection?

First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it doesn’t work,
$ git bisect old
Otherwise,
$ git bisect new
Repeat to "make -j`nproc` deb-pkg" until you find the commit fixes the issue.

[PlantDaddy (plantdaddy)]

Yeah I would, but with the 5.3.0-26 update, it's now working again. Do you still want me to try?

[Kai-Heng Feng (kaihengfeng)]

If it's fixed then there's no need to test further.