BIOS Error (bug) during boot

Every time I boot my 9.3 system a number of messages flash by.
They disappear too quickly to read on screen but I managed to make a video which shows a series of errors of the form:
0.115128 ACPI BIOS Error (bug): Failure creating named object [_SB.PC00.X.RHUB.SS05._PLD,AE_ALREADY_EXISTS (20221020/DWSLOAD2-326)
[43621] ACPI Error AE_ALREADY_EXISTS, During name lookup/catalog (202210-object-220)

Then
[ 0.594255] integrity: Problem loading X.509 certificate -126

They don’t seem to any harm and the boot and subsequent processing proceed as if nothing had happened.
I’m just curious as to the cause.

Using a tool like journctl or dmesg will let you see the sequence of those errors. Which you could then copy and paste fragments into your browser as search terms to get a better understanding.

journalctl -b 0
or
dmesg | less

will get you scrollable output.

I’m also getting these errors and also has not seemed to be affecting anything…

So x.509 wise, logs show this:

Apr 11 17:25:30 localhost kernel: Loading compiled-in X.509 certificates
Apr 11 17:25:30 localhost kernel: Loaded X.509 cert 'Rocky kernel signing key: 4d2b1020fffc9503b86f8624f149a91811fde20b'
Apr 11 17:25:30 localhost kernel: Loaded X.509 cert 'Rocky Enterprise Software Foundation: Rocky Linux Driver Signing Cert 101: ce537f0c615c038114acbb01233a5b62b93a1971'
Apr 11 17:25:30 localhost kernel: Loaded X.509 cert 'Rocky Enterprise Software Foundation: Rocky Linux Driver Signing Cert 101 (aarch64): 27049f986744cc3d6a729d084fea189a8a4162ae'
Apr 11 17:25:30 localhost kernel: Loaded X.509 cert 'Rocky Enterprise Software Foundation: Rocky Linux IMA CA: 1d1cda4d16acd5196226d19e1fdb2c2761d12c4d'
Apr 11 17:25:30 localhost kernel: zswap: loaded using pool lzo/zbud
Apr 11 17:25:30 localhost kernel: page_owner is disabled
Apr 11 17:25:30 localhost kernel: Key type big_key registered
Apr 11 17:25:30 localhost kernel: Key type encrypted registered
Apr 11 17:25:30 localhost kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table)
Apr 11 17:25:30 localhost kernel: integrity: Problem loading X.509 certificate -126
Apr 11 17:25:30 localhost kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table)
Apr 11 17:25:30 localhost kernel: integrity: Loaded X.509 cert 'Rocky Enterprise Software Foundation: Rocky Linux Secure Boot Root CA: 4c2c6bd7d64ee81581cab8e986661f65e2166fc4'
Apr 11 17:25:30 localhost kernel: ima: No TPM chip found, activating TPM-bypass!
Apr 11 17:25:30 localhost kernel: Loading compiled-in module X.509 certificates
Apr 11 17:25:30 localhost kernel: Loaded X.509 cert 'Rocky kernel signing key: 4d2b1020fffc9503b86f8624f149a91811fde20b'

And the earlier messages are with this context:

Apr 11 18:24:38 localhost kernel: ACPI: Added _OSI(Module Device)
Apr 11 18:24:38 localhost kernel: ACPI: Added _OSI(Processor Device)
Apr 11 18:24:38 localhost kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Apr 11 18:24:38 localhost kernel: ACPI: Added _OSI(Processor Aggregator Device)
Apr 11 18:24:38 localhost kernel: ACPI: Added _OSI(Linux-Dell-Video)
Apr 11 18:24:38 localhost kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Apr 11 18:24:38 localhost kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
Apr 11 18:24:38 localhost kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20221020/dswload2-326)
Apr 11 18:24:38 localhost kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20221020/psobject-220)
Apr 11 18:24:38 localhost kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
Apr 11 18:24:38 localhost kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20221020/dswload2-326)
Apr 11 18:24:38 localhost kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20221020/psobject-220)
Apr 11 18:24:38 localhost kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
Apr 11 18:24:38 localhost kernel: ACPI: 14 ACPI AML tables successfully acquired and loaded

I encountered the same error “-126” on 9.3, bootup continued past the error for several months but for reasons I don’t understand a few weeks ago bootup stalled on this error and would no longer proceed. I was eventually forced to start over with a fresh install (9.4) which is now showing the same error but bootup continues past it (for now).

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.