BUG: kernel NULL pointer dereference, address: 000000000000000c

[Oliver Nissen]

This bug has been introduced with the upgrade of linux-image-5.13.0-22-generic to linux-image-5.13.0-23-generic.

One effect - the only one observed so far - is that my system does not reboot or shutdown anymore; a hard power cycle is required to recover for the next system boot.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-23-generic 5.13.0-23.23
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
Uname: Linux 5.13.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: unknown
Date: Sun Jan 9 14:15:57 2022
InstallationDate: Installed on 2021-10-08 (92 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: GIGABYTE GB-BRR7H-4800
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=3a66a17e-60e4-4005-864e-410313ceda0d ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-23-generic N/A
 linux-backports-modules-5.13.0-23-generic N/A
 linux-firmware 1.201.3
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-11-08 (62 days ago)
dmi.bios.date: 05/05/2021
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: GB-BRR7H-4800
dmi.board.vendor: GIGABYTE
dmi.board.version: 1.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/05/2021:br5.16:svnGIGABYTE:pnGB-BRR7H-4800:pvr1.x:rvnGIGABYTE:rnGB-BRR7H-4800:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
dmi.product.family: BRIX-00
dmi.product.name: GB-BRR7H-4800
dmi.product.sku: 01
dmi.product.version: 1.x
dmi.sys.vendor: GIGABYTE

[Matthew Ruffell (mruffell)]

Hi Oliver,

I believe you are seeing the same issue in:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956519

I'll take a look and put updates in that bug.

Thanks for reporting!

Matthew

[Oliver Nissen (nextcube)]

Hi Matthew,

that was quick! Yes, it appears to be sort of the same issue apart from that where Vadik's machine does not make it through the boot process mine does, but it will fail to shutdown or reboot...

Oliver

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.