Ryzen 7 Pro 3700U stuck at 399MHz after wake from suspend

myu · 2021-02-15 13:49:38

System Description

Thinkpad T495
Linux 5.10.15-arch1-1
AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile

Issue Description

The CPU often gets stuck at 399MHz after resuming from suspend. Although this doesn't always occur, I haven't found a way to consistently reproduce the issue. The only workaround is to reboot the system, where the CPU starts to perform as expected again. This is an issue I have been dealing with since purchasing the laptop (Sept. 2019).

I'm currently on the latest BIOS version (1.27 R12ET57W) and my system is up to date. The CPU governor is set to 'schedutil'. I have tried switching to 'ondemand', but still ran into the same problem. It shouldn't be an overheating issue since my CPU is usually quite cool (between 50-60°) and the issue seems to occur regardless of the temperature.

Other possibly relevant information:

Fastboot is disabled
amd-ucode is a boot parameter

I have also created a post in the AMD community but am hoping someone here has found a working solution.

Ryzen 7 PRO 3700U CPU log

gnox · 2021-02-15 14:30:23

Looks almost similar to this : https://www.phoronix.com/scan.php?page= … hermal-Fix, an acpi issue, I dont know if the module asus_nb_wmi can be loaded in that laptop but you can try it and set 0 to /sys/devices/platform/asus-nb-wmi/throttle_thermal_policy after resuming from suspend.

xerxes_ · 2021-02-15 15:50:32

What about cpupower? Will not work? For example: 'cpupower frequency-set -f 3Ghz', 'cpupower frequency-set -g performance', 'cpupower frequency-set -d min_clock_freq' ?

myu · 2021-02-17 19:37:53

xerxes_ wrote:

What about cpupower? Will not work? For example: 'cpupower frequency-set -f 3Ghz', 'cpupower frequency-set -g performance', 'cpupower frequency-set -d min_clock_freq' ?

Unfortunately this does not work. I'm able to set the frequency via '-f/-g/-d', however the changes don't have an effect on the actual frequency. Strangely enough, I get different readings when running 'cpupower frequency-info' as root rather than user:

$ cpupower frequency-info

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

$ sudo cpupower frequency-info

analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 1.40 GHz - 2.30 GHz
  available frequency steps:  2.30 GHz, 1.70 GHz, 1.40 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 2.00 GHz and 2.30 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency: 2.30 GHz (asserted by call to hardware)
  boost state support:
    Supported: no
    Active: no
    Boost States: 0
    Total States: 3
    Pstate-P0:  2300MHz
    Pstate-P1:  1700MHz
    Pstate-P2:  1400MHz

I'm not sure what causes this behavior, but running as root reads a different 'current CPU frequency' value. When setting the governor, the changes are reflected in the 'current policy' value when running 'cpupower frequency-info' as user, however, the frequency stays at 399MHz. When watching the cpu frequencies, I can confirm that they stay at 399MHz, even when set using cpupower as root.

Arch Linux

#1 2021-02-15 13:49:38