Testers for inxi/pinxi redone -C CPU logic... huge internal changes

truepatriot76 · 11-28-2021, 12:14 AM

Recent AMD Platform

Code:

$ inxi -MCazy
Machine:
  Type: Desktop Mobo: ASRock model: X570 Taichi serial: <filter> 
  UEFI: American Megatrends v: P4.60 date: 08/03/2021 
CPU:
  Info: 8-Core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 
  type: MT MCP arch: Zen 3 family: 19 (25) model-id: 50 (80) stepping: 0 
  microcode: A50000C cache: L2: 4 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 121599 
  Speed: 1397 MHz min/max: 1400/3800 MHz boost: enabled Core speeds (MHz): 
  1: 1397 2: 1395 3: 1398 4: 1397 5: 1397 6: 1397 7: 1395 8: 1396 9: 1394 
  10: 1400 11: 1399 12: 1399 13: 1406 14: 1399 15: 1392 16: 1399 
  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, IBRS_FW, 
  STIBP: always-on, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
$ ./pinxi -MCazy
Machine:
  Type: Desktop Mobo: ASRock model: X570 Taichi serial: <superuser required>
  UEFI: American Megatrends v: P4.60 date: 08/03/2021
CPU:
  Info: 8-Core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64
  type: MT MCP arch: Zen 3 family: 19 (25) model-id: 50 (80) stepping: 0
  microcode: A50000C cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
  desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
  flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 7599
  Speed (MHz): avg: 1876 high: 2846 min/max: 1400/4672 boost: enabled cores:
  1: 2215 2: 1412 3: 2239 4: 1406 5: 2413 6: 2365 7: 1392 8: 1619 9: 2291
  10: 1394 11: 2401 12: 1415 13: 1413 14: 2846 15: 1409 16: 1788
  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, IBRS_FW,
  STIBP: always-on, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected

$ ./pinxi --version | grep ^pinxi
pinxi 3.3.09-10 (2021-11-26)

JayByrd · 11-28-2021, 12:18 AM

Another AMD, i586 (my Slackpowered print/ntp/dns-server and fax machine box):

Code:

miah@fax:~$ inxi --version
inxi 3.3.09-00 (2021-11-22) 
miah@fax:~$ inxi -MCazy
Machine:
  Type: Unknown Mobo: ASUSTeK model: P5A-B v: REV 1.XX
  serial: <superuser required> BIOS: Award
  v: ASUS P5A-B Revision 1011 Beta 005 date: 05/02/02
CPU:
  Info: Single Core model: AMD-K6 3D bits: 32 type: UP arch: K6-2 family: 5
  model-id: 8 stepping: C (12) microcode: N/A cache: L1: 64 KiB L2: 64 KiB
  flags: N/A bogomips: 570
  Speed: 285 MHz min/max: N/A Core speed (MHz): 1: 285
  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 status: Vulnerable
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
  mitigation: Full generic retpoline, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected

miah@fax:~$ ./pinxi --version
pinxi 3.3.09-09 (2021-11-26)
miah@fax:~$ ./pinxi -MCazy1  
Machine:
  Type: Unknown
  Mobo: ASUSTeK
    model: P5A-B
    v: REV 1.XX
    serial: <superuser required>
  BIOS: Award
    v: ASUS P5A-B Revision 1011 Beta 005
    date: 05/02/02

CPU:
  Info: Single Core
    model: AMD-K6 3D
    bits: 32
    type: UP
    arch: K6-2
    family: 5
    model-id: 8
    stepping: C (12)
    microcode: N/A
    cache:
      L2: 64 KiB
    flags: N/A
    bogomips: 570
  Speed (MHz): 285
    min/max: N/A
    core:
      1: 285
  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
      status: Vulnerable
    Type: spectre_v1
      mitigation: usercopy/swapgs barriers and __user pointer sanitization
    Type: spectre_v2
      mitigation: Full generic retpoline, STIBP: disabled, RSB filling
    Type: srbds
      status: Not affected
    Type: tsx_async_abort
      status: Not affected

