[SOLVED] Can somebody identify and help solve this error occuring right after switching on?

[raffael84]

Hello!

This is shown after switching the laptop on and I find it rather annoying.

I would like to understand the cause of the error message and solve it. Can someone help?

Thanks

Code: Select all

$ inxi -Fxxrzc0

System:
  Kernel: 5.15.0-94-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
    Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin dm: LightDM
    Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: LENOVO product: 20XGS1L002 v: ThinkPad T14s Gen 2a
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 20XGS1L002 v: SDK0T76538 WIN
    serial: <superuser required> UEFI: LENOVO v: R1NET54W (1.24)
    date: 10/27/2022
Battery:
  ID-1: BAT0 charge: 56.4 Wh (100.0%) condition: 56.4/57.0 Wh (99.0%)
    volts: 17.4 min: 15.4 model: Celxpert 5B10W51815 serial: <filter>
    status: Full
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse B330/M330/M331
    serial: <filter> charge: 55% (should be ignored) status: Discharging
CPU:
  Info: 6-core model: AMD Ryzen 5 PRO 5650U with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 16 MiB
  Speed (MHz): avg: 1553 high: 3370 min/max: 1600/2300 boost: enabled
    cores: 1: 1348 2: 1397 3: 1393 4: 1394 5: 1394 6: 1396 7: 1395 8: 1396
    9: 1369 10: 1398 11: 1397 12: 3370 bogomips: 55100
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Cezanne vendor: Lenovo driver: amdgpu v: kernel pcie:
    speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1
    bus-ID: 06:00.0 chip-ID: 1002:1638
  Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-2:2 chip-ID: 13d3:5405
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: eDP res: 1920x1080 dpi: 158 diag: 354mm (13.9")
  OpenGL: renderer: RENOIR (renoir LLVM 15.0.7 DRM 3.42 5.15.0-94-generic)
    v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 06:00.1 chip-ID: 1002:1637
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
    vendor: Lenovo driver: snd_rn_pci_acp3x v: kernel pcie: speed: 8 GT/s
    lanes: 16 bus-ID: 06:00.5 chip-ID: 1022:15e2
  Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 06:00.6 chip-ID: 1022:15e3
  Sound Server-1: ALSA v: k5.15.0-94-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8168
  IF: enp2s0f0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie:
    speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723
  IF: wlp3s0 state: up mac: <filter>
  IF-ID-1: wwan0 state: down mac: N/A
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 5-4:3 chip-ID: 8087:0029
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter>
    bt-v: 3.0 lmp-v: 5.2 sub-v: 237e
Drives:
  Local Storage: total: 238.47 GiB used: 92.59 GiB (38.8%)
  ID-1: /dev/nvme0n1 vendor: Micron model: MTFDKBA256TFK size: 238.47 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 31.9 C
Partition:
  ID-1: / size: 230.57 GiB used: 63.46 GiB (27.5%) fs: ext4 dev: /dev/dm-1
    mapped: vgmint-root
  ID-2: /boot size: 1.61 GiB used: 833.4 MiB (50.7%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 976 MiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/dm-2 mapped: vgmint-swap_1
Sensors:
  System Temperatures: cpu: 49.0 C mobo: N/A gpu: amdgpu temp: 47.0 C
  Fan Speeds (RPM): fan-1: 0
Repos:
  Packages: 2734 apt: 2728 flatpak: 6
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/kdenlive-kdenlive-stable-jammy.list
    1: deb [signed-by=/etc/apt/keyrings/kdenlive-kdenlive-stable-jammy.gpg] https://ppa.launchpadcontent.net/kdenlive/kdenlive-stable/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://ftp-stud.hs-esslingen.de/pub/Mirrors/packages.linuxmint.com virginia main upstream import backport
    2: deb http://ftp-stud.hs-esslingen.de/ubuntu jammy main restricted universe multiverse
    3: deb http://ftp-stud.hs-esslingen.de/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://ftp-stud.hs-esslingen.de/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
    1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
  Active apt repos in: /etc/apt/sources.list.d/swi-prolog-stable-jammy.list
    1: deb [signed-by=/etc/apt/keyrings/swi-prolog-stable-jammy.gpg] https://ppa.launchpadcontent.net/swi-prolog/stable/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:
  Processes: 379 Uptime: 4h 9m Memory: 14.45 GiB used: 2.83 GiB (19.6%)
  Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12
  Shell: Zsh v: 5.8.1 running-in: tmux: inxi: 3.3.13

[xenopeek]

It is a bug in the BIOS. Possibly a BIOS update will solve it in the future. You can't solve it from the OS side, you can only suppress it. See this earlier topic about the exact same problem: viewtopic.php?t=412877

I've opted to just ignore it.

[raffael84]

How dangerous is it to update BIOS on a Thinkpad with Linux running on it? Of course it is possible but is there some nontrivial risk involved?

[Schultz]

ACPI "errors" are harmless. I've had them for 8 years and ignore it. If it bugs you, you can suppress the messages. Go to xenopeek's link, second post.

[bendipa]

At first sight it looks like a firmware issue. But sometimes error messages are misleading. I would disconnect your disk(s), RAM, any GPU and then try booting to BIOS. If that error still persists, I'd contact Lenovo's helpdesk/customer service about it. You should not be seeing that.

[Schultz]

At first sight it looks like a firmware issue. But sometimes error messages are misleading. I would disconnect your disk(s), RAM, any GPU and then try booting to BIOS. If that error still persists, I'd contact Lenovo's helpdesk/customer service about it. You should not be seeing that.

Wrong. There are many posts about this subject. Most of the time, the "errors" are harmless. If your computer works fine after boot, it's nothing to worry about. No need to tear up your system.

Boot warnings: how can I suppress unimportant messages?
19. Sometimes you get to see warnings when you boot your system. These are usually quite unimportant; Linux is notoriously talkative about even totally innocent "errors".

Thankfully you can filter out the irrelevant warnings, leaving only the more important ones. Namely by decreasing the log level, which is set one notch too high in Linux Mint and Ubuntu. Proceed like this: . . . .
https://easylinuxtipsproject.blogspot.c ... .html#ID19

[AndyMH]

How dangerous is it to update BIOS on a Thinkpad with Linux running on it? Of course it is possible but is there some nontrivial risk involved?

If it works don't fix it. A BIOS update going wrong is about the only way to brick a computer with software. For some thinkpads lenovo release an iso to upgrade BIOS, for others the only route is windows.

The kernel is very good at reporting errors due to BIOS implementations that are non-compliant with specifications. If it works, ignore it.

[bendipa]

At first sight it looks like a firmware issue. But sometimes error messages are misleading. I would disconnect your disk(s), RAM, any GPU and then try booting to BIOS. If that error still persists, I'd contact Lenovo's helpdesk/customer service about it. You should not be seeing that.

Wrong. There are many posts about this subject. Most of the time, the "errors" are harmless. If your computer works fine after boot, it's nothing to worry about. No need to tear up your system.

I don't care how many previous discussions there have been.You are wrong. You should not be getting an error/warning like that on booting to BIOS. Obviously it indicates there is some sort of power issue issue or future hardware issue that can arise, especially if this has not occurred on previous boots. Common sense would tell you that alone.

[Schultz]

especially if this has not occurred on previous boots.

Well you should find this out from the OP before you tell somebody to rip up their computer. And this is a common issue:

viewtopic.php?p=2422438
viewtopic.php?p=2429616
viewtopic.php?p=2425912
viewtopic.php?p=2424830
viewtopic.php?p=2078780 (This link has my screenshot of these "errors")

I repeat, if the everything runs fine after boot, they really aren't "errors" at all. Like I said, I've had these from day 1 eight years ago, and my computer hasn't blown up yet.

@raffael84 Is this a new Mint install? Have you always gotten these messages? Does everything run fine after boot up? Take AndyMH's advice above if you answer any of these questions in the affirmative.

[PaulL]

At first sight it looks like a firmware issue. But sometimes error messages are misleading. I would disconnect your disk(s), RAM, any GPU and then try booting to BIOS. If that error still persists, I'd contact Lenovo's helpdesk/customer service about it. You should not be seeing that.

Even on Windows, there is a difference between a warning and an error, and that is especially true on Linux Mint. As a former programmer, I appreciate the wealth of information that Linux Mint logs, but it remains true that informational warnings can be disregarded if the machine boots properly and works well.

A further consideration is what, precisely, the warning actually means. I don't see ACPI warnings on boot up--though they appear in the log--but the one warning I do see on startup is that "SGX has been disabled by BIOS." I get that message every time I boot, and it doesn't matter whether SGX is actually disabled in the BIOS or not. So either (a) the bootloader cannot actually detect the state of SGX in the BIOS, or (b) there is a bug that attaches the wrong warning message to whatever condition the bootloader is actually trying to warn me about. Nevertheless, the system boots and runs fine, so it's not worth worrying about.

[Reddog1]

As pointed out by numerous posters, it's a failure of the firmware programmers to implement acpi the way that linux expects it, and the error message plainly states that linux considers this to be a (bug).

Some distributions won't print this error because it's superfluous, and their default is 'loglevel=3'. Unfortunately, ubuntu isn't one of them, which causes numerous useless posts from newbies concerned about it.

[raffael84]

@raffael84 Is this a new Mint install? Have you always gotten these messages? Does everything run fine after boot up? Take AndyMH's advice above if you answer any of these questions in the affirmative.

This is a rather new Mint install from November or December 2023 on a brand new Thinkpad T14s.

I'm pretty sure the messages have been shown since right after installation and except for unstable bluetooth I do not experience any issues whatsoever.

Also I have not been worried really at any point given that as far as I can remember I never had Mint running on a Thinkpad without similar error messages. I considered it always more of a cosmetic issue.

Having said that if you would like to dig a little deeper I'd love to provide you with additional information.

[Schultz]

Having said that if you would like to dig a little deeper I'd love to provide you with additional information.

There's nothing to dig out. Reddog1 already gave the correct answer:

As pointed out by numerous posters, it's a failure of the firmware programmers to implement acpi the way that linux expects it, and the error message plainly states that linux considers this to be a (bug).

Some distributions won't print this error because it's superfluous, and their default is 'loglevel=3'. Unfortunately, ubuntu isn't one of them, which causes numerous useless posts from newbies concerned about it.

If you don't want to see these unreal errors on bootup follow the instructions in this link: https://easylinuxtipsproject.blogspot.c ... .html#ID19

[raffael84]

alrighty ... I'd rather not fool around with my system if I can avoid it