ACPI Thermal Limit Triggers Thermal Shutdown on Sleep

Support
,
1

I have an issue where the my motherboard bios is reporting the following:

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
temp2:        +16.8°C  (crit = +20.8°C)
temp3:        +16.8°C  (crit = +20.8°C)

When I put the computer into sleep mode these sensors get picked up as being at 20.8C causing the Linux kernel to trigger an emergency shutdown, thus failing to enter sleep.

I reached out to Gigabyte on this but their support rep just stated that “we do not support Linux systems”.

Is there anyway to disable or ignore this sensor from the OS side?

System Specs:
OS: Manjaro Linux x86_64
Motherboard: X570 AORUS ELITE -CF
Kernel: 6.5.13-6-MANJARO
Shell: bash 5.2.21
DE: Plasma 5.27.10
CPU: AMD Ryzen 7 5800X (16) @ 3.800GHz
GPU: AMD ATI Radeon RX 6800/6800 XT / 6900 XT

2

Hi @BeepBoopImAComputa and welcome to the Manjaro community

Your mainboard manual may be helpful.

I imagine disabling the sensor might be unwise. As kernel 6.5 has reached EOL I’d recommend upgrading to the latest available (6.6.8), which may (or may not) improve things. Beyond that, I have nothing more to add. Cheers.

1 Like
3

Hi @soundofthunder thank you for your response.

That’s a good point, there might be a setting in the BIOS that I can tinker with.

I will give Kernel 6.6.8 a try to see if that helps.

And I agree disabling the sensor would not be ideal.

4

can you report

inxi -Mxxa
5 
Machine:
  Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: X570 AORUS ELITE serial: <superuser required>
    UEFI: American Megatrends LLC. v: F38g date: 09/20/2023
6

Also here is the log from an attempted suspend

