I run watch -n1 grep -i MHz /proc/cpuinfo in a Yakuake tab to keep an eye on CPU frequencies. It shows the frequency of every CPU thread, down to a single MHz. Or did.
After the last testing update on February 24th, it has started to report values like this:
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 3700.000
cpu MHz : 2197.728
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
cpu MHz : 2200.000
Only a thread or two shows a more specific value at a time. And it shifts from thread to thread (as is expected). These values seem more like “power states” of threads than their true frequencies.
Meanwhile, inxi reports values that are very specific per thread, and pretty much mirror what /proc/cpuinfo used to report. Here you can see the values reported, along with the rest of my system information:
inxi -Fxza
System: Kernel: 5.11.1-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.11-x86_64 root=UUID=c28c9ba1-1ab9-48ed-a6c3-a5cf6794acea ro apparmor=1
security=apparmor udev.log_priority=3 sysrq_always_enabled=1
Desktop: KDE Plasma 5.21.1 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
Machine: Type: Desktop Mobo: Micro-Star model: B450M MORTAR MAX (MS-7B89) v: 1.0 serial: <filter>
UEFI: American Megatrends LLC. v: 2.C0 date: 02/01/2021
CPU: Info: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+ family: 17 (23) model-id: 8 stepping: 2
microcode: 800820D L2 cache: 4 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 118445
Speed: 2347 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 1: 2347 2: 1917 3: 1868 4: 2986 5: 1891
6: 2199 7: 1887 8: 1965 9: 1969 10: 3759 11: 1967 12: 2160 13: 2008 14: 1889 15: 2429 16: 2070
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: ASUSTeK driver: nvidia v: 460.39 alternate: nouveau,nvidia_drm
bus ID: 26:00.0 chip ID: 10de:1b06 class ID: 0300
Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: nvidia display ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.7x13.5") s-diag: 692mm (27.3")
Monitor-1: DP-0 res: 2560x1440 hz: 144 dpi: 109 size: 597x336mm (23.5x13.2") diag: 685mm (27")
OpenGL: renderer: GeForce GTX 1080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 direct render: Yes
Audio: Device-1: NVIDIA GP102 HDMI Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 26:00.1
chip ID: 10de:10ef class ID: 0403
Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus ID: 28:00.3 chip ID: 1022:1457 class ID: 0403
Device-3: GYROCOM C&C UAC1 DAC type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-10:2 chip ID: 1852:5110
class ID: 0102
Sound Server: ALSA v: k5.11.1-1-MANJARO
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel
port: e000 bus ID: 22:00.0 chip ID: 10ec:8168 class ID: 0200
IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID: Supported mdraid levels: raid0
Device-1: md0 maj-min: 9:0 type: mdraid level: raid-0 status: active size: 744.74 GiB
Info: report: N/A blocks: 780914688 chunk size: 512k super blocks: 1.2
Components: Online:
0: sdb maj-min: 8:16 size: 186.31 GiB
1: sdc maj-min: 8:32 size: 186.31 GiB
2: sdd maj-min: 8:48 size: 186.31 GiB
3: sde maj-min: 8:64 size: 186.31 GiB
Drives: Local Storage: total: raw: 1.18 TiB usable: 1.18 TiB used: 431.27 GiB (35.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 4B6Q scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 model: SSD 910 200GB size: 186.31 GiB block size: physical: 4096 B logical: 512 B
rotation: SSD serial: N/A rev: a424
ID-3: /dev/sdc maj-min: 8:32 model: SSD 910 200GB size: 186.31 GiB block size: physical: 4096 B logical: 512 B
rotation: SSD serial: N/A rev: a424
ID-4: /dev/sdd maj-min: 8:48 model: SSD 910 200GB size: 186.31 GiB block size: physical: 4096 B logical: 512 B
rotation: SSD serial: N/A rev: a424
ID-5: /dev/sde maj-min: 8:64 model: SSD 910 200GB size: 186.31 GiB block size: physical: 4096 B logical: 512 B
rotation: SSD serial: N/A rev: a424
Partition: ID-1: / raw size: 465.26 GiB size: 456.96 GiB (98.22%) used: 192.36 GiB (42.1%) fs: ext4 dev: /dev/sda2
maj-min: 8:2
ID-2: /boot/efi raw size: 512 MiB size: 511 MiB (99.80%) used: 312 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap: Kernel: swappiness: 20 (default 60) cache pressure: 100 (default)
ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2 file: /mnt/faaast/swap
Sensors: System Temperatures: cpu: 47.0 C mobo: 41.0 C gpu: nvidia temp: 42 C
Fan Speeds (RPM): fan-1: 0 fan-2: 1337 fan-3: 977 fan-4: 638 fan-5: 874 gpu: nvidia fan: 32%
Info: Processes: 314 Uptime: 39m wakeups: 0 Memory: 31.35 GiB used: 2.56 GiB (8.2%) Init: systemd v: 247 Compilers:
gcc: 10.2.0 Packages: pacman: 1373 lib: 422 Shell: Zsh v: 5.8 running in: yakuake inxi: 3.3.01
(Both commands were under pretty much the same load)
Has cpuinfo been hit by some bug, or is this a deliberate change? And what source does inxi use to get these seemingly more accurate values?
Edit: I just realised there’s been an update in the Testing branch today. 
I will report back after it lands in my mirrors, and I’m up-to-date.