scary 'Problem blacklisting hash' messages at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
linux-generic 6.2.0.20.20 on lunar, the following messages (retrieved from dmesg) are displayed on my console at boot:
[ 1.134865] blacklist: Problem blacklisting hash (-13)
[ 1.134925] blacklist: Problem blacklisting hash (-13)
[ 1.134961] blacklist: Problem blacklisting hash (-13)
[ 1.134983] blacklist: Problem blacklisting hash (-13)
Sounds like a problem!
---
ProblemType: Bug
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.04
InstallationDate: Installed on 2019-12-23 (1235 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QVCTO1WW
NonfreeKernelMo
Package: linux (not installed)
ProcFB:
0 nouveaudrmfb
1 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 20230323.
Tags: lunar
Uname: Linux 6.2.0-20-generic x86_64
UpgradeStatus: Upgraded to lunar on 2023-05-11 (0 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild src sudo
_MarkForUpload: True
dmi.bios.date: 04/28/2021
dmi.bios.release: 1.39
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET52W (1.39 )
dmi.board.
dmi.board.name: 20QVCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.ec.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QVCTO1WW
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
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 2019261
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.