How To Rectify ACPI Errors

Support and Help
21

Only 51 errors…

sudo grep -Ei ‘error’ /var/log/*g




/var/log/auth.log:2026-01-11T00:19:37.457543-05:00 wyatt-82xb sudo:    wyatt : TTY=pts/0 ; PWD=/home/wyatt ; USER=root ; COMMAND=/usr/bin/grep -Ei error /var/log/apport.log /var/log/auth.log /var/log/boot.log /var/log/dmesg /var/log/dpkg.log /var/log/gpu-manager.log /var/log/kern.log /var/log/lastlog /var/log/syslog /var/log/Xorg.0.log
/var/log/dmesg:[    0.008019] kernel: [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors
/var/log/dmesg:[    0.206597] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS01._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206609] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206615] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS01._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206618] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206624] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS02._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206627] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206658] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206662] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206665] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206668] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206703] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206706] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206709] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206712] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206746] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206749] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206753] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206755] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206790] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206792] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206796] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206799] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206833] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206836] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206868] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206871] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206874] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206877] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206912] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206915] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206945] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206948] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206952] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS08._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206954] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206989] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS01._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206992] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.206995] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS01._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.206998] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.207033] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS02._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.207036] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.207039] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS02._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.207042] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.207076] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS03._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.207079] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    0.207110] kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.XHCI.RHUB.SS04._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
/var/log/dmesg:[    0.207113] kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
/var/log/dmesg:[    1.052755] kernel: RAS: Correctable Errors collector initialized.
/var/log/dmesg:[    3.258794] kernel: lenovo_wmi_hotkey_utilities CE6C0974-0407-4F50-88BA-4FC3B6559AD8: probe with driver lenovo_wmi_hotkey_utilities failed with error -5
/var/log/Xorg.0.log:	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
```
22

Benign messages > " the standard complaint of the kernel about the bios poor acpi implementation. Most motherboards are like that."
As one reference - https://www.reddit.com/r/linuxquestions/comments/11gcnvd/acpi_bios_error_bug_failure_creating_named_object/

-looks good to me-

23

I did an internet search of the first message…

Here’s what showed up in the AI Overview before the search results.

What would you suggest my next move might be?

Note: AI Overview responses may include mistakes.

https://support.google.com/websearch?p=ai_overviews&hl=en

###================================================================###

kernel: [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors

###----------------------------------------------------------------###

This message indicates that the Linux kernel detected inconsistent
Time Stamp Counter (TSC) values between different CPU cores or
sockets during boot.

###----------------------------------------------------------------###

Meaning of the Message

TSC Inconsistency:
The hardware (firmware) failed to synchronize the high-resolution
timers (TSC) across all CPU cores.

Kernel Correction:
The phrase “fixing all errors” means the Linux kernel has
successfully performed a synchronization routine to align these
timers itself.

Firmware Bug:
This is typically caused by a BIOS/UEFI implementation that does not
meet the expected ACPI standards for clock synchronization.

###----------------------------------------------------------------###

Recommended Actions
If your system is running normally without crashes or clock drift, this message can generally be ignored as the kernel has already mitigated the issue. However, if you experience instability or want to clear the error, follow these steps:

  1. Update BIOS/UEFI:
    This is the primary fix, as manufacturers often release updates to resolve ACPI and TSC synchronization issues.

  2. Update CPU Microcode:
    Ensure you have the latest microcode updates installed, which can fix known CPU errata related to timers.

    1. Ubuntu/Debian:

      For Intel…

      $ sudo apt install -y intel-microcode

      For AMD

      $ sudo apt install -y amd64-microcode

    2. Arch/Fedora:
      Ensure the intel-ucode or amd-ucode package is installed and
      loaded in your bootloader.

    3. Kernel Parameters (Workaround):
      If the message persists and causes issues like “unstable clock
      detected,” you can force a different clocksource by adding
      tsc=unstable to your GRUB boot parameters.

    4. Virtual Machines:
      If this occurs in a VM, it is often due to the hypervisor
      failing to maintain coherent TSC values during live migration
      or CPU hot-plugging.

      Ensure your hypervisor (e.g., KVM, VMware) is updated

###================================================================###
24

Well, as your system is functional in all respects - I would do nothing. However, it is a good idea to have the latest BIOS update installed.
Microcode: these updates are in routine package updates.
see for instance:

dpkg -l amd64-microcode
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name            Version                     Architecture Description
+++-===============-===========================-============-=======================>
ii  amd64-microcode 3.20250311.1ubuntu0.24.04.1 amd64        Processor microcode fir>
sysop@Xm2404

Timers: the kernel adjust - no action needed on your part.

-if it ain’t broke, do not fix it-

25

Note to self:

“aint no since in posting doubles.”

26

I know all of them may or may not be…but

How may I not display the “false positive’s” in errors and warnings?

27

That one I do not know - I have never given such a thought in all my years.

-a know-it-all I am not-

28

I can understand that one.
Are there any which look like it may be an actual issue?

29

I did look through your log posting fairly close; I did not see anything I found concerning. However, that is not to say that I may have missed something of import in all the clutter.

-just say’n-

30

I’m going through TJ’s guidance.

He mentions navigating to the line starting “linux” and a “kernal command line” in grub.

Which line in grub was he meaning?

Is the following what he’s talking about…


```

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
```
```

Or is it something in grub mentioned here…


```

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR='Ubuntu'
GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'
GRUB_CMDLINE_LINUX=""

```
```
31

Did you do a memory test (best done over night) to actually identify broken bits of your memory to map them in that commandline option in grub so they get excluded from accessing ? For the BADRAM option you will need to know the exact broken bits of your RAM to list them.

Your logs do not seem to indicate any broken memory modules though, only incompatible BIOS/UEFI bits that only a BIOS update would have the potential to solve …

1 Like
32

All this is now put in the plans.
In what order should these be perormed?

TJ says to navigate to the line in grub starting with “linux …”.
Which line in grub is he taliking about?

How should a memory test be done for these types of detections and/or corrections?

How would I do a BIOS update here in (L)ubuntu?

How should a BIOS/UEFI update be done?

33

Well, do you have any actual indication that there is anything broken with your memory modules like random crashes of apps, a complete hang of the system or unexpected reboots that you have no explanation for ? Else I’d not put effort into digging into this …

There is a memtest option in the grub menu that you should be able to get to when hitting ESC during boot … as I said, you should let it run at least over night or even longer …

If your mainboard is supported by fwupd you could use the usually pre-installed fwupdmgr from lubuntu itself, but that requires that your hardware manufacturer actually submitted your BIOS to the LVFS database at https://fwupd.org/

If this is not the case you will need to follow the instructions of your hardware manufacturer and likey do the update from within the UEFI/BIOS, there should be an option in there …

That said, all this indeed assumes that your manufacturer even offers a newer BIOS/UEFI version…

TBH, I’d just ignore the errors in the logs since they do not seem to have any functional impact beyond some log noise …

34

I will check on the BIOS/UEFU updates.

That leads me back to two main questions…

  1. TJ says to navigate to the line in grub starting with “linux …”.
    Which line in grub was he taliking about?

  2. How to suppress “log noise” apart from the “real” warnings and errors?

35

Regarding 1. … no idea who TJ is but he/she/it seems to be not referring to Ubuntu … usually additional options go behind “quiet splash” in the GRUB_CMDLINE_LINUX_DEFAULT= option, though GRUB_BADRAM= seems to actually be its own option, I’d read the Ubuntu grub documentation (manpages etc) to see if you need to add it as its own variable to /etc/default/grub …

For 2. you could turn down the kernel logging parameters, read up about how to configure sysctl and particularly about the kernel.printk option, though I would not recommend this since it will also suppress potentially important log messages you would actually want to see …
Typically ACPI errors only show up right after boot and not later on when the system is running so they are usually rather harmless and will not fill your log too much …

1 Like
36

Thanks a bunch, sir

Posted by bashing-om for my consideration.
Note the “< TJ->”
I refer to he or she as “TJ”

Which-ever Linux “TJ” is refering to…
It seem’s as though Lubuntu on my Lenovo Ideapad might need that(those) setting(s).

Wow…Thanks so much.

37

Why exactly do you think you need this ? Have you proven yet that you have any damaged memory sticks in your machine?

(TBH, even if you have, I’d personally rather invest a bit of money and get a new memory stick to replace the broken one on my Mainboard instead of excluding single blocks of memory from being used by the kernel since there is likely a physical reason that caused the damage and it might increase over time so the crashes and unexpected reboots this would cause would return eventually anyway)

EDIT: and quoting the excellent advice @bashing-om gave above… -if it ain’t broke, do not fix it- … there seems to be nothing wrong with your system, it is just a bit noisy on boot due to the badly implemented BIOS it has, I wouldn’t do anything here…

3 Likes
38

It’s “new” hardware…nothing wrong with it.

To quote bashing-om …

“If it ain’t broke, do not fix it”

Thanks

39

If it’s hardware that’s broke, don’t fix it, just replace it when you can.

I didn’t realize I was delving into a hardware issue…which I have none.