Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DDR5 temperature sensor (spd5118) fails after resuming from S3 (NovaCustom NV54 laptop) #9720

Open
lfinbob opened this issue Jan 18, 2025 · 0 comments
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: power management hardware support P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.

Comments

@lfinbob
Copy link

lfinbob commented Jan 18, 2025

Qubes OS release

Qubes OS 4.2

Brief summary

Device: NV54 Laptop from NovaCustom
Firmware: coreboot: 0.9.0 07/17/2024 (the latest for this laptop)
kernel: 6.12.5-2.qubes.fc37.x86_64

Error in kernel log:

[   18.573184] spd5118 16-0050: DDR5 temperature sensor: vendor 0x0e:0x8f revision 1.2
[   18.583174] spd5118 16-0052: DDR5 temperature sensor: vendor 0x0e:0x8f revision 1.2
... (supend and resume) ...
[ 1621.796873] spd5118 16-0050: Failed to write b = 0: -6
[ 1621.796889] spd5118 16-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[ 1621.796962] spd5118 16-0050: PM: failed to resume async: error -6
[ 1621.797139] spd5118 16-0052: Failed to write b = 0: -6
[ 1621.797148] spd5118 16-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
[ 1621.797170] spd5118 16-0052: PM: failed to resume async: error -6

It happens only after resuming from S3 (so far at least).

Reading the temperature still seems to work after resume. I see values in /sys/class/hwmon/hwmon{4,5}/temp1_input that change very slightly every few seconds and seem sensible (around 48 degree Celsius).
So very low-prio/minor issue.

Detailed sensor readings:

# ll /sys/class/hwmon/hwmon4/
lrwxrwxrwx 1 root root    0 Jan 18 09:02 device -> ../../../16-0050
-r--r--r-- 1 root root 4096 Jan 17 18:32 name
drwxr-xr-x 2 root root    0 Jan 18 09:02 power
lrwxrwxrwx 1 root root    0 Jan 18 09:02 subsystem -> ../../../../../../../class/hwmon
-rw-r--r-- 1 root root 4096 Jan 18 09:02 temp1_crit
-r--r--r-- 1 root root 4096 Jan 18 09:02 temp1_crit_alarm
-rw-r--r-- 1 root root 4096 Jan 18 09:02 temp1_enable
-r--r--r-- 1 root root 4096 Jan 18 09:02 temp1_input
-rw-r--r-- 1 root root 4096 Jan 18 09:02 temp1_lcrit
-r--r--r-- 1 root root 4096 Jan 18 09:02 temp1_lcrit_alarm
-rw-r--r-- 1 root root 4096 Jan 18 09:02 temp1_max
-r--r--r-- 1 root root 4096 Jan 18 09:02 temp1_max_alarm
-rw-r--r-- 1 root root 4096 Jan 18 09:02 temp1_min
-r--r--r-- 1 root root 4096 Jan 18 09:02 temp1_min_alarm
-rw-r--r-- 1 root root 4096 Jan 18 09:02 uevent

# cat /sys/class/hwmon/hwmon4/*
cat: /sys/class/hwmon/hwmon4/device: Is a directory
spd5118
cat: /sys/class/hwmon/hwmon4/power: Is a directory
cat: /sys/class/hwmon/hwmon4/subsystem: Is a directory
85000
0
1
47500
0
0
55000
0
0
0

# cat /sys/class/hwmon/hwmon5/*
cat: /sys/class/hwmon/hwmon5/device: Is a directory
spd5118
cat: /sys/class/hwmon/hwmon5/power: Is a directory
cat: /sys/class/hwmon/hwmon5/subsystem: Is a directory
85000
0
1
48000
0
0
55000
0
0
0

Steps to reproduce

  1. Boot
  2. Suspend to S3 with systemctl suspend
  3. Resume
@lfinbob lfinbob added the P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. label Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: power management hardware support P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.
Projects
None yet
Development

No branches or pull requests

2 participants