Kernel: hp_wmi: query 0x4 returned error 0x5

Issues & Assistance
1

paste.cachyos.org/p/a24b222.log

I was able to correct certain errors with:

sudo systemctl stop nvidia-powerd
sudo systemctl disable nvidia-powerd

sudo systemctl mask nvidia-power

sudo pacman -S libcamera-ipa pipewire-libcamera
systemctl --user restart wireplumber.service

Result:

uname -a
Linux cachyos-N3R 6.18.9-2-cachyos #1 SMP PREEMPT_DYNAMIC Sat, 07 Feb 2026 00:59:36 +0000 x86_64 GNU/Linux

~
❯ sudo journalctl -b | grep -i wmi

févr. 15 16:06:55 cachyos kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: DF4E63B6-3BBC-4858-9737-C74F82F821F3 has zero instances
févr. 15 16:06:55 cachyos kernel: wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances
févr. 15 16:06:55 cachyos kernel: wmi_bus wmi_bus-PNP0C14:02: [Firmware Bug]: WQZZ data block query control method not found
févr. 15 16:06:59 cachyos-N3R kernel: hp_wmi: query 0x4 returned error 0x5
févr. 15 16:06:59 cachyos-N3R kernel: input: HP WMI hotkeys as /devices/virtual/input/input21
févr. 15 16:07:01 cachyos-N3R systemd-logind[869]: Watching system buttons on /dev/input/event14 (HP WMI hotkeys)

I think my system is crashing because of this error. I don’t really understand the problem.
Can someone explain it to me?

I still have a few errors, I can’t find the solution:

