Kinoite Overheats When Resuming From Sleep

Ask Fedora
, , , , ,
1

Hi all,

I’m a relatively new Fedora/Kinoite user and have been struggling with an annoying issue that I can’t find anyone else posting about anywhere. Roughly 30% of the time, when I resume the machine from sleep, it immediately reboots, and when I check the logs with journalctl -b -1 -k afterwards I can see it was shut down due to the CPU temperature getting too high:

Mar 19 18:44:39 fedora kernel: CPU13 is up
Mar 19 18:44:39 fedora kernel: smpboot: Booting Node 0 Processor 14 APIC 0xd
Mar 19 18:44:39 fedora kernel: CPU14 is up
Mar 19 18:44:39 fedora kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Mar 19 18:44:39 fedora kernel: CPU15 is up
Mar 19 18:44:39 fedora kernel: ACPI: PM: Waking up from system sleep state S3
Mar 19 18:44:39 fedora kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: PSP is resuming...
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: reserve 0xa00000 from 0x81fd000000 for PSP TMR
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: RAS: optional ras ta ucode is not available
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: SMU is resuming...
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b3100 (59.49.0)
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: SMU driver if version not matched
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: use vbios provided pptable
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: SMU is resumed successfully!
Mar 19 18:44:39 fedora kernel: [drm] kiq ring mec 2 pipe 1 q 0
Mar 19 18:44:39 fedora kernel: [drm] DMUB hardware initialized: version=0x02020020
Mar 19 18:44:39 fedora kernel: ata9: SATA link down (SStatus 0 SControl 300)
Mar 19 18:44:39 fedora kernel: ata3: SATA link down (SStatus 0 SControl 300)
Mar 19 18:44:39 fedora kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 19 18:44:39 fedora kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 19 18:44:39 fedora kernel: ata4.00: supports DRM functions and may not be fully accessible
Mar 19 18:44:39 fedora kernel: ata6.00: supports DRM functions and may not be fully accessible
Mar 19 18:44:39 fedora kernel: ata6.00: NCQ Send/Recv Log not supported
Mar 19 18:44:39 fedora kernel: sd 5:0:0:0: [sdc] Starting disk
Mar 19 18:44:39 fedora kernel: ata6.00: supports DRM functions and may not be fully accessible
Mar 19 18:44:39 fedora kernel: ata6.00: NCQ Send/Recv Log not supported
Mar 19 18:44:39 fedora kernel: ata6.00: configured for UDMA/133
Mar 19 18:44:39 fedora kernel: sd 3:0:0:0: [sda] Starting disk
Mar 19 18:44:39 fedora kernel: ata4.00: supports DRM functions and may not be fully accessible
Mar 19 18:44:39 fedora kernel: ata4.00: configured for UDMA/133
Mar 19 18:44:39 fedora kernel: ata4.00: Enabling discard_zeroes_data
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Mar 19 18:44:39 fedora kernel: amdgpu 0000:0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Mar 19 18:44:39 fedora kernel: PM: resume devices took 0.641 seconds
Mar 19 18:44:39 fedora kernel: OOM killer enabled.
Mar 19 18:44:39 fedora kernel: Restarting tasks ... done.
Mar 19 18:44:39 fedora kernel: random: crng reseeded on system resumption
Mar 19 18:44:39 fedora kernel: PM: suspend exit
Mar 19 18:44:39 fedora kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 19 18:44:39 fedora kernel: sd 9:0:0:0: [sdd] Starting disk
Mar 19 18:44:39 fedora kernel: ata10.00: configured for UDMA/133
Mar 19 18:44:39 fedora kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 19 18:44:39 fedora kernel: sd 4:0:0:0: [sdb] Starting disk
Mar 19 18:44:39 fedora kernel: ata5.00: configured for UDMA/133
Mar 19 18:44:40 fedora kernel: thermal thermal_zone1: acpitz: critical temperature reached
Mar 19 18:44:40 fedora kernel: reboot: HARDWARE PROTECTION shutdown (Temperature too high)

There are never any issues with heat otherwise, I have a lot of fans in this case and the temperature usually idles around 30C and maxes out at 70-80C under extremely high loads. It also resumes fine ~70% of the time.

Has anyone else encountered this? Why would the CPU be heating up when the computer is sleeping? Is there anything I can do about it?

Thanks!

1 Like
3

Hi Algebro,

The only thing that comes to mind is are the fans running as soon as the machine resumes from sleep? If not, it could be that the CPU is getting hot enough/fast enough that the fans are not keeping up with the sudden demand of a resume. Also, I would check the heatsink and the heatsink compound for the CPU … are they undersized/insufficient? … those are the only things that come to mind at the moment …

4

This is my guess too, but is there any way to adjust that in Kinoite?

5

Hi Algebro,

is there any way to adjust that in Kinoite?

It really depends on the motherboard/mfg. The first palce I would look would be in BIOS settings for the fan control/thermal controls. As an example, on my machine I can set the fan speeds and timing from BIOS. Not all machines can do this … and to complicate things a bit more … there is a thing called the EC tables for the specific motherboard. Some mfgs. have provided interface drivers for this in Linux but it is rare … In the past I had similar issues with one of my machines and I resorted to just keeping one of the cooling fans running full time for as long as power was available to the motherboard… not pretty but it worked …

8

You can change the sleep state between s2idle and s3 in the BIOS often.

You could check if that is a workaround.

Normally the fans should still be controlled when suspending though