Since the intel_pstate driver is asking for 3.4 GHz, but the processor itself is only granting 0.8 GHz we now know that the throttling is within the processor and not externally driven.
It might be related to what koba noted in comment #8, I don't know. The processor has MSRs with bits to indicate the reasons it is throttling, which is the next place to look. Myself, I am tried of decoding the common MSR bits, so I wrote a decoder. It is at (coded so as to avoid bots): double u double u double u dot smythies dot com /~doug/temp_kernel/ Both the c code and compiled, msr-decoder.c run as sudo: "sudo ./msr-decoder" and post the output here. There is also a log bit reset program, that clears held bits for ongoing work. If you do not want to use my programs, then read MSR's 0x19c, 0x1aa, 0x1b1, 0x16f, 0x1fc and post the contents here. As a side note: Your /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq:800000 is not 50% of maximum as dictated by /sys/devices/system/cpu/intel_pstate/min_perf_pct:50. I had thought the two getting out of sync had been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
