All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218188] New: hp_wmi_sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -61
Date: Sat, 25 Nov 2023 12:54:45 +0000	[thread overview]
Message-ID: <bug-218188-215701@https.bugzilla.kernel.org/> (raw)

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@kernel-bugs.osdl.org
          Reporter: alexbelm48@gmail.com
        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.

             reply	other threads:[~2023-11-25 12:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25 12:54 bugzilla-daemon [this message]
2023-11-25 13:40 ` [Bug 218188] hp_wmi_sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -61 bugzilla-daemon
2023-11-25 15:13 ` bugzilla-daemon
2023-11-25 15:52 ` bugzilla-daemon
2023-11-25 17:00 ` bugzilla-daemon
2023-11-25 17:33 ` bugzilla-daemon
2023-11-25 18:23 ` bugzilla-daemon
2023-11-25 18:34 ` bugzilla-daemon
2023-11-25 19:50 ` bugzilla-daemon
2023-11-25 19:51 ` bugzilla-daemon
2023-11-25 21:45 ` bugzilla-daemon
2023-11-25 22:07 ` bugzilla-daemon
2023-11-25 22:10 ` bugzilla-daemon
2023-11-26 15:38 ` bugzilla-daemon
2023-11-26 16:16 ` bugzilla-daemon
2023-11-26 19:54 ` bugzilla-daemon
2023-11-26 20:08 ` bugzilla-daemon
2023-11-26 22:49 ` bugzilla-daemon
2023-11-27 19:42 ` bugzilla-daemon
2023-11-27 19:44 ` bugzilla-daemon
2023-11-27 19:44 ` bugzilla-daemon
2023-11-27 21:48 ` bugzilla-daemon
2023-11-28  7:17 ` bugzilla-daemon
2023-11-28  7:17 ` bugzilla-daemon
2023-11-29  9:40 ` bugzilla-daemon
2023-11-29  9:40 ` bugzilla-daemon
2023-11-29 15:22 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-218188-215701@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.