You are not logged in.
Pages: 1
I'm getting the following ACPI errors during boot on my laptop. This was not present before updating to kernel 6.19.11.
[ 17.948940] clevo_acpi: failed to evaluate _DSM
[ 17.949605] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [S907] at bit offset/length 112/16 exceeds size of target Buffer (120 bits) (20250807/dsopcode-198)
[ 17.949610] ACPI Error: Aborting method \_SB.DCHU.PEVT due to previous error (AE_AML_BUFFER_LIMIT) (20250807/psparse-529)
[ 17.949621] ACPI Error: Aborting method \_SB.DCHU._DSM due to previous error (AE_AML_BUFFER_LIMIT) (20250807/psparse-529)
[ 17.949626] ACPI: \_SB_.DCHU: failed to evaluate _DSM e424f293-dcfb-bf4b-add6-db71bdc0afad rev:0 func:4 (0x300a)
[ 17.949628] clevo_acpi: failed to evaluate _DSMThe BIOS never produced this bug with previous 6.19 kernels. How do I clear this error?
Thanks.
Offline
Fans working?
Keyboard backlight? (if there)
performance modes or power profiles working??
suspend/hibernation?
battery reporting?
brightness?
Edit:
in short if your laptop is behaving normally, then these are just noise ![]()
Last edited by 5hridhyan (2026-04-08 04:46:06)
---
Offline
Actually, it looks like cpu boost states, which should go up to 5.1 GHz, is currently reduced to 3.29 GHz. This is according to cpupower frequency-info.
sudo cpupower frequency-info
analyzing CPU 4:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 4
CPUs which need to have their frequency coordinated by software: 4
energy performance preference: performance
hardware limits: 605 MHz - 3.29 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 605 MHz and 3.29 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.99 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
amd-pstate limits:
Highest Performance: 125. Maximum Frequency: 3.29 GHz.
Nominal Performance: 76. Nominal Frequency: 2.00 GHz.
Lowest Non-linear Performance: 23. Lowest Non-linear Frequency: 605 MHz.
Lowest Performance: 23. Lowest Frequency: 599 MHz.
Preferred Core Support: 0. Preferred Core Ranking: 125.I'd like the boost setting to be back.
Last edited by haigioli (2026-04-08 11:20:11)
Offline
I've always had 'initcall_blacklist=acpi_cpufreq_init' in my grub.cfg. Is this causing a problem, now? I usually pair it with 'amd_pstate=passive' so that I have more granular control over cpu power scaling for some realtime applications.
But, upon further investigation, cpu power scaling seems to be working fine. With passive turned on, I get the full range of boost states.
What seem the be the problem is that I don't hear any fans.
'sensors-detect' lists the following:
Sorry, no sensors were detected.
This is relatively common on laptops, where thermal management is
handled by ACPI rather than the OS.Temps appear to be reporting with 'sensors':
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +31.0°C
spd5118-i2c-21-50
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +36.0°C (low = +0.0°C, high = +55.0°C)
(crit low = +0.0°C, crit = +85.0°C)
amdgpu-pci-c300
Adapter: PCI adapter
vddgfx: 0.00 V
vddnb: 0.00 V
edge: +37.0°C
PPT: 4.08 W (avg = 4.08 W)
sclk: 630 MHz
BAT0-acpi-0
Adapter: ACPI interface
in0: 17.44 V
curr1: 0.00 A
spd5118-i2c-21-51
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +37.2°C (low = +0.0°C, high = +55.0°C)
(crit low = +0.0°C, crit = +85.0°C)
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +40.6°C
nvme-pci-c100
Adapter: PCI adapter
Composite: +33.9°C (low = -273.1°C, high = +84.8°C)
(crit = +84.8°C)
Sensor 1: +32.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +33.9°C (low = -273.1°C, high = +65261.8°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +40.0°C The only thing is that I haven't heard fans turn on at all. How do I test this?
Last edited by haigioli (2026-04-08 11:48:25)
Offline
so you say you don't hear fans at all, so you sus fans are not working, but looking at your temps, it shows 40, in many laptops, there is hardcoded rules that the fans spin up, only when they hit 65+, for example HP Notebook models, they spin at fast when they hit 70, which laptop is yours? how was the behavior before this kernel version?
are you using TLP/power-profile daemons? or auto-cpufreq?
Edit:
Re-wrote post according to OPs latest status quo
Edit2:
you can test by stress test, https://wiki.archlinux.org/title/Stress_testing to see upon high temps, if the fan spins up/you can hear them spinning
Last edited by 5hridhyan (2026-04-08 12:10:01)
---
Offline
Thank you for your patience and help, @5hridyan.
I use 'tuned' with 'tuned-ppd' quite successfully for a long time. Sometimes, when I 'need to be sure' because of the RT apps I write and run, I disable all that and set my cpu scaling with 'cpupower' with amd pstate driver set to 'passive' explicitly. Most of the time, though, active with tuned is what I use for day-to-day on this laptop.
I'll hit my CPU harder and see if I can get through the threshold, but two things:
1) I noticed no fans listed in '/sys/class/hwmon*'
2) pwmconfig reports no pwn controllers
Now, I don't know if that's normal for clevo-based laptops because I never really checked before this (fans kicked in and all seemed well, so I never checked).
'sensors' reports no fan info (as you can see).
Offline
No problem ![]()
once see this
┌──(shridhyan@ATRNXA)-[~]
└─$ sensors
hp-isa-0000
Adapter: ISA adapter
pwm1: N/A
amdgpu-pci-0400
Adapter: PCI adapter
vddgfx: N/A
vddnb: N/A
edge: +49.0°C
sclk: 200 MHz
BAT0-acpi-0
Adapter: ACPI interface
in0: 12.88 V
curr1: 0.00 A
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +49.4°C
nvme-pci-0100
Adapter: PCI adapter
Composite: +29.9°C (low = -0.1°C, high = +84.8°C)
(crit = +94.8°C)
ERROR: Can't get value of subfeature temp2_min: I/O error
ERROR: Can't get value of subfeature temp2_max: I/O error
Sensor 1: +47.9°C (low = +0.0°C, high = +0.0°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +49.0°C
temp2: +0.0°C
┌──(shridhyan@ATRNXA)-[~]
└─$ ls /sys/class/hwmon*
hwmon0 hwmon1 hwmon2 hwmon3 hwmon4 hwmon5 hwmon6
┌──(shridhyan@ATRNXA)-[~]
└─$ pwmconfig
You need to be root to run this script.
┌──(shridhyan@ATRNXA)-[~]
└─$ sudo pwmconfig
[sudo] password for shridhyan:
# pwmconfig version 3.6.2
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
/usr/bin/pwmconfig: There are no pwm-capable sensor modules installedas you can see, mine also reports 'N/A' for PWM and pwmconfig finds nothing, this is because, like your clevo, my HP handles fan logic through the embedded controller/ECrather than the OS, most laptops are designed this way, the BIOS/EC is the "brain" for the fans, and the Linux kernel is just a passenger...
also the fact that sensors doesn't show fan RPMs on your machine is almost certainly how it has always been, you're just noticing it now because those ACPI errors made you go looking for problems!
How did the stress test go? if it hit 65-70°C, did the 'ghost' fans finally make some noise??
---
Offline
Good news is that all seems good. Fans kick in elegantly. So, going back to your original list of ACPI things to look for gotchas: They all seem to be working fine.
Should I simply ignore these errors? Should I monitor something just in case?
Offline
For context see mine.
Apr 08 09:35:37 ATRNXA kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.BCM5], AE_NOT_FOUND (20250807/dswload2-162)
Apr 08 09:35:37 ATRNXA kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20250807/psobject-220)
Apr 08 09:35:42 ATRNXA kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x000000032) is beyond end of object (length 0x32) (20250807/exopa>
Apr 08 09:35:42 ATRNXA kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous error (AE_AML_BUFFER_LIMIT) (20250807/psparse-529)Should I simply ignore these errors? Should I monitor something just in case?
if I were you I'd ignore those and chill, you can monitor, or test, if those errors is related with the "checklist" in #2 ![]()
---
Offline
Did clevo_acpi load before?
Offline
Pages: 1