Ich habe ein
Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Memory 16305MB (2531MB used)
Machine Type Laptop
Operating System Ubuntu 20.04.3 LTS
In meinem/etc/default/grubDatei habe ich die Zeile
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable"
Ich habe einsudo update-grubnach den Änderungen, aber wenn ich ein cpupower-Frequenzinfo oder cpufreq-info --driveres heißt, der verwendete Treiber istintel_cpufreq
rt@sys76:~$ cpufreq-info --driver
intel_cpufreq
rt@sys76:~$ cpupower frequency-info
analyzing CPU 0:
driver: intel_cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 20.0 us
hardware limits: 800 MHz - 3.40 GHz
available cpufreq governors: conservative ondemand userspace powersave performance schedutil
current policy: frequency should be within 1.70 GHz and 3.40 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 798 MHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
rt@sys76:~$
Wie erhalte ich diecpufreq-info --Treiber benutzenintel_pstateTreiber?
Antwort1
Ihr Prozessor, i7-4700MQ, ist älter als die HWP-Steuerung (Hardware Pstate). Der von der Kernel-Energieverwaltungsgruppe festgelegte Migrationspfad für diese Intel-Prozessoren besteht darin, standardmäßig den intel_pstate CPU-Frequenzskalierungstreiber im passiven Modus mithilfe des Schedutil-Skalierungsreglers zu verwenden. Zu diesem Zweck wurde dieser Commit durchgeführt:
Commit 33aa46f252c703e42c81a76696cd0c240f2281e4 Autor: Rafael J. Wysocki[email geschützt]Datum: Mi 25. März 15:03:35 2020 +0100
cpufreq: intel_pstate: Use passive mode by default without HWP After recent changes allowing scale-invariant utilization to be used on x86, the schedutil governor on top of intel_pstate in the passive mode should be on par with (or better than) the active mode "powersave" algorithm of intel_pstate on systems in which hardware-managed P-states (HWP) are not used, so it should not be necessary to use the internal scaling algorithm in those cases. Accordingly, modify intel_pstate to start in the passive mode by default if the processor at hand does not support HWP of if the driver is requested to avoid using HWP through the kernel command line. Among other things, that will allow utilization clamps and the support for RT/DL tasks in the schedutil governor to be utilized on systems in which intel_pstate is used.
Sie verwenden tatsächlich den CPU-Frequenzskalierungstreiber intel_pstate, allerdings im passiven Modus. Versuchen Sie Folgendes:
echo active | sudo tee /sys/devices/system/cpu/intel_pstate/status
und dann prüfen:
cat /sys/devices/system/cpu/intel_pstate/status
Wenn das wie erwartet funktioniert, ändern Sie Ihre Grub-Zeile wie folgt:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=active"
und prüfen Sie, ob es wie gewünscht bootet.
Beachten Sie, dass der CPU-Frequenzskalierungstreiber intel_cpufreq
nur der intel_pstate
Treiber im passiven Modus ist.
Beispiel:
doug@s19:~/temp$ grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu10/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu11/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu1/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu2/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu3/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu4/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu5/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu6/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu7/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu8/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu9/cpufreq/scaling_driver:intel_cpufreq
doug@s19:~/temp$ cat /sys/devices/system/cpu/intel_pstate/status
passive
doug@s19:~/temp$ echo active | sudo tee /sys/devices/system/cpu/intel_pstate/status
active
doug@s19:~/temp$ grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu10/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu11/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu1/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu2/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu3/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu4/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu5/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu6/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu7/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu8/cpufreq/scaling_driver:intel_pstate
/sys/devices/system/cpu/cpu9/cpufreq/scaling_driver:intel_pstate
Antwort2
Das Netzteil des Laptops funktionierte nicht mehr und ich habe es ausgetauscht. Plötzlich funktionierten die CPUs wieder einwandfrei. Es sah so aus, als wäre das Netzteil defekt gewesen und hätte nicht genug Strom geliefert.