I'll get to the Intel rigs eventually.

h2-1 · 11-28-2021, 12:27 AM

bw42, how many actual cores does your PPC have? That's an amazing processor, but pinxi seems to believe it has 4 threads per core, can that be right? The data shows that too. I actually made a concrete decision in the refactor to not assume 2 threads only per core, and allowed any number since who knows what the future brings, but is this correct?

I thought I'd done a lot of research on what is going on with CPUs, but your PowerPC system shows I didn't do enough, LOL.

It does look also like it failed to match the if (that's what IF-ID-XX means, failed to match the IF to the device) devices to the network device, with one exception, that may be fixable, I will have to check. Yes, it definitely failed to get a match, checking. I've never seen a PowerPC system like this before so I'll have to think on this one.

willysr · 11-28-2021, 12:29 AM

Here's on my desktop

Quote:

Machine:
Type: Desktop System: Gigabyte product: AB350M-Gaming 3 v: N/A serial: N/A
Mobo: Gigabyte model: AB350M-Gaming 3-CF v: x.x serial: N/A
UEFI-[Legacy]: American Megatrends v: F30 date: 04/18/2019
CPU:
Info: 6-Core model: AMD Ryzen 5 1600X socket: AM4 bits: 64 type: MT MCP
arch: Zen family: 17 (23) model-id: 1 stepping: 1 microcode: 8001137 cache:
L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB
L3: 16 MiB desc: 2x8 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 7185
Speed (MHz): avg: 2329 high: 3675 min/max: 2200/3600 base/boost: 3600/4100
boost: enabled volts: 1.4 V ext-clock: 100 MHz cores: 1: 2187 2: 2119
3: 2195 4: 2130 5: 1894 6: 3675 7: 2194 8: 2193 9: 2195 10: 2110 11: 2111
12: 2952
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

bw42 · 11-28-2021, 12:32 AM

Quote:

Originally Posted by h2-1

bw42, how many actual cores does your PPC have? That's an amazing processor, but pinxi seems to believe it has 4 threads per core, can that be right? The data shows that too. I actually made a concrete decision in the refactor to not assume 2 threads only per core, and allowed any number since who knows what the future brings, but is this correct?

I thought I'd done a lot of research on what is going on with CPUs, but your PowerPC system shows I didn't do enough, LOL.

It does look also like it failed to match the if (that's what IF-ID-XX means, failed to match the IF to the device) devices to the network device, with one exception, that may be fixable, I will have to check. Yes, it definitely failed to get a match, checking. I've never seen a PowerPC system like this before so I'll have to think on this one.

Its an 8-core POWER9 with SMT4, so 4 threads per core.
The board has multiple NICs, one shared with OpenBMC, and one I have configured for bridging with LXC containers.
Not sure if that would cause problems with your program.

h2-1 · 11-28-2021, 12:40 AM

bw42, your power pc has some very good corner cases, you should have also seen some sensors data in inxi at least, but it failed to handle that, I'm going to take a look at some of these things tomorrow, but have to call it a night today. I'm amazed at how much did show given I've seen I think only one or two power pc datasets, but the things that failed aren't specific to power pc, so those are worth dealing with.

The networking issues come about from a case where inxi is using SOC ARM type logic to get the device paths, and I think failing to get the right path, the data appears to be there, but I have to be careful with that to avoid breaking anything, but I think maybe if I add some tests I can get those to connect as expected.

The sensors likewise I think I can get at least partially working, though I don't think I can get a match to the actual field name, but that's got excellent sensors data, and would be a shame not to show some.

Thanks for confirming 4 threads per core, what's funny is I had no idea that existed, but figured it might one day, so added that support in anyway.

I'm thinking maybe not the worst idea to have inxi show how many threads per core it detected, since it has the data internally anyway. I'll work on that tomorrow.

Impressive machine though.

thanks

h2-1 · 11-28-2021, 12:47 AM

willysr, that looks solid, thanks. Given that MT doesn't just mean 2 threads, as we see here, I think it's worth listing how many per core it did detect to avoid ambiguity. I'd been assuming always 2, but maybe in future more, but given we have here 2 in your case, and 4 in bw42's power pc case, it's clear that actually showing that count might be worth it.

h2-1 · 11-28-2021, 01:04 AM

JayByrd, that's a great one, inxi was wrong on the L1/L2, but for some reason pinxi is also believing it has L2 when it only has L1:
https://www.cpu-world.com/CPUs/K6-2/...3D-300AFR.html

These are almost too good to be true, thanks so much.

Can you paste the output of these two somewhere:

Code:

for i in $(ls /sys/devices/system/cpu/{cpu*/topology,cpu*/cpufreq,cpu*/cache/index*,smt}/*);do echo -n "$i::";cat $i;done > cpu-sys.txt
cat /proc/cpuinfo > cpuinfo.txt

The first one is the closest I can get to a one liner for most of the /sys data used for cpu, not all of it, but most.

My suspicion is that the CPU itself is reporting it wrong, and calling Level 1 cache level 2, so pinxi can't tell the difference there.

I suspect inxi had two because it may have gotten the right one from dmidecode, and the wrong one from /proc/cpuinfo. Excellent corner case however.

Note that I don't mind if pinxi is wrong on these if the actual data is wrong, but if it's wrong due to a bug or other issue, then I definitely want to fix it.

My oldest running system is a 1998 gateway laptop, with pentium MMX CPU, that one is excellent to test optimizations since they actually show up as real time saved in execution, not milliseconds. But this K6 is great, though it has cache, unlike my old pentium mmx.

JayByrd · 11-28-2021, 01:43 AM

I'm glad to be of help. Here's the info you requested about my last post:

Code:

miah@fax:~$ cat /proc/cpuinfo
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 5
model		: 8
model name	: AMD-K6(tm) 3D processor
stepping	: 12
cpu MHz		: 285.221
cache size	: 64 KB
fdiv_bug	: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr cx8 pge mmx syscall 3dnow k6_mtrr 3dnowprefetch vmmcall
bugs		: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips	: 570.44
clflush size	: 32
cache_alignment	: 32
address sizes	: 32 bits physical, 32 bits virtual
power management:

miah@fax:~$ for i in $(ls /sys/devices/system/cpu/{cpu*/topology,cpu*/cpufreq,cpu*/cache/index*,smt}/*);do echo -n "$i::";cat $i;done 
/bin/ls: cannot access '/sys/devices/system/cpu/cpu*/cpufreq/*': No such file or directory
/bin/ls: cannot access '/sys/devices/system/cpu/cpu*/cache/index*/*': No such file or directory
/bin/ls: cannot access '/sys/devices/system/cpu/smt/*': No such file or directory
/sys/devices/system/cpu/cpu0/topology/core_id::0
/sys/devices/system/cpu/cpu0/topology/core_siblings::1
/sys/devices/system/cpu/cpu0/topology/core_siblings_list::0
/sys/devices/system/cpu/cpu0/topology/physical_package_id::0
/sys/devices/system/cpu/cpu0/topology/thread_siblings::1
/sys/devices/system/cpu/cpu0/topology/thread_siblings_list::0

JayByrd · 11-28-2021, 01:55 AM

And here's an old(ish) Intel

Code:

mikebig@BOINC2:/boot/initrd-tree$ inxi --version
inxi 3.3.09-00 (2021-11-22)
mikebig@BOINC2:/boot/initrd-tree$ inxi -MCazy
Machine:
  Type: Unknown Mobo: Intel model: D865GBF v: AAC25843-409
  serial: <superuser required> BIOS: Intel v: BF86510A.86A.0077.P25.0508040031
  date: 08/04/2005
CPU:
  Info: Single Core model: Intel Celeron bits: 32 type: MCP
  arch: Netburst Northwood family: F (15) model-id: 2 stepping: 9
  microcode: 2E cache: L1: 8 KiB L2: 128 KiB
  flags: ht pae sse sse2 bogomips: 5187
  Speed: 2594 MHz min/max: N/A Core speed (MHz): 1: 2594
  Vulnerabilities: Type: itlb_multihit status: Processor vulnerable
  Type: l1tf mitigation: PTE Inversion
  Type: mds
  status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
  Type: meltdown status: Vulnerable
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
  mitigation: Full generic retpoline, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected

mikebig@BOINC2:/boot/initrd-tree$ ~/pinxi --version
pinxi 3.3.09-10 (2021-11-26)
mikebig@BOINC2:/boot/initrd-tree$ ~/pinxi -MCazy
Machine:
  Type: Unknown Mobo: Intel model: D865GBF v: AAC25843-409
  serial: <superuser required> BIOS: Intel v: BF86510A.86A.0077.P25.0508040031
  date: 08/04/2005
CPU:
  Info: Single Core model: Intel Celeron bits: 32 type: MCP
  arch: Netburst Northwood family: F (15) model-id: 2 stepping: 9
  microcode: 2E cache: L2: 128 KiB
  flags: ht pae sse sse2 bogomips: 5187
  Speed (MHz): 2594 min/max: N/A core: 1: 2594
  Vulnerabilities: Type: itlb_multihit status: Processor vulnerable
  Type: l1tf mitigation: PTE Inversion
  Type: mds
  status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
  Type: meltdown status: Vulnerable
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
  mitigation: Full generic retpoline, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected

drgibbon · 11-28-2021, 02:24 AM

Things look correct for Purism Librem Mini:

Code:

$~ inxi --version               
inxi 3.3.09-00 (2021-11-22)

$~ inxi -MCazy                                                                                                                  Machine:
  Type: Desktop System: Purism product: Librem Mini v: 1.0
  serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: Purism model: Librem Mini v: 1.0 serial: <superuser required>
  BIOS: coreboot v: 4.14-Purism-1 date: 06/18/2021
CPU:
  Info: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP
  arch: Kaby Lake note: check family: 6 model-id: 8E (142) stepping: C (12)
  microcode: EA cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  bogomips: 31999
  Speed: 2242 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 2129 2: 2244
  3: 2257 4: 2148 5: 2149 6: 2156 7: 2199 8: 2160
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
  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: Enhanced IBRS, IBPB: conditional, RSB filling
  Type: srbds mitigation: TSX disabled
  Type: tsx_async_abort status: Not affected

Code:

$~ ./pinxi --version
pinxi 3.3.09-10 (2021-11-26)

$~ ./pinxi -MCazy1
Machine:
  Type: Desktop
  System: Purism
    product: Librem Mini
    v: 1.0
    serial: <filter>
  Chassis: 
    type: 3
    serial: <filter>
  Mobo: Purism
    model: Librem Mini
    v: 1.0
    serial: <filter>
  BIOS: coreboot
    v: 4.14-Purism-1
    date: 06/18/2021

CPU:                                                                                                                                                                  [3/257]
  Info: Quad Core                                                                                                                                                            
    model: Intel Core i7-8565U                                                                                                                                               
    bits: 64                                                                                                                                                                 
    type: MT MCP
    arch: Kaby Lake
      note: check
    family: 6
    model-id: 8E (142)
    stepping: C (12)
    microcode: EA
    L2 cache: 8 MiB
    flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
    bogomips: 31999
  Speed: 1997 MHz
    min/max: 400/4600 MHz
    Core speeds (MHz): 
      1: 1997
      2: 2000
      3: 1968
      4: 2040
      5: 2100
      6: 2008
      7: 2051
      8: 2032
  Vulnerabilities: 
    Type: itlb_multihit
      status: KVM: VMX disabled
    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: Enhanced IBRS, IBPB: conditional, RSB filling
    Type: srbds
      mitigation: TSX disabled
    Type: tsx_async_abort
      status: Not affected

chrisretusn · 11-28-2021, 02:34 AM

Here is my main computer.

Code:

~# inxi --version | grep ^inxi
inxi 3.3.06-00 (2021-07-21)
~# ./pinxi --version | grep ^pinxi
pinxi 3.3.09-10 (2021-11-26)

~# inxi -MCazy
Machine:
  Type: Desktop System: Gigabyte product: M68MT-S2 v: N/A serial: N/A Chassis: 
  type: 3 serial: N/A 
  Mobo: Gigabyte model: M68MT-S2 serial: N/A BIOS: Award v: F1 
  date: 11/15/2010 
CPU:
  Info: Quad Core model: AMD Phenom II X4 840 socket: M2 bits: 64 type: MCP 
  arch: K10 family: 10 (16) model-id: 5 stepping: 3 microcode: 10000C8 cache: 
  L1: 256 KiB L2: 2 MiB L3: 512 KiB 
  flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 25717 
  Speed: 3200 MHz min/max: 800/3200 MHz base/boost: 3200/3200 volts: 1.0 V 
  ext-clock: 200 MHz Core speeds (MHz): 1: 3200 2: 3200 3: 3200 4: 3200 
  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 status: Not affected 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 
  mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 

~# ./pinxi -Cazy
CPU:
  Info: Quad Core model: AMD Phenom II X4 840 socket: M2 bits: 64 type: MCP
  arch: K10 family: 10 (16) model-id: 5 stepping: 3 microcode: 10000C8 cache:
  L1: 512 KiB desc: d-4x64 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB
  L3: 512 KiB
  flags: ht lm nx pae sse sse2 sse3 sse4a svm bogomips: 6429
  Speed (MHz): avg: 3200 min/max: 800/3200 base/boost: 3200/3200
  boost: disabled volts: 1.0 V ext-clock: 200 MHz cores: 1: 3200 2: 3200
  3: 3200 4: 3200
  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 status: Not affected
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
  mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected

I checked against cpu-world.com https://www.cpu-world.com/CPUs/K10/A...40WFK42GM.html
Looks good to my untrained eyes, aside from Level 3 cache size.

My first run I used -MCrazy, LOL. I forgot about that neat feature of inxi, pretty cool.

Code:

Repos:
  Packages: note: see --pkg pkgtool: 1
  slackpkg repos in: /etc/slackpkg/mirrors
  1: file://home/slackware/slackware64-current/
  slackpkg+ repos in: /etc/slackpkg/slackpkgplus.conf
  1: justpkgs ~ dir://home/non-slack/justpkgs/
  2: nonslack ~ file://home/non-slack/slackbuilds/
  3: slackpkgplus ~ https://slakfinder.org/slackpkg+dev/
  4: multilib ~ file://home/non-slack/multilib/current/
  5: restricted ~ file://home/non-slack/alienbob_restricted/current/x86_64/
  6: alienbob ~ file://home/non-slack/alienbob/current/x86_64/

MDKDIO · 11-28-2021, 02:42 AM

My main desktop (laptops will follow)

Code:

bash-5.1$ inxi --version | grep ^inxi
inxi 3.3.09-00 (2021-11-22)

bash-5.1# inxi -MCazy
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B450-PLUS v: Rev X.0x
  serial: <filter> UEFI: American Megatrends v: 2409 date: 12/02/2020
CPU:
  Info: 6-Core model: AMD Ryzen 5 3600 socket: AM4 bits: 64 type: MT MCP
  arch: Zen 2 family: 17 (23) model-id: 71 (113) stepping: 0
  microcode: 8701021 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
  flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 86238
  Speed: 2214 MHz min/max: 2200/3600 MHz base/boost: 3600/4200 boost: enabled
  volts: 1.1 V ext-clock: 100 MHz Core speeds (MHz): 1: 2214 2: 2506 3: 2755
  4: 2200 5: 2189 6: 2075 7: 2207 8: 2388 9: 2191 10: 2274 11: 1980 12: 2145
  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:
  conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected

Laptop1:

Code:

bash-5.1# inxi -MCazy
Machine:
  Type: Laptop System: Hewlett-Packard product: HP Pavilion dm3 Notebook PC
  v: 0486110000241F00110320000 serial: <filter> Chassis: type: 10 serial: N/A
  Mobo: Hewlett-Packard model: 3649 v: 41.3D serial: <filter> BIOS: Insyde
  v: F.19 date: 11/16/2010
CPU:
  Info: Dual Core model: Intel U4100 bits: 64 type: MCP arch: Penryn family: 6
  model-id: 17 (23) stepping: A (10) microcode: A07 cache: L1: 128 KiB
  L2: 4 MiB
  flags: ht lm nx pae sse sse2 sse3 ssse3 bogomips: 5187
  Speed: 1227 MHz min/max: 1200/1300 MHz base/boost: 1300/1300 volts: 1.6 V
  ext-clock: 800 MHz Core speeds (MHz): 1: 1266 2: 1213
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds
  status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
  mitigation: Full generic retpoline, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected

z80 · 11-28-2021, 04:23 AM

From a virtual AMD Epyc system:

Code:

root@marjory:~# inxi --version | grep ^inxi
inxi 3.3.06-00 (2021-07-21)

root@marjory:~# inxi -MCazy
Machine:
  Type: Vmware System: VMware product: VMware Virtual Platform v: N/A 
  serial: <filter> Chassis: No Enclosure type: 1 serial: N/A 
  Mobo: Intel model: 440BX Desktop Reference Platform serial: N/A 
  BIOS: Phoenix v: 6.00 date: 11/12/2020 
CPU:
  Info: Quad Core (4-Die) model: AMD EPYC 7302 bits: 64 type: MCP MCM 
  arch: Zen 2 family: 17 (23) model-id: 31 (49) stepping: 0 microcode: 8301034 
  cache: L1: 64 KiB L2: 2 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
  bogomips: 23999 
  Speed: 3000 MHz min/max: N/A base/boost: 3000/30000 volts: 3.3 V 
  Core speeds (MHz): 1: 3000 2: 3000 3: 3000 4: 3000 
  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 


root@marjory:~# ./pinxi --version | grep ^pinxi
pinxi 3.3.09-10 (2021-11-26)

root@marjory:~# ./pinxi -MCazy1
Machine:
  Type: Vmware
  System: VMware
    product: VMware Virtual Platform
    v: N/A
    serial: <filter>
  Chassis: No Enclosure
    type: 1
    serial: N/A
  Mobo: Intel
    model: 440BX Desktop Reference Platform
    serial: N/A
  BIOS: Phoenix
    v: 6.00
    date: 11/12/2020

CPU:
  Info: Quad Core (4-Die)
    model: AMD EPYC 7302
    bits: 64
    type: MCP MCM
    arch: Zen 2
    family: 17 (23)
    model-id: 31 (49)
    stepping: 0
    microcode: 8301034
    cache:
      L1: 256 KiB
        desc: d-4x32 KiB; i-4x32 KiB
      L2: 2 MiB
        desc: 4x512 KiB
      L3: 128 MiB
        desc: 1x128 MiB
    flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
    bogomips: 5999
  Speed (MHz):
    avg: 3000
    min/max: N/A
    base/boost: 3000/30000
    volts: 3.3 V
    cores:
      1: 3000
      2: 3000
      3: 3000
      4: 3000
  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

z80 · 11-28-2021, 04:32 AM

From Raspberry PI3:

Code:

Machine:
  Type: ARM Device
  System: Raspberry Pi 3 Model B Rev 1.2
    details: BCM2835
    rev: a02082
    serial: <filter>

CPU:
  Info: Quad Core
    model: ARMv7 v7l
    variant: cortex-a53
    bits: 32
    type: MCP
    arch: v7l
    family: 7
    model-id: 0
    stepping: 4
    bogomips: 76
  Speed (MHz):
    avg: 1200
    min/max: 600/1200
    cores:
      1: 1200
      2: 1200
      3: 1200
      4: 1200
  Features: crc32 edsp evtstrm fastmult half idiva idivt lpae neon thumb tls vfp vfpd32 vfpv3 vfpv4
  Vulnerabilities: No CPU vulnerability/bugs data available.