Bug 219721 - spd5118 11-0050: Failed to write b = 0: -6
Summary: spd5118 11-0050: Failed to write b = 0: -6
Status: NEW
Alias: None
Product: Power Management
Classification: Unclassified
Component: Other (show other bugs)
Hardware: Intel Linux
: P3 normal
Assignee: Rafael J. Wysocki
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-25 00:17 UTC by alexknoptech
Modified: 2025-02-20 11:50 UTC (History)
2 users (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Strix - Dmesg & Info (2.93 KB, text/plain)
2025-02-20 11:50 UTC, Antonín Skala 		Details
Add an attachment (proposed patch, testcase, etc.)

Description alexknoptech 2025-01-25 00:17:53 UTC 
Noticing these errors in recent kernel versions.

alex@fedora:~$ sudo inxi -SM
System:
  Host: fedora Kernel: 6.12.9-200.fc41.x86_64 arch: x86_64 bits: 64
  Console: pty pts/3 Distro: Fedora Linux 41 (Workstation Edition)
Machine:
  Type: Laptop System: Razer product: Blade 15 (2022) - RZ09-0421 v: 8.04
    serial: BY2222M73501760
  Mobo: Razer model: CH580 v: 4 serial: N/A UEFI: Razer v: 2.06
    date: 11/01/2023



[ 6979.278270] spd5118 11-0050: Failed to write b = 0: -6
[ 6979.278280] spd5118 11-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[ 6979.278292] spd5118 11-0050: PM: failed to resume async: error -6
[ 6979.278559] spd5118 11-0052: Failed to write b = 0: -6
[ 6979.278569] spd5118 11-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[ 6979.278581] spd5118 11-0052: PM: failed to resume async: error -6
[ 8291.455654] spd5118 11-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[ 8291.455667] spd5118 11-0050: PM: failed to resume async: error -6
[ 8291.455954] spd5118 11-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[ 8291.455966] spd5118 11-0052: PM: failed to resume async: error -6
[13891.273716] spd5118 11-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[13891.273749] spd5118 11-0050: PM: failed to resume async: error -6
[13891.274165] spd5118 11-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[13891.274187] spd5118 11-0052: PM: failed to resume async: error -6
[18379.491845] spd5118 11-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[18379.491862] spd5118 11-0050: PM: failed to resume async: error -6
[18379.492109] spd5118 11-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[18379.492136] spd5118 11-0052: PM: failed to resume async: error -6
[25062.995021] spd5118 11-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[25062.995039] spd5118 11-0050: PM: failed to resume async: error -6
[25062.995313] spd5118 11-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[25062.995327] spd5118 11-0052: PM: failed to resume async: error -6
[74408.948242] spd5118 11-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[74408.948260] spd5118 11-0050: PM: failed to resume async: error -6
[74408.948740] spd5118 11-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[74408.948754] spd5118 11-0052: PM: failed to resume async: error -6
[115286.672241] spd5118 11-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[115286.672250] spd5118 11-0050: PM: failed to resume async: error -6
[115286.672624] spd5118 11-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[115286.672637] spd5118 11-0052: PM: failed to resume async: error -6
Comment 1 Roberto Salomon 2025-02-16 13:30:08 UTC 
Same messages observed with OpenSUSE Tumbleweed:
Linux treebeard 6.13.1-1-default #1 SMP PREEMPT_DYNAMIC Mon Feb  3 05:33:25 UTC 2025 (1918d13) x86_64 x86_64 x86_64 GNU/Linux


<From dmesg>
[   59.382718] [    T163] spd5118 11-0051: Failed to write b = 0: -6
[   59.382751] [    T163] spd5118 11-0051: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[   59.382769] [    T163] spd5118 11-0051: PM: failed to resume async: error -6

The system is functional after resume, but the messages indicate there may be something with the spd5118 sensor.

# inxi -SMG
System:
  Host: treebeard Kernel: 6.13.1-1-default arch: x86_64 bits: 64
  Console: pty pts/1 Distro: openSUSE Tumbleweed 20250211
Machine:
  Type: Laptop System: LENOVO product: 21D6S16900 v: ThinkPad P16 Gen 1 serial: PF4LTYR0
  Mobo: LENOVO model: 21D6S16900 v: SDK0T76530 WIN serial: L1HF35J02K2 UEFI: LENOVO
    v: N3FET43W (1.28 ) date: 07/02/2024
Graphics:
  Device-1: Intel Alder Lake-HX GT1 [UHD Graphics 770] driver: i915 v: kernel
  Device-2: NVIDIA GA107GLM [RTX A2000 8GB Laptop GPU] driver: nvidia v: 570.86.16
  Device-3: Bison Integrated RGB Camera driver: uvcvideo type: USB
  Display: unspecified server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5 driver: X:
    loaded: modesetting,nvidia dri: iris gpu: i915,nvidia,nvidia-nvswitch tty: 163x50 resolution:
    1: 1920x1080 2: 2560x1600
  API: EGL v: 1.5 drivers: nvidia platforms: gbm,surfaceless,device
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.86.16 note: console (EGL sourced) renderer: NVIDIA
    RTX A2000 8GB Laptop GPU/PCIe/SSE2
  API: Vulkan v: 1.4.304 drivers: N/A surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: nvidia-settings wl: wayland-info x11: xdpyinfo, xprop, xrandr
Comment 2 Antonín Skala 2025-02-20 11:50:29 UTC 
Created attachment 307689 [details]
Strix - Dmesg & Info

My Strix usually won't jump to Gnome after wake up from sleep. Just this dmesg output stay on internal display.
Note You need to log in before you can comment on or make changes to this bug.