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] hp_wmi_sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -61
Date: Sat, 25 Nov 2023 17:00:26 +0000	[thread overview]
Message-ID: <bug-218188-215701-Vp6AFcwuH8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218188-215701@https.bugzilla.kernel.org/>

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

--- Comment #3 from Alexis Belmonte (alexbelm48@gmail.com) ---
I still have the same error printed out when manually inserting hp_wmi_sensors
-- I also noticed that wmi_bus complains about WQ00 not being there:

# dmesg|grep wmi
[    2.074660] wmi_bus wmi_bus-PNP0C14:00: WQ00 data block query control method
not found
[   30.175458] hp-wmi-sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A
failed with error -61

I can confirm that the situation did not change, I made sure that I didn't do
something wrong by executing the following command to clean, build & install
the kernel:

$ make -j64 clean && make -j64 all modules bzImage && sudo make -j64
modules_install && sudo cp -v arch/x86_64/boot/bzImage /boot/vmlinuz-linux-next
&& sudo mkinitcpio -p linux-next && sudo grub-mkconfig -o /boot/grub/grub.cfg

For your information, I integrated next-20231124 in my working source tree; let
me know if you want me to test this on the mainline codebase instead.

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

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

  parent reply	other threads:[~2023-11-25 17:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25 12:54 [Bug 218188] New: hp_wmi_sensors: probe of 8F1F6435-9F42-42C8-BADC-0E9424F20C9A failed with error -61 bugzilla-daemon
2023-11-25 13:40 ` [Bug 218188] " bugzilla-daemon
2023-11-25 15:13 ` bugzilla-daemon
2023-11-25 15:52 ` bugzilla-daemon
2023-11-25 17:00 ` bugzilla-daemon [this message]
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-Vp6AFcwuH8@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.