[Bug 218188] New: hp_wmi_sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -61

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=218188

            Bug ID: 218188
           Summary: hp_wmi_sensors: probe of
                    8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error
                    -61
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@xxxxxxxxxxxxxxxxxxxx
          Reporter: alexbelm48@xxxxxxxxx
        Regression: No

Created attachment 305470
  --> https://bugzilla.kernel.org/attachment.cgi?id=305470&action=edit
ACPI dump & disassembly + BMOF and MOF files from the ck2000nf (8BAD) board

I've installed ArchLinux on my HP Omen 17 ck2000nf laptop, and I've noticed
that the hp_wmi_sensors module isn't loaded automatically by the kernel.

Modprobing manually, the hp-wmi-sensors module fails to load with a -61
(ENODATA) error:
[  350.834728] hp-wmi-sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A
failed with error -61

Peeking at the MOF files after dumping them with bmf2mof, the WMI
HPBIOS_BIOSNumericSensor object is defined as expected:

#pragma namespace("\\\\.\\root\\HP\\InstrumentedBIOS")                          
#pragma classflags("forceupdate")                                               
[WMI, Dynamic, Provider("Provider_BIOSInterface"), Description("Class Sensor
Data"), GUID("{8F1F6435-9F42-42c8-BADC-0E9424F20C9A}")]
class HPBIOS_BIOSNumericSensor : HP_BIOSNumericSensor {                         
  [key, read] string InstanceName;                                              
  [read] boolean Active;                                                        
  [WmiDataId(7), read] string PossibleStates[3];                                
};

The only thing that's odd is that there's a lowercase 'c' in the GUID string,
but *maybe* it's just an issue with the bmf2mof tool. Could it be the source of
the problem?

I run linux-next kernel 6.7.0-rc2-next-20231124-00403-g4bdf9e948c23, as I have
modified hp-wmi to add my board (8BAD) to the list of supported
omen_thermal_profile_boards, so that my CPU isn't power limited by my embedded
controller.

The issue is also observable with mainline 6.6.2-arch1-1.

I'm also dropping in my full set of raw/dumped MOF and ACPI files in the
attachment, if that can help troubleshoot the issue.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.




[Index of Archives]     [Linux Kernel Development]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux