Sometimes the system is very slow, in terms of how fast applications work. After I reboot, maybe a few times, the system returns to a normal state. There are no background activities that affect the booting process or after. The settings in BIOS are to default.
Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu the process is noticeable slow, even dragging a terminal window is slow. Linux Mint is faster, although starting a CPU benchmark will quickly show the slowness.
Windows 10 does not have any issues.
I suspect that it remains at 800 MHz.
----
Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700 512GB SSD 8GB using Ubuntu 20 or Linux Mint or Win 10.
Kernel: 5.11.0-37-generic
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
4800000
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
800000
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 16
On-line CPU(s) list: 0-15
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 165
Model name: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
Stepping: 5
CPU MHz: 2900.000
CPU max MHz: 4800,0000
CPU min MHz: 800,0000
BogoMIPS: 5799.77
Virtualization: VT-x
L1d cache: 256 KiB
L1i cache: 256 KiB
L2 cache: 2 MiB
L3 cache: 16 MiB
NUMA node0 CPU(s): 0-15
Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB filling
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
s ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
top_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
cid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
avec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
1d arch_capabilities
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 4294.55 ms.
hardware limits: 800 MHz - 4.80 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 800 MHz and 4.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 829 MHz.
analyzing CPU 1:
driver: intel_pstate
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 4294.55 ms.
hardware limits: 800 MHz - 4.80 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 800 MHz and 4.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
...
analyzing CPU 15:
driver: intel_pstate
CPUs which run at the same hardware frequency: 15
CPUs which need to have their frequency coordinated by software: 15
hardware limits: 800 MHz - 4.80 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 800 MHz and 4.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 3.92 GHz.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: alin 4180 F.... pulseaudio
/dev/snd/controlC0: alin 4180 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-07-27 (71 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
MachineType: ASUSTeK COMPUTER INC. ASUS EXPERTCENTER D700TA_D700TA
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=dcba4ac8-878e-4597-90f7-80a1acec490e ro
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
RelatedPackageVersions:
linux-restricted-modules-5.11.0-27-generic N/A
linux-backports-modules-5.11.0-27-generic N/A
linux-firmware 1.187.16
Tags: focal
Uname: Linux 5.11.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/25/2021
dmi.bios.release: 5.17
dmi.bios.vendor: ASUSTeK COMPUTER INC.
dmi.bios.version: D700TA.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: D700TA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 3
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvrD700TA.306:bd06/25/2021:br5.17:svnASUSTeKCOMPUTERINC.:pnASUSEXPERTCENTERD700TA_D700TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnD700TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct3:cvr1.0:
dmi.product.family: ASUS EXPERTCENTER
dmi.product.name: ASUS EXPERTCENTER D700TA_D700TA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1946323
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.