❯ sudo dmesg | egrep -i ‘(error|warn)’
egrep: warning: egrep is obsolescent; using grep -E
[ 0.342082] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [CAP1] at bit offset/length 64/32 exceeds size of target Buffer (64 bits) (20250807/dsopcode-198)
[ 0.342082] ACPI Error: Aborting method \_SB._OSC due to previous error (AE_AML_BUFFER_LIMIT) (20250807/psparse-531)
[ 3.385676] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20250807/exoparg2-393)
[ 3.385687] ACPI Error: Aborting method \_TZ.GETP due to previous error (AE_AML_PACKAGE_LIMIT) (20250807/psparse-531)
[ 3.385694] ACPI Error: Aborting method \_TZ.CHGZ._CRT due to previous error (AE_AML_PACKAGE_LIMIT) (20250807/psparse-531)
[ 3.387396] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20250807/exoparg2-393)
[ 3.387409] ACPI Error: Aborting method \_TZ.GETP due to previous error (AE_AML_PACKAGE_LIMIT) (20250807/psparse-531)
[ 3.387415] ACPI Error: Aborting method \_TZ.CHGZ._CRT due to previous error (AE_AML_PACKAGE_LIMIT) (20250807/psparse-531)
[ 3.700706] RAS: Correctable Errors collector initialized.
[ 5.089647] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20250807/nsarguments-61)
[ 8.644492] hp_wmi: query 0x4 returned error 0x5
[ 36.608243] warning: `kdeconnectd’ uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211

2

It has always been my understanding that this is just informative ie:

This message indicates that the WMI (Windows Management Instrumentation) subsystem on your system attempted to access a specific firmware interface identified by the GUID DF4E63B6-3BBC-4858-9737-C74F82F821F3, but found zero instances of it available. This is typically a non-critical informational log and not an error.

What it means(Please Do Correct me if I’m wrong): The system’s firmware (BIOS/UEFI) exposes certain WMI interfaces for hardware control (ie:., fan speed, battery status, hotkeys). This specific GUID corresponds to a firmware-defined interface that your laptop’s BIOS does not provide or has disabled.
Is it a problem? No, this is generally harmless.

This I’ve only seen a few time recently:

The warning kdeconnectd uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 indicates that kdeconnectd, a component of KDE Connect, is using deprecated wireless extensions (wext) instead of the modern nl80211 interface.

This is not a critical error for current Wi-Fi functionality, as most modern systems use nl80211 via wpa_supplicant and NetworkManager. However, the warning will become a problem with Wi-Fi 7 hardware, which will no longer support the older wext API.

There was a bug related to that but i thought it was fixed by now,also I have seen others block (wext) on kernel, But that’s not a suggestion I recomend today anyway. :slight_smile:

Also you seem to be on an older kernel Kernel: 6.18.9-2-cachyos to uname -r 6.19.0-2-cachyos

maybe an update may help.:folded_hands:

Dang I get so caught up in my replies I forget all in my head….LOL

But to check a bit run:

iw phy | grep -i "nl80211"                                                                                                                  
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
                * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support

Confirmed on my end and using the modern “nl80211”

3

Indeed, the following command gives me the same result:

iw phy | grep -i “nl80211”

[ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211

[ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support

[ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support

However, I have the impression that it’s my keyboard shortcuts integrated into my BIOS that are causing the following problem:

hp_wmi: query 0x4 returned error 0x5

Regarding the ACPI BIOS errors: I’m a bit lost.

My system is relatively stable, but I find that all these errors slow down my computer’s startup. I don’t know if I should look in the BIOS or the kernel.

I haven’t found a proper solution yet. The WIFI 7 issue seems to be a normal bug during development, so it’s not really a problem…

I’m going to try upgrading my system, but I doubt that will fix anything.

Thanks for your help. I hope to find a solution :slight_smile:

4

Sorry I thought I covered that as well:

ACPI BIOS Error (AE_AML_BUFFER_LIMIT): This error indicates a firmware-level issue where the BIOS provides malformed ACPI tables that the Linux kernel cannot parse correctly. The specific error AE_AML_BUFFER_LIMIT means a field in the ACPI table exceeds the size of its target buffer, which is a BIOS bug, not a kernel or OS problem.

5

Yes, I’ll have to look for a BIOS update.

After the update, it’s not really any better:

I’m using the most recent version: 01.31.00 from February 2025.

So unfortunately, it’s definitely a BIOS issue with HP. I think I’ll try to report the problem to them.
Linux isn’t the cause at all.

After test : sudo nano /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT=“quiet loglevel=3 rd.udev.log_level=3 acpi=strict”

and

GRUB_CMDLINE_LINUX_DEFAULT=’quiet loglevel=3 acpi_osi=! acpi_osi=“Windows 2022”‘

and

GRUB_CMDLINE_LINUX_DEFAULT=’quiet loglevel=3 acpi_osi=! acpi_osi=“Windows 2020”‘

And

GRUB_CMDLINE_LINUX_DEFAULT=‘nowatchdog nvme_load=YES zswap.enabled=0 splash loglevel=3 acpi_enforce_resources=lax acpi_osi=! acpi_osi=“Windows 2022”’

sudo grub-mkconfig -o /boot/grub/grub.cfg

I tried it:

It didn’t change anything :frowning:

The mistakes are still there

6

In conclusion, despite all my efforts, the problem definitely comes from the BIOS. Windows hides the errors, but Linux doesn’t.
If you have the same problem as me and want to quickly report it to support, here’s my script:

#!/bin/bash

#Script pour générer log ACPI et préparer le ticket HP ZBook
#Script to generate ACPI log and prepare the HP ZBook ticket

#Notice:

#chmod +x ~/hp_acpi_bug.sh

#bash ~/hp_acpi_bug.sh

LOG=“$HOME/acpi_log.txt”

echo “=== Génération du log ACPI - ACPI log generation ===”
sudo dmesg | grep -i acpi > “$LOG”

if [ $? -eq 0 ]; then
echo “Log ACPI généré avec succès / ACPI log generated successfully : $LOG”
else
echo “Erreur lors de la génération du log ACPI. / Error generating ACPI log.”
exit 1
fi

echo “”
echo “=== Informations système - System information ===”
MODEL=$(sudo dmidecode -s system-product-name)
VERSION=$(sudo dmidecode -s system-version)
BIOS=$(sudo dmidecode -s bios-version)
BIOS_DATE=$(sudo dmidecode -s bios-release-date)
SERIAL=$(sudo dmidecode -t 1 |grep Serial)
KERNEL=$(uname -r)
GRUB=$(grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub)

echo “Modèle / Model : $MODEL”
echo “Version : $VERSION”
echo “BIOS : $BIOS ($BIOS_DATE)”
echo “SERIAL : $SERIAL”
echo “Kernel : $KERNEL”
echo “GRUB options : $GRUB”

echo “”
echo “=== Ouvrir la page de support / Open the support page ===”
echo “Veuillez joindre le fichier / Please attach the file : $LOG lors de la création du ticket. / during ticket creation.”
xdg-open “https://support.hp.com” &>/dev/null

echo “”
echo “Script terminé. Le navigateur HP Support s’est ouvert. / Script complete. The HP Support browser has opened.”
echo “Joignez le fichier acpi_log.txt au ticket et copiez les informations système affichées.”
echo “Attach the acpi_log.txt file to the ticket and copy the displayed system information.”
7

My final solution : Thank you So Mutch @anon15508052 for your help:

GRUB_CMDLINE_LINUX_DEFAULT=‘nowatchdog nvme_load=YES zswap.enabled=0 splash loglevel=3 acpi_enforce_resources=lax acpi_osi=! acpi_osi=“Windows 2019” 8250.nr_uarts=0’

No more erreur : hp_wmi: query 0x4 returned error 0x5

And:


sudo systemctl disable plymouth-quit-wait.service
sudo systemctl mask plymouth-quit-wait.service

My ZBook G6 now takes 4 seconds less to boot up

8

Recommended**!

Concrete steps for a stable ZBook G6 on CachyOS
Limit Turbo Boost:**

echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo

I have a real CPU overheating problem. I recommend this action if you are experiencing freezes related to CPU overheating.

Or Very Best Solution:

echo 0 | tee /sys/devices/system/cpu/intel_pstate/no_turbo > /dev/null
cpupower frequency-set -u 3.6GHz
cpupower frequency-set -g powersave