Bug 201881 - hp_wmi: query 0xd returned error 0x5
Summary: hp_wmi: query 0xd returned error 0x5
Status: NEW
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-04 12:15 UTC by Cristian Aravena Romero
Modified: 2019-01-06 09:08 UTC (History)
2 users (show)

See Also:
Kernel Version: Ubuntu 4.18.0-11.12-generic 4.18.12
Tree: Mainline
Regression: No


Attachments

Description Cristian Aravena Romero 2018-12-04 12:15:04 UTC
Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1806681

dmesg:
hp_wmi: query 0xd returned error 0x5

Best regards,
--
Cristian Aravena Romero (caravena)
Comment 1 Colin Ian King 2018-12-04 12:28:47 UTC
This does not appear to be an error to worry about. The WMI driver for your machine is performing a feature query with the ACPI driver with HPWMI_FEATURE2_QUERY. This seems to be a feature that is enabled on HP WMI firmware from around 2009 onwards. Some machines may support this, however it seems that your firmware does not seem to have support for this, hence the query failure.

The kernel throws a warning message to indicate that this feature is not supported. I doubt this is something you need to worry about.
Comment 2 Cristian Aravena Romero 2018-12-04 12:40:17 UTC
A more friendly message?
Comment 3 Colin Ian King 2018-12-04 12:43:30 UTC
If we fill the kernel up with friendly messages it will be massive. It's already got >100,000 kernel messages.
Comment 4 Colin Ian King 2018-12-04 12:45:32 UTC
Most warnings like this are really for the per driver kernel developers.
Comment 5 NotTheEvilOne 2019-01-06 09:08:23 UTC
Hi,

This issue seems not to be only a warning / developer specific log message. An "HP Elite x2 1013 G3" has no working "hp-wmi" sysfs entries at all. E.g. trying to output "/sys/devices/platform/hp-wmi/als" results in the reported log message. As error code 0x05 indicates "invalid parameters" my guess would be that another variant of the "hp_wmi_bios_2009_later()" would be required or that the WMI methods have been removed. I would appreciate to provide more details if guided how to further debug / receive details needed.

Note You need to log in before you can comment on or make changes to this bug.