Nov 17 16:12:00 My-PC systemd[1]: Starting System Suspend...
Nov 17 16:12:00 My-PC systemd-sleep[158526]: Entering sleep state 'suspend'...
Nov 17 16:12:00 My-PC kernel: PM: suspend entry (deep)
Nov 17 16:12:00 My-PC kernel: Filesystems sync: 0.002 seconds
Nov 17 16:12:07 My-PC kernel: Freezing user space processes
Nov 17 16:12:07 My-PC kernel: Freezing user space processes completed (elapsed 0.024 seconds)
Nov 17 16:12:07 My-PC kernel: OOM killer disabled.
Nov 17 16:12:07 My-PC kernel: Freezing remaining freezable tasks
Nov 17 16:12:07 My-PC kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Nov 17 16:12:07 My-PC kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 17 16:12:07 My-PC kernel: sd 5:0:0:0: [sda] Synchronizing SCSI cache
Nov 17 16:12:07 My-PC kernel: sd 11:0:0:0: [sdc] Synchronizing SCSI cache
Nov 17 16:12:07 My-PC kernel: ata6.00: Entering standby power mode
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: MODE1 reset
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: GPU mode1 reset
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: GPU smu mode1 reset
Nov 17 16:12:07 My-PC kernel: ACPI: PM: Preparing to enter system sleep state S3
Nov 17 16:12:07 My-PC kernel: ACPI: PM: Saving platform NVS memory
Nov 17 16:12:07 My-PC kernel: Disabling non-boot CPUs ...
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 1 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 2 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 3 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 4 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 5 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 6 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 7 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 8 is now offline
Nov 17 16:12:07 My-PC kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 9 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 10 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 11 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 12 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 13 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 14 is now offline
Nov 17 16:12:07 My-PC kernel: smpboot: CPU 15 is now offline
Nov 17 16:12:07 My-PC kernel: ACPI: PM: Low-level resume complete
Nov 17 16:12:07 My-PC kernel: ACPI: PM: Restoring platform NVS memory
Nov 17 16:12:07 My-PC kernel: LVT offset 0 assigned for vector 0x400
Nov 17 16:12:07 My-PC kernel: Enabling non-boot CPUs ...
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C002: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU1 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C004: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU2 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C006: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU3 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C008: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU4 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C00A: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU5 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 6 APIC 0xc
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C00C: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU6 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 7 APIC 0xe
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C00E: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU7 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 8 APIC 0x1
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C001: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Nov 17 16:12:07 My-PC kernel: CPU8 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 9 APIC 0x3
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C003: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU9 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 10 APIC 0x5
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C005: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU10 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 11 APIC 0x7
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C007: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU11 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 12 APIC 0x9
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C009: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU12 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 13 APIC 0xb
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C00B: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU13 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 14 APIC 0xd
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C00D: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU14 is up
Nov 17 16:12:07 My-PC kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Nov 17 16:12:07 My-PC kernel: ACPI: \_PR_.C00F: Found 2 idle states
Nov 17 16:12:07 My-PC kernel: CPU15 is up
Nov 17 16:12:07 My-PC kernel: ACPI: PM: Waking up from system sleep state S3
Nov 17 16:12:07 My-PC kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
Nov 17 16:12:07 My-PC kernel: [drm] PSP is resuming...
Nov 17 16:12:07 My-PC kernel: nvme nvme0: 32/0/0 default/read/poll queues
Nov 17 16:12:07 My-PC kernel: nvme nvme1: 15/0/0 default/read/poll queues
Nov 17 16:12:07 My-PC kernel: [drm] reserve 0xa00000 from 0x83fd000000 for PSP TMR
Nov 17 16:12:07 My-PC kernel: usb 3-6.1: reset full-speed USB device number 3 using xhci_hcd
Nov 17 16:12:07 My-PC kernel: usb 7-4: reset full-speed USB device number 3 using xhci_hcd
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resuming...
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5800 (58.88.0)
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: SMU driver if version not matched
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: use vbios provided pptable
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resumed successfully!
Nov 17 16:12:07 My-PC kernel: [drm] DMUB hardware initialized: version=0x02020020
Nov 17 16:12:07 My-PC kernel: ata3: SATA link down (SStatus 0 SControl 300)
Nov 17 16:12:07 My-PC kernel: ata9: SATA link down (SStatus 0 SControl 300)
Nov 17 16:12:07 My-PC kernel: ata5: SATA link down (SStatus 0 SControl 300)
Nov 17 16:12:07 My-PC kernel: ata4: SATA link down (SStatus 0 SControl 300)
Nov 17 16:12:07 My-PC kernel: ata10: SATA link down (SStatus 0 SControl 300)
Nov 17 16:12:07 My-PC kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 17 16:12:07 My-PC kernel: ata6.00: Entering active power mode
Nov 17 16:12:07 My-PC kernel: ata6.00: supports DRM functions and may not be fully accessible
Nov 17 16:12:07 My-PC kernel: ata6.00: supports DRM functions and may not be fully accessible
Nov 17 16:12:07 My-PC kernel: ata6.00: configured for UDMA/133
Nov 17 16:12:07 My-PC kernel: [drm] kiq ring mec 2 pipe 1 q 0
Nov 17 16:12:07 My-PC kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Nov 17 16:12:07 My-PC kernel: [drm] JPEG decode initialized successfully.
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 8
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8
Nov 17 16:12:07 My-PC kernel: amdgpu 0000:0c:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 8
Nov 17 16:12:07 My-PC kernel: xhci_hcd 0000:0c:00.2: xHC error in resume, USBSTS 0x401, Reinit
Nov 17 16:12:07 My-PC kernel: usb usb5: root hub lost power or was reset
Nov 17 16:12:07 My-PC kernel: usb usb6: root hub lost power or was reset
Nov 17 16:12:07 My-PC kernel: OOM killer enabled.
Nov 17 16:12:07 My-PC kernel: Restarting tasks ... 
Nov 17 16:12:07 My-PC kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Nov 17 16:12:07 My-PC kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Nov 17 16:12:07 My-PC kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Nov 17 16:12:07 My-PC kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
Nov 17 16:12:07 My-PC kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Nov 17 16:12:07 My-PC kernel: done.
Nov 17 16:12:07 My-PC kernel: random: crng reseeded on system resumption
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/ldac
Nov 17 16:12:07 My-PC systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 17 16:12:07 My-PC wpa_supplicant[1123]: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSink/aptx_hd
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_hd
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSink/aptx
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSink/aac
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aac
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc_xq
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc_xq
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/faststream
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/faststream_duplex
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSink/opus_05
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/opus_05
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.83" (uid=1000 pid=1983 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.0" (uid=0 pid=9>
Nov 17 16:12:07 My-PC wpa_supplicant[1123]: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 17 16:12:07 My-PC wpa_supplicant[1123]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Nov 17 16:12:07 My-PC dbus-daemon[947]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.4" (uid=0 pid=971 comm="/usr/bin/NetworkManager --no-daemon") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.82" (uid=1>
Nov 17 16:12:07 My-PC bluetoothd[946]: Destroy Adv Monitor Manager
Nov 17 16:12:07 My-PC bluetoothd[946]: Battery Provider Manager destroyed
Nov 17 16:12:07 My-PC systemd[1]: Stopped target Bluetooth Support.
Nov 17 16:12:07 My-PC systemd[1699]: Stopped target Bluetooth.
Nov 17 16:12:07 My-PC systemd[1]: Reached target Bluetooth Support.
Nov 17 16:12:07 My-PC systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 17 16:12:07 My-PC systemd[1699]: Reached target Bluetooth.
Nov 17 16:12:07 My-PC plasmashell[1875]: qt.qpa.clipboard: QXcbClipboard::setMimeData: Cannot set X11 selection owner
Nov 17 16:12:07 My-PC plasmashell[1875]: qt.qpa.clipboard: QXcbClipboard::setMimeData: Cannot set X11 selection owner
Nov 17 16:12:07 My-PC plasmashell[1875]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Nov 17 16:12:07 My-PC plasmashell[1875]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Nov 17 16:12:07 My-PC plasmashell[1875]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Nov 17 16:12:07 My-PC kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
Nov 17 16:12:07 My-PC bluetoothd[946]: Battery Provider Manager created
Nov 17 16:12:07 My-PC kernel: Bluetooth: MGMT ver 1.22
Nov 17 16:12:07 My-PC bluetoothd[946]: profiles/audio/bap.c:bap_adapter_probe() BAP requires ISO Socket which is not enabled
Nov 17 16:12:07 My-PC bluetoothd[946]: bap: Operation not supported (95)
Nov 17 16:12:07 My-PC bluetoothd[946]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Nov 17 16:12:07 My-PC bluetoothd[946]: Adv Monitor Manager created with supported features:0x00000000, enabled features:0x00000000, max number of supported monitors:32, max number of supported patterns:16
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/ldac
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/aptx_hd
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_hd
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/aptx
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/aac
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aac
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc_xq
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc_xq
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/faststream
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/faststream_duplex
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/opus_05
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/opus_05
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Nov 17 16:12:07 My-PC bluetoothd[946]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Nov 17 16:12:07 My-PC NetworkManager[971]: <info>  [1700259127.9201] manager: (18:CE:94:38:33:E7): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/8)
Nov 17 16:12:07 My-PC NetworkManager[971]: <info>  [1700259127.9318] audit: op="statistics" interface="18:CE:94:38:33:E7" args="500" pid=1966 uid=1000 result="success"
Nov 17 16:12:07 My-PC NetworkManager[971]: <info>  [1700259127.9368] audit: op="statistics" interface="18:CE:94:38:33:E7" args="500" pid=1966 uid=1000 result="success"
Nov 17 16:12:08 My-PC systemd-sleep[158526]: System returned from sleep state.
Nov 17 16:12:08 My-PC bluetoothd[946]: Controller resume with wake event 0x0
Nov 17 16:12:08 My-PC systemd[1]: systemd-suspend.service: Deactivated successfully.
Nov 17 16:12:08 My-PC kernel: thermal thermal_zone1: acpitz: critical temperature reached, shutting down
Nov 17 16:12:08 My-PC kernel: reboot: HARDWARE PROTECTION shutdown (Temperature too high)
Nov 17 16:12:08 My-PC kernel: PM: suspend exit
Nov 17 16:12:08 My-PC systemd[1]: Finished System Suspend.
Nov 17 16:12:08 My-PC systemd[1]: Stopped target Sleep.
Nov 17 16:12:08 My-PC systemd[1]: Reached target Suspend.
Nov 17 16:12:08 My-PC systemd[1]: Stopped target Suspend.
Nov 17 16:12:08 My-PC systemd-logind[950]: Operation 'sleep' finished.
Nov 17 16:12:08 My-PC ModemManager[1077]: <msg> [sleep-monitor-systemd] system is resuming
Nov 17 16:12:08 My-PC NetworkManager[971]: <info>  [1700259128.6336] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Nov 17 16:12:08 My-PC NetworkManager[971]: <info>  [1700259128.6337] device (enp5s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 17 16:12:08 My-PC NetworkManager[971]: <info>  [1700259128.6618] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 17 16:12:08 My-PC NetworkManager[971]: <info>  [1700259128.6864] device (wlp6s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 17 16:12:08 My-PC NetworkManager[971]: <info>  [1700259128.6868] device (p2p-dev-wlp6s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 17 16:12:08 My-PC NetworkManager[971]: <info>  [1700259128.6869] device (18:CE:94:38:33:E7): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 17 16:12:08 My-PC NetworkManager[971]: <info>  [1700259128.6871] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 17 16:12:08 My-PC NetworkManager[971]: <info>  [1700259128.6872] device (18:CE:94:38:33:E7): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 17 16:12:08 My-PC kernel: reboot: Hardware protection timed-out. Trying forced poweroff
7

can you report

sudo mhwd-kernel -li
pacman -Qs linux66-headers
cpupower frequency-info
pacman -Qi 
sensors
pacman -Qs lm_sensors

from mine

sensors
it8792-isa-0a60
Adapter: ISA adapter
in0:           1.78 V  (min =  +0.00 V, max =  +2.78 V)
in1:         676.00 mV (min =  +0.00 V, max =  +2.78 V)
in2:         992.00 mV (min =  +0.00 V, max =  +2.78 V)
+3.3V:         3.38 V  (min =  +0.00 V, max =  +5.56 V)
in4:           1.78 V  (min =  +0.00 V, max =  +2.78 V)
in5:           1.19 V  (min =  +0.00 V, max =  +2.78 V)
in6:           2.78 V  (min =  +0.00 V, max =  +2.78 V)  ALARM
3VSB:          3.36 V  (min =  +0.00 V, max =  +5.56 V)
Vbat:          3.10 V  
fan1:           0 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:         761 RPM  (min =    0 RPM)
temp1:        +42.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:        -55.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:        +39.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
intrusion0:  ALARM

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  
temp2:        +16.8°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +42.4°C  
Tccd1:        +44.2°C
8

I just updated to Kernel 6.6.8 and still see the same behavior
Here is the outputs of the commands you posted:

sudo mhwd-kernel -li
Currently running: 6.6.8-2-MANJARO (linux66)
The following kernels are installed in your system:
   * linux510
   * linux515
   * linux61
   * linux65
   * linux66

pacman -Qs linux66-headers
local/linux66-headers 6.6.8-2
    Header files and scripts for building modules for Linux66 kernel

cpupower frequency-info
analyzing CPU 14:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 14
  CPUs which need to have their frequency coordinated by software: 14
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 2.20 GHz - 4.85 GHz
  available frequency steps:  3.80 GHz, 2.80 GHz, 2.20 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 2.20 GHz and 3.80 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 2.64 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: no

sensors
amdgpu-pci-0c00
Adapter: PCI adapter
vddgfx:      768.00 mV 
fan1:           0 RPM  (min =    0 RPM, max = 3300 RPM)
edge:         +41.0°C  (crit = +100.0°C, hyst = -273.1°C)
                       (emerg = +105.0°C)
junction:     +46.0°C  (crit = +110.0°C, hyst = -273.1°C)
                       (emerg = +115.0°C)
mem:          +42.0°C  (crit = +100.0°C, hyst = -273.1°C)
                       (emerg = +105.0°C)
PPT:          33.00 W  (cap = 203.00 W)

gigabyte_wmi-virtual-0
Adapter: Virtual device
temp1:        +38.0°C  
temp2:        +45.0°C  
temp3:        +51.0°C  
temp4:        +43.0°C  
temp5:        +46.0°C  
temp6:        +56.0°C  

nvme-pci-0100
Adapter: PCI adapter
Composite:    +51.9°C  (low  =  -5.2°C, high = +83.8°C)
                       (crit = +87.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  
temp2:        +16.8°C  
temp3:        +16.8°C  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +39.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +51.2°C  
Tccd1:        +42.5°C  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +44.9°C  (low  =  -0.1°C, high = +74.8°C)
                       (crit = +79.8°C)
ERROR: Can't get value of subfeature temp3_min: I/O error
ERROR: Can't get value of subfeature temp3_max: I/O error
Sensor 2:     +44.9°C  (low  =  +0.0°C, high =  +0.0°C)
ERROR: Can't get value of subfeature temp4_min: I/O error
ERROR: Can't get value of subfeature temp4_max: I/O error
Sensor 3:     +59.9°C  (low  =  +0.0°C, high =  +0.0°C)
ERROR: Can't get value of subfeature temp5_min: I/O error
ERROR: Can't get value of subfeature temp5_max: I/O error
Sensor 4:     +44.9°C  (low  =  +0.0°C, high =  +0.0°C)
ERROR: Can't get value of subfeature temp6_min: I/O error
ERROR: Can't get value of subfeature temp6_max: I/O error
Sensor 5:     +44.9°C  (low  =  +0.0°C, high =  +0.0°C)
ERROR: Can't get value of subfeature temp7_min: I/O error
ERROR: Can't get value of subfeature temp7_max: I/O error
Sensor 6:     +44.9°C  (low  =  +0.0°C, high =  +0.0°C)

pacman -Qs lm_sensors
local/lib32-lm_sensors 1:3.6.0.r41.g31d1f125-2
    Collection of user space tools for general SMBus access and hardware monitoring (32-bit)
local/lm_sensors 1:3.6.0.r41.g31d1f125-2
    Collection of user space tools for general SMBus access and hardware monitoring

pacman -Qi - ouput is too long

9

This might also be useful

acpi -V or sensors
No support for device type: power_supply
No support for device type: power_supply
Thermal 0: ok, 16.8 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 20.8 degrees C
Thermal 0: trip point 1 switches to mode hot at temperature 19.8 degrees C
Thermal 1: ok, 16.8 degrees C
Thermal 1: trip point 0 switches to mode critical at temperature 20.8 degrees C
Thermal 1: trip point 1 switches to mode hot at temperature 19.8 degrees C
Thermal 2: ok, 16.8 degrees C
Thermal 2: trip point 0 switches to mode critical at temperature 20.8 degrees C
Thermal 2: trip point 1 switches to mode hot at temperature 19.8 degrees C
Cooling 0: Processor 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Processor 0 of 10
Cooling 4: Processor 0 of 10
Cooling 5: Processor 0 of 10
Cooling 6: Processor 0 of 10
Cooling 7: Processor 0 of 10
Cooling 8: Processor 0 of 10
Cooling 9: iwlwifi_1 no state information available
Cooling 10: Processor 0 of 10
Cooling 11: Processor 0 of 10
Cooling 12: Processor 0 of 10
Cooling 13: Processor 0 of 10
Cooling 14: Processor 0 of 10
Cooling 15: Processor 0 of 10
Cooling 16: Processor 0 of 10
10

may be recheck all parameter in UEFI motherboard
in advanced cpu , recheck options ( should be auto mode in most cases )
except cppc on

you can use theses option on boot kernel
“iommu=pt amd-pstate=guided”

you have to remove EOL kernel

sudo mhwd-kernel -r linux65

i suggest redo sensors-detect

sudo sensors-detect
1 Like
11

However, mainboards tend to have a manual override of some kind for setting the warning temperature limits. Sometimes these settings might be obfuscated (hidden behind basic/advanced mode, or similar). I note that ~20 degrees seems (to me) a little low, generally; ~50 degrees seems more realistic, or even higher, depending on the machine – don’t quote me, as it’s also possible that some boards are designed with a lower threshold in mind. :person_shrugging:

12

Hey I went through and turned CPPC on

Don’t think iommu=pt is needed as thats for PCI pass-through for VMs right?

This arg might improve perf amd-pstate=guided, but I don’t think is relevant to the current issue.

I have remove the EOL kernel and rerun sensors-detect

13

Yeah I did find a manual override for the CPU throttle temperature, but nothing pertaining to the ACPI critical temperature. 20C is far too low and just about an average room temperature.

The sensor “acpitz-acpi-0” reported temperatures will always remain 16.8C even when watching those sensors. The only point at which they report 20.8C is when going into suspend.

Which makes me wonder if the value being reported is even a temperature at all, maybe its just a misreading of some other value…who knows :stuck_out_tongue:

14

Can you please describe how you came to this conclusion? It would be helpful to provide the command and output letting you assume this.

I would read this as your system is shutdown in waking up phase rather than going into sleep.

Also, please provide full output of

inxi -Fza

Yes, but as @soundofthunder mentioned - if you not yet found the procedure yourself I doubt you are experienced enough that someone should show it to you. :stuck_out_tongue_winking_eye:

15

Hey Wollie thanks for your reply!

I came to the conclusion via this route:

  • Seeing this log entry:
  • thermal thermal_zone1: acpitz: critical temperature reached, shutting down
  • then this (acpitz being the sensor with a critical temperature of 20.8C)
  • reboot: HARDWARE PROTECTION shutdown (Temperature too high)

Yeah, that’s correct.
When watching the system it does the following:

  • Begins to enter suspend
  • wakes up a few seconds after the suspension
  • immediately powers off the PC.

I’m not sure I understand what Hardware protection timed-out. means, what is it waiting for?

System:
  Kernel: 6.6.8-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=689975af-fbb9-4da6-81e2-e04cc96db4e4 rw quiet apparmor=1
    security=apparmor resume=UUID=24f81326-2130-4c7d-9592-cdc3d4f5d38e
    udev.log_priority=3 amdgpu.ppfeaturemask=0xffffffff
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF serial: N/A
  Mobo: Gigabyte model: X570 AORUS ELITE serial: N/A UEFI: American
    Megatrends LLC. v: F38g date: 09/20/2023
CPU:
  Info: model: AMD Ryzen 7 5800X socket: AM4 bits: 64 type: MT MCP
    arch: Zen 3+ gen: 4 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA20102B
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 2837 high: 3800 min/max: 2200/4776 boost: enabled
    base/boost: 3800/4850 scaling: driver: acpi-cpufreq governor: schedutil
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 2200 2: 2200 3: 2200 4: 2200
    5: 2200 6: 3800 7: 3800 8: 2200 9: 3800 10: 2200 11: 3800 12: 2200
    13: 3800 14: 2800 15: 3800 16: 2200 bogomips: 121661
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] driver: amdgpu
    v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22
    pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1,DP-2,HDMI-A-1
    empty: DP-3 bus-ID: 0c:00.0 chip-ID: 1002:73bf class-ID: 0300
  Display: x11 server: X.Org v: 21.1.10 with: Xwayland v: 23.2.3
    compositor: kwin_x11 driver: X: loaded: amdgpu dri: radeonsi gpu: amdgpu
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5440x2645 s-dpi: 96 s-size: 1439x699mm (56.65x27.52")
    s-diag: 1600mm (62.98")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,bottom-c
    model: Dell S2721DGF serial: <filter> built: 2021 res: 2560x1440 dpi: 109
    gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: max: 2560x1440 min: 720x400
  Monitor-2: DP-2 mapped: DisplayPort-1 pos: top-right model: Dell S2721DS
    serial: <filter> built: 2020 res: 1440x2560 dpi: 109 gamma: 1.2
    size: 336x597mm (13.23x23.5") diag: 676mm (26.6") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: middle-l model: Dell S2721D
    serial: <filter> built: 2022 res: 1440x2560 dpi: 109 gamma: 1.2
    size: 336x597mm (13.23x23.5") diag: 676mm (26.6") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.1.9-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6800 (navi21 LLVM
    16.0.6 DRM 3.54 6.6.8-2-MANJARO) device-ID: 1002:73bf memory: 15.62 GiB
    unified: no
  API: Vulkan v: 1.3.274 layers: 3 device: 0 type: discrete-gpu name: AMD
    Radeon RX 6800 (RADV NAVI21) driver: mesa radv v: 23.1.9-manjaro1.1
    device-ID: 1002:73bf surfaces: xcb,xlib
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Plantronics BT600 driver: plantronics,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-1.3.4:7
    chip-ID: 047f:02ee class-ID: 0300 serial: <filter>
  API: ALSA v: k6.6.8-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp5s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp6s0 state: up mac: <filter>
  IF-ID-1: br-fde7c943275a state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-4:3 chip-ID: 2550:8761
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.83 TiB used: 1.36 TiB (74.2%)
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Western Digital
    model: WDS100T1X0E-00AFY0 size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 611100WD temp: 52.9 C scheme: GPT
  SMART: yes health: PASSED on: 1y 85d 22h cycles: 1,452
    read-units: 43,972,593 [22.5 TB] written-units: 83,428,103 [42.7 TB]
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: A-Data model: SX8200PNP
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 42A4SANA temp: 45.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 1y 112d 20h cycles: 1,989
    read-units: 25,425,157 [13.0 TB] written-units: 28,984,420 [14.8 TB]
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 500GB
    family: based SSDs size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 2B6Q temp: 33 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 241d 5h cycles: 5213
    written: 34.02 TiB
  ID-4: /dev/sdb maj-min: 8:16 model: General size: 119 MiB block-size:
    physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s lanes: 1
    mode: 2.0 tech: N/A serial: <filter> fw-rev: 5.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 922.42 GiB size: 906.86 GiB (98.31%)
    used: 687.87 GiB (75.9%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:4
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 288 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:3
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:5
Sensors:
  System Temperatures: cpu: 69.5 C mobo: 39.0 C gpu: amdgpu temp: 49.0 C
    mem: 48.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Processes: 448 Uptime: 4h 42m wakeups: 0 Memory: total: 32 GiB
  available: 31.26 GiB used: 9.17 GiB (29.3%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: 2094 pm: pacman pkgs: 2075 libs: 449 tools: pamac,yay pm: flatpak
  pkgs: 5 pm: snap pkgs: 14 Shell: Bash (su) v: 5.2.21 running-in: konsole
  inxi: 3.3.31

I would agree with that, bit of a nuclear option :laughing:

16

Right, it seems like the forums had a bit of a lie down and forgot some stuff (including my entire account, as I’d only just registered…). So I’m going to post something that’s probably similar to what I posted before, but obviously I can’t recall this one-for-one.

Basically, I have the same issue as @BeepBoopImAComputa. My Gigabyte X570 I motherboard also has some sensors that always read as 16.8°C with a cutoff at 20.8°C, and sometimes when resuming from suspend these sensors get tripped. As the room the computer is in is typically at 21°C, a quick check on the rules of thermodynamics suggest that the 16.8°C being reported is unlikely to be a real temperature. Further, while it was for a different issue, I notice that a user on the L1Techs forum posted a log for their Gigabyte X50 Aorus Master with the same temperature/critical values reported in 2020 (edited once I regained link privileges).

Therefore, all things considered, I think this is likely to be a quirk of the Gigabyte X570 platform. Perhaps some places where thermistors were supposed to be just have resistors on them? Who knows.

On my machine, it should be possible to disable the offending behaviour by running

echo disabled > /sys/class/thermal/thermal_zone1/mode

as root. From the logs, this should also work for @BeepBoopImAComputa. For others, you should check which thermal_zone triggers the critical temperature error in the logs and update the command accordingly.

Note that this command has some risk attached to using it - it relies on this error actually being a hardware quirk rather than actual overheating of some component. If it’s the latter, disabling the protection could cause a problem. Further, I can’t verify that it’s a guaranteed fix, as for me the behaviour is quite intermittent.

In terms of why this behaviour isn’t more widely known, it’s probably because it does not manifest on Ubuntu, or at least when I was using it. This likely means that either Ubuntu knows about this behaviour and has patched it out themselves, or there is some difference between Ubuntu and Manjaro (for example, Manjaro using a newer kernel version) that causes the problem to manifest on Manjaro.

1 Like
17

@dgdg Thank you for your response I have tested this and it works!

18

For posterity, the earlier fix is only until reboot. To make this permanent the command needs to be run at boot, which can be done by a systemd service. Take the following service configuration

[Unit]
Description=Gigabyte X570 Platform Sensor Fix

[Service]
ExecStart=/bin/sh -c 'echo disabled > /sys/class/thermal/thermal_zone1/mode'

[Install]
WantedBy=multi-user.target

and save it to /etc/systemd/system/gigabyte-x570-fix.service. Then run sudo systemctl enable --now gigabyte-x570-fix.service to enable the service, and it should automatically apply the fix at boot from now on.

1 Like
19

This topic was automatically closed 3 hours after the last reply. New replies are no longer allowed.