Ttyjfyk

It recently seemed like my fan was running more than average, but I didn't notice anything significant showing in top. I looked via i7zl and found that one core was staying in state C0 ~85% of the time. I downgraded my kernel, and things seemed to be better after a reboot... but it turned out to be connected to startup vs. after a suspend/resume cycle.

Here's a snapshot of i7z after booting:

Real Current Frequency 804.79 MHz [100.10 x 8.04] (Max of below)
 Core [core-id] :Actual Freq (Mult.) C0% Halt(C1)% C3 % C6 % C7 % Temp VCore
 Core 1 [0]: 797.84 (7.97x) 1 0.465 0 0 99.5 42 0.6702
 Core 2 [1]: 802.24 (8.01x) 1 0.218 0 0 99.8 42 0.6710
 Core 3 [2]: 794.34 (7.94x) 1 1.08 0 0 98.9 42 0.6715
 Core 4 [3]: 804.79 (8.04x) 1 1.44 0 0 98.5 41 0.6710

And here's after a suspend/resume cycle:

 Real Current Frequency 3841.43 MHz [100.14 x 38.36] (Max of below)
 Core [core-id] :Actual Freq (Mult.) C0% Halt(C1)% C3 % C6 % C7 % Temp
 Core 1 [0]: 3841.43 (38.36x) 87.3 0 0 0 1 55
 Core 2 [1]: 3641.83 (36.37x) 1.71 16.9 1 1 78.9 43
 Core 3 [2]: 3539.75 (35.35x) 1 0 1 1 98.7 42
 Core 4 [3]: 3642.87 (36.38x) 1 3.24 1 2.15 93.2 42

I have a post about this in the arch linux forums, but I thought I would add here as I'm not sure where to troubleshoot something like this. My cores appear to function normally at boot so my system appears capable of running them properly, it just doesn't do this after suspend/resume?

Thanks for any suggestions or requests for more information.

Linux 5.0.6-arch1-1-ARCH #1 SMP PREEMPT Wed Apr 3 09:35:20 UTC 2019 x86_64 GNU/Linux