Slackware This Forum is for the discussion of Slackware Linux.
Notices
Welcome to
LinuxQuestions.org , a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please
contact us . If you need to reset your password,
click here .
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a
virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month.
Click here for more info.
12-01-2021, 02:44 AM
#121
Member
Registered: Feb 2012
Location: EU
Distribution: Slackware 15 and current
Posts: 94
Rep:
Quote:
Originally Posted by
h2-1
-----------------------------------------
Eeel, that's an interesting point, I wonder how much of this depends on the kernel. Based on what I see on cpu-world.com, it looks like the data pinxi is getting for caches from sys is using the same exact data source as the cpu-world.com data collector (they also rely, like me, lol, on user data for their cpuid stuff), which makes me think this comes from cpuid itself, mapped to /sys data structures.
I actually wish /sys would have the rest of the cpu data, the flags, model, family, stepping, etc, then I could totally skip cpuinfo for data.
Would be interesting to see if you see any differences with different kernel, that's a good idea.
-----------------------------------------
First computer with the 5.4.84 kernel same inxi/pinxi version. Will post other computers a bit later.
Code:
# inxi -MCazy
Machine:
Type: Desktop Mobo: Intel model: DH67CF v: AAG10215-204 serial: <filter>
BIOS: Intel v: BLH6710H.86A.0105.2011.0301.1654 date: 03/01/2011
CPU:
Info: Quad Core model: Intel Core i5-2320 socket: BGA1155 (SKTH) note: check
bits: 64 type: MCP arch: Sandy Bridge family: 6 model-id: 2A (42)
stepping: 7 microcode: 14 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 23944
Speed: 3192 MHz min/max: 1600/3300 MHz base/boost: 3000/4000 volts: 1.7 V
ext-clock: 100 MHz Core speeds (MHz): 1: 3211 2: 2963 3: 3186 4: 2052
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
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
# pinxi -MCazy1
Machine:
Type: Desktop
Mobo: Intel
model: DH67CF
v: AAG10215-204
serial: <filter>
BIOS: Intel
v: BLH6710H.86A.0105.2011.0301.1654
date: 03/01/2011
CPU:
Info: Quad Core
model: Intel Core i5-2320
socket: BGA1155 (SKTH)
note: check
bits: 64
type: MCP
arch: Sandy Bridge
family: 6
model-id: 2A (42)
stepping: 7
microcode: 14
cache:
L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB
L2: 1024 KiB
desc: 4x256 KiB
L3: 6 MiB
desc: 1x6 MiB
flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 5986
Speed (MHz):
avg: 2555
high: 3290
min/max: 1600/3300
base/boost: 3000/4000
volts: 1.7 V
ext-clock: 100 MHz
cores:
1: 1682
2: 2054
3: 3194
4: 3290
Vulnerabilities:
Type: itlb_multihit
status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
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
The previous results with 5.15.4 kernel
Quote:
Code:
# inxi -MCazy
Machine:
Type: Desktop Mobo: Intel model: DH67CF v: AAG10215-204 serial: <filter>
BIOS: Intel v: BLH6710H.86A.0105.2011.0301.1654 date: 03/01/2011
CPU:
Info: Quad Core model: Intel Core i5-2320 socket: BGA1155 (SKTH) note: check
bits: 64 type: MCP arch: Sandy Bridge family: 6 model-id: 2A (42)
stepping: 7 microcode: 14 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 23946
Speed: 1757 MHz min/max: 1600/3300 MHz base/boost: 3000/4000 volts: 1.7 V
ext-clock: 100 MHz Core speeds (MHz): 1: 2079 2: 2911 3: 2565 4: 2661
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
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
# pinxi -MCazy1
Machine:
Type: Desktop
Mobo: Intel
model: DH67CF
v: AAG10215-204
serial: <filter>
BIOS: Intel
v: BLH6710H.86A.0105.2011.0301.1654
date: 03/01/2011
CPU:
Info: Quad Core
model: Intel Core i5-2320
socket: BGA1155 (SKTH)
note: check
bits: 64
type: MCP
arch: Sandy Bridge
family: 6
model-id: 2A (42)
stepping: 7
microcode: 14
cache:
L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB
L2: 1024 KiB
desc: 4x256 KiB
L3: 6 MiB
desc: 1x6 MiB
flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 5986
Speed (MHz):
avg: 1846
high: 2063
min/max: 1600/3300
base/boost: 3000/4000
volts: 1.7 V
ext-clock: 100 MHz
cores:
1: 1762
2: 1860
3: 1699
4: 2063
Vulnerabilities:
Type: itlb_multihit
status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
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
Thinkpad with 5.4.84
Code:
# inxi -MCazy
Machine:
Type: Laptop System: LENOVO product: 20HES18R2A v: ThinkPad T470
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20HES18R2A v: SDK0J40697 WIN serial: <filter>
UEFI: LENOVO v: N1QET87W (1.62 ) date: 02/27/2020
CPU:
Info: Dual Core model: Intel Core i5-7300U socket: BGA1356 (U3E1)
note: check bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check
family: 6 model-id: 8E (142) stepping: 9 microcode: CA cache: L1: 128 KiB
L2: 512 KiB L3: 3 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 21599
Speed: 3500 MHz min/max: 400/3500 MHz base/boost: 2600/2700 volts: 1.1 V
ext-clock: 100 MHz Core speeds (MHz): 1: 3500 2: 3500 3: 3500 4: 3501
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
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 generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
# pinxi -MCazy1
Machine:
Type: Laptop
System: LENOVO
product: 20HES18R2A
v: ThinkPad T470
serial: <filter>
Chassis:
type: 10
serial: <filter>
Mobo: LENOVO
model: 20HES18R2A
v: SDK0J40697 WIN
serial: <filter>
UEFI: LENOVO
v: N1QET87W (1.62 )
date: 02/27/2020
CPU:
Info: Dual Core
model: Intel Core i5-7300U
socket: BGA1356 (U3E1)
note: check
bits: 64
type: MT MCP
arch: Amber/Kaby Lake
note: check
family: 6
model-id: 8E (142)
stepping: 9
microcode: CA
cache:
L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB
desc: 2x256 KiB
L3: 3 MiB
desc: 1x3 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 5399
Speed (MHz):
avg: 3500
min/max: 400/3500
base/boost: 2600/2700
volts: 1.1 V
ext-clock: 100 MHz
cores:
1: 3500
2: 3500
3: 3500
4: 3500
Vulnerabilities:
Type: itlb_multihit
status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown
mitigation: PTI
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 generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds
status: Vulnerable: No microcode
Type: tsx_async_abort
mitigation: Clear CPU buffers; SMT vulnerable
Thinkpad previous test with 5.15.4
Quote:
Code:
# inxi -MCazy
Machine:
Type: Laptop System: LENOVO product: 20HES18R2A v: ThinkPad T470
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20HES18R2A v: SDK0J40697 WIN serial: <filter>
UEFI: LENOVO v: N1QET87W (1.62 ) date: 02/27/2020
CPU:
Info: Dual Core model: Intel Core i5-7300U socket: BGA1356 (U3E1)
note: check bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check
family: 6 model-id: 8E (142) stepping: 9 microcode: CA cache: L1: 128 KiB
L2: 512 KiB L3: 3 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 21599
Speed: 3502 MHz min/max: 400/3500 MHz base/boost: 2600/2700 volts: 1.1 V
ext-clock: 100 MHz Core speeds (MHz): 1: 3502 2: 3483 3: 3500 4: 3500
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
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 generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
# pinxi -MCazy1
Machine:
Type: Laptop
System: LENOVO
product: 20HES18R2A
v: ThinkPad T470
serial: <filter>
Chassis:
type: 10
serial: <filter>
Mobo: LENOVO
model: 20HES18R2A
v: SDK0J40697 WIN
serial: <filter>
UEFI: LENOVO
v: N1QET87W (1.62 )
date: 02/27/2020
CPU:
Info: Dual Core
model: Intel Core i5-7300U
socket: BGA1356 (U3E1)
note: check
bits: 64
type: MT MCP
arch: Amber/Kaby Lake
note: check
family: 6
model-id: 8E (142)
stepping: 9
microcode: CA
cache:
L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB
desc: 2x256 KiB
L3: 3 MiB
desc: 1x3 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 5399
Speed (MHz):
avg: 3425
high: 3501
min/max: 400/3500
base/boost: 2600/2700
volts: 1.1 V
ext-clock: 100 MHz
cores:
1: 3500
2: 3201
3: 3501
4: 3501
Vulnerabilities:
Type: itlb_multihit
status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown
mitigation: PTI
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 generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds
status: Vulnerable: No microcode
Type: tsx_async_abort
mitigation: Clear CPU buffers; SMT vulnerable
Last edited by Eeel; 12-01-2021 at 05:01 AM .
Reason: add other test
12-01-2021, 12:13 PM
#122
Member
Registered: Mar 2004
Location: Sweden
Distribution: Slackware 15
Posts: 521
Rep:
ASUSTek VivoPC VM40B
Code:
# pinxi -MCazy1
Machine:
Type: Desktop
System: ASUSTeK
product: VM40B
v: N/A
serial: <filter>
Mobo: ASUSTeK
model: VM40B
v: Rev 1.xx
serial: <filter>
UEFI: American Megatrends
v: 1501
date: 12/09/2014
CPU:
Info: Dual Core
model: Intel Celeron 1007U
socket: BGA1023
bits: 64
type: MCP
arch: Ivy Bridge
family: 6
model-id: 3A (58)
stepping: 9
microcode: 17
cache:
L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB
desc: 2x256 KiB
L3: 2 MiB
desc: 1x2 MiB
flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
bogomips: 2992
Speed (MHz):
avg: 851
high: 871
min/max: 800/1500
base/boost: 1500/1500
volts: 1.0 V
ext-clock: 100 MHz
cores:
1: 832
2: 871
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
# dmesg | grep micro
[ 0.111982] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
[ 3.862429] microcode: sig=0x306a9, pf=0x10, revision=0x17
[ 3.865206] microcode: Microcode Update Driver: v2.2.
And dmesg after I've loaded the microcode:
Code:
# dmesg | grep micro
[ 0.000000] microcode: microcode updated early to revision 0x21, date = 2019-02-13
[ 3.870719] microcode: sig=0x306a9, pf=0x10, revision=0x21
[ 3.873495] microcode: Microcode Update Driver: v2.2.
And pinxi -MCazy1:
Code:
CPU:
Info: Dual Core
model: Intel Celeron 1007U
socket: BGA1023
bits: 64
type: MCP
arch: Ivy Bridge
family: 6
model-id: 3A (58)
stepping: 9
microcode: 21
cache:
L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB
desc: 2x256 KiB
L3: 2 MiB
desc: 1x2 MiB
flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
bogomips: 2993
Speed (MHz):
avg: 817
high: 836
min/max: 800/1500
base/boost: 1500/1500
volts: 1.0 V
ext-clock: 100 MHz
cores:
1: 836
2: 798
Vulnerabilities:
Type: itlb_multihit
status: KVM: VMX unsupported
Type: l1tf
mitigation: PTE Inversion
Type: mds
mitigation: Clear CPU buffers; SMT disabled
Type: meltdown
mitigation: PTI
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 generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling
Type: srbds
status: Not affected
Type: tsx_async_abort
status: Not affected
12-01-2021, 12:38 PM
#123
Member
Registered: Jun 2021
Location: Alberta
Distribution: Slackware...mostly
Posts: 328
Quote:
Originally Posted by
h2-1
fourtysixandtwo, thanks so much for firing up these old systems, that type of data is very useful to trap and locate areas where inxi is assuming data will always be one way (like stepping: being an integer, always). That's the first time I've seen 'unknown' in those fields, I'll have to add some filters there I think, I will go in and modify the global filtering tools since I've found a few variations already in this thread's samples that the tools did not handle.
Also reminds me to finalize the output for cache: when nothing is found at all, that should have said:
cache: N/A, not cache: L2: N/A
That's corrected in 3.3.09-21. Stepping: 0 should have been stepping: N/A, or just not showing, that's also fixed, I think.
AMD Athlon XP 1800+ looks good, arch: right, etc.
Intel Pentium 4, the fix for the Data L1 only cache working fine, that's good. Microarchitecture lookup table matches seem to be fairly solid now. Tweaked the arch: to show stepping 1, Netburst Prescott, I'd never found stepping data for the Netburst model Ids.
https://www.cpu-world.com/CPUs/Penti...6PE2800E).html
Celeron (Coppermine) looks like the cache data came from dmidecode, and the speed data probably came from cpuinfo, which means it's all working now in terms of the fallbacks clicking in to fill in missing data.
-----------------------------------------
Glad to help. I'm still trying to get the P90 to a state where it can be tested. It has the soldered on CMOS battery and it's dead so it's already limited bios is completely useless for working around anything. Drive is <300MB (4gb bios limited) and the nic has stopped working as well...it's really putting up a fight! lol
Here's an updated output from the 486.
Code:
# ./pinxi --version | grep ^pinxi
pinxi 3.3.09-22 (2021-11-29)
# ./pinxi -MCazy1
Machine:
Message: No machine data: try newer kernel. Is dmidecode installed? Try -M --dmidecode.
CPU:
Info: Single Core
model: 486
bits: N/A
type: UP
arch: N/A
family: 4
model-id: N/A
microcode: N/A
cache: N/A
flags: N/A
bogomips: N/A
Speed: N/A
min/max: N/A
core: No per core speed data found.
Vulnerabilities: No CPU vulnerability/bugs data available.
12-01-2021, 12:58 PM
#124
Member
Registered: Feb 2020
Location: Brazil
Distribution: Slackware
Posts: 45
Rep:
Old toy...
Code:
$ ./inxi -MCazy
Machine:
Type: Portable System: Dell product: Vostro 3500 v: A12
serial: <superuser required>
Mobo: Dell model: 0PXM4R v: A12 serial: <superuser required> BIOS: Dell
v: A12 date: 04/08/2014
CPU:
Info: Dual Core model: Intel Core i5 M 430 bits: 64 type: MT MCP
arch: Nehalem family: 6 model-id: 25 (37) stepping: 2 microcode: 9 cache:
L1: 128 KiB L2: 512 KiB L3: 4 MiB
flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18088
Speed: 2262 MHz min/max: 1197/2262 MHz boost: enabled Core speeds (MHz):
1: 2262 2: 1729 3: 1729 4: 2262
Vulnerabilities: Type: itlb_multihit status: Processor vulnerable
Type: l1tf mitigation: PTE Inversion
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
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
Code:
$ ./pinxi -MCazy
Machine:
Type: Portable System: Dell product: Vostro 3500 v: A12
serial: <superuser required>
Mobo: Dell model: 0PXM4R v: A12 serial: <superuser required> BIOS: Dell
v: A12 date: 04/08/2014
CPU:
Info: Dual Core model: Intel Core i5 M 430 bits: 64 type: MT MCP
arch: Westmere family: 6 model-id: 25 (37) stepping: 2 microcode: 9 cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 3 MiB desc: 1x3 MiB
flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 4522
Speed (MHz): avg: 1962 high: 2262 min/max: 1197/2262 boost: enabled cores:
1: 1463 2: 2262 3: 2262 4: 1862
Vulnerabilities:
Type: itlb_multihit status: Processor vulnerable
Type: l1tf mitigation: PTE Inversion
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
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
arch and L3 seems different...
12-01-2021, 12:58 PM
#125
Member
Registered: Mar 2018
Distribution: Debian Testing
Posts: 562
Original Poster
MDKDIO, aus9, thanks for showing that the 'microcode' feature has actual utility!! Sometimes I just toss bits of data in 'because they are there', but it's always good to see that it actually can have real implications and value to see that data. Microcode is one I'd always used just because 'it is there', but I never thought about what it could actually mean, or that it could be an important thing in some cases, for security updates etc. Thanks aus9 for pointing that out.
2 members found this post helpful.
12-01-2021, 01:08 PM
#126
Member
Registered: Mar 2018
Distribution: Debian Testing
Posts: 562
Original Poster
carriunix, that Intel Core i5 M 430 is a good example of why I didn't trust the method for L1,2,3 cache inxi 3.3.09 used as a short term fix. First, I didn't know what was generating that data, second, I didn't know if it was real, or just a string value set somewhere in the system, third, it didn't have anyway of indicating how many of each cache type were on the system, so inxi had to still do its guessing game of 1 L1 per core, usually 1 L2 per core, with known exceptions, and 1 L3 per core, which is not a correct assumption either. As you can see, inxi using the provisional method got the wrong data for L3, which means that data did not come from the actual CPU, which was my strong suspicion.
Note that the methods now in pinxi were my 3rd attempt, the second was such a horrifyingly bad idea that I'll keep it too myself, but I did actually start that, then quickly realized that was the path to insanity and horror, a nefandous realm which no sane person should want to enter.
https://www.cpu-world.com/CPUs/Core_...7004161AD.html
Microarchitecture Westmere
Level 1 cache size ? 2 x 32 KB 4-way set associative instruction caches
2 x 32 KB 8-way set associative data caches
Level 2 cache size ? 2 x 256 KB 8-way set associative caches
Level 3 cache size 3 MB 12-way set associative shared cache
I'm actually curious, if you run on that system (root or sudo so dmidecode can run):
Code:
pinxi -Ca --dmidecode
What is the cache data then?
I've also had a suspicion that the dmidecode cpu cache data may not be completely accurate in all cases, though it appears to be generally right.
Last edited by h2-1; 12-01-2021 at 01:10 PM .
12-01-2021, 07:20 PM
#127
Member
Registered: Nov 2018
Distribution: Slackware
Posts: 797
Here's a range of machines from oldest to newest, tested with 'inxi 3.3.06-00' and 'pinxi 3.3.09-22' respectively. It's mostly Intel CPUs, with one ARM.
Probably most of these are non interesting but let me know if you need anything else.
Code:
./inxi -MCazy
Machine:
Type: Desktop Mobo: ASUSTeK model: P5K-VM v: Rev 1.xx serial: <filter>
BIOS: American Megatrends v: 0704 date: 01/18/2008
CPU:
Info: Quad Core model: Intel Core2 Quad Q6600 bits: 64 type: MCP
arch: Core Merom family: 6 model-id: F (15) stepping: B (11) microcode: B6
cache: L2: 4 MiB
flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 19199
Speed: 1601 MHz min/max: 1596/2394 MHz Core speeds (MHz): 1: 1601 2: 2193
3: 1600 4: 1600
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled
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
./pinxi -MCazy1
Machine:
Type: Desktop
Mobo: ASUSTeK
model: P5K-VM
v: Rev 1.xx
serial: <superuser required>
BIOS: American Megatrends
v: 0704
date: 01/18/2008
CPU:
Info: Quad Core
model: Intel Core2 Quad Q6600
bits: 64
type: MCP
arch: Core Merom
family: 6
model-id: F (15)
stepping: B (11)
microcode: B6
cache:
L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB
L2: 8 MiB
desc: 2x4 MiB
flags: ht lm nx pae sse sse2 sse3 ssse3 vmx
bogomips: 4799
Speed (MHz):
avg: 2017
high: 2377
min/max: 1596/2394
cores:
1: 2377
2: 1981
3: 1921
4: 1790
Vulnerabilities:
Type: itlb_multihit
status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: EPT disabled
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
Code:
./inxi -MCazy
Machine:
Type: Laptop System: ASUSTeK product: 1000H v: x.x serial: <filter>
Chassis: ASUSTek Computer INC. type: 10 v: x.x serial: <filter>
Mobo: ASUSTeK model: 1000H v: x.xx serial: <filter>
BIOS: American Megatrends v: 2204 date: 10/21/2009
CPU:
Info: Single Core model: Intel Atom N270 bits: 32 type: UP arch: Bonnell
family: 6 model-id: 1C (28) stepping: 2 microcode: 212 cache: L2: 512 KiB
flags: nx pae sse sse2 sse3 ssse3 bogomips: 3191
Speed: 798 MHz min/max: 800/1600 MHz Core speed (MHz): 1: 798
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 status: Not affected
Type: spectre_v2 status: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
./pinxi -MCazy1
Machine:
Type: Laptop
System: ASUSTeK
product: 1000H
v: x.x
serial: <superuser required>
Chassis: ASUSTek Computer INC.
type: 10
v: x.x
serial: <superuser required>
Mobo: ASUSTeK
model: 1000H
v: x.xx
serial: <superuser required>
BIOS: American Megatrends
v: 2204
date: 10/21/2009
CPU:
Info: Single Core
model: Intel Atom N270
bits: 32
type: MCP
arch: Bonnell
family: 6
model-id: 1C (28)
stepping: 2
microcode: 212
cache:
L1: 56 KiB
desc: d-1x24 KiB; i-1x32 KiB
L2: 512 KiB
desc: 1x512 KiB
flags: ht nx pae sse sse2 sse3 ssse3
bogomips: 3191
Speed (MHz): 831
min/max: 800/1600
core:
1: 831
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
status: Not affected
Type: spectre_v2
status: Not affected
Type: srbds
status: Not affected
Type: tsx_async_abort
status: Not affected
Code:
./inxi -MCazy
Machine:
Type: Laptop System: Apple product: MacBookPro8,2 v: 1.0 serial: <filter>
Chassis: type: 10 v: Mac-94245A3940C91C80 serial: <filter>
Mobo: Apple model: Mac-94245A3940C91C80 v: MacBookPro8,2 serial: <filter>
UEFI: Apple v: MBP81.88Z.0047.B2C.1510261540 date: 10/26/15
CPU:
Info: Quad Core model: Intel Core i7-2720QM bits: 64 type: MT MCP
arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 1A
cache: L2: 6 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 35200
Speed: 2332 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 2332 2: 1692
3: 2277 4: 2998 5: 3051 6: 3210 7: 1982 8: 2844
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
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
./pinxi -MCazy1
Machine:
Type: Laptop
System: Apple
product: MacBookPro8,2
v: 1.0
serial: <superuser required>
Chassis:
type: 10
v: Mac-94245A3940C91C80
serial: <superuser required>
Mobo: Apple
model: Mac-94245A3940C91C80
v: MacBookPro8,2
serial: <superuser required>
UEFI: Apple
v: MBP81.88Z.0047.B2C.1510261540
date: 10/26/15
CPU:
Info: Quad Core
model: Intel Core i7-2720QM
bits: 64
type: MT MCP
arch: Sandy Bridge
family: 6
model-id: 2A (42)
stepping: 7
microcode: 1A
cache:
L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB
L2: 1024 KiB
desc: 4x256 KiB
L3: 6 MiB
desc: 1x6 MiB
flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 4400
Speed (MHz):
avg: 2965
high: 3266
min/max: 800/3300
cores:
1: 1885
2: 2892
3: 3205
4: 3266
5: 3257
6: 3030
7: 3076
8: 3112
Vulnerabilities:
Type: itlb_multihit
status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
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
Code:
./inxi -MCazy
Machine:
Type: Laptop System: Dell product: XPS 13 9350 v: N/A serial: <filter>
Chassis: type: 9 serial: <filter>
Mobo: Dell model: 07TYC2 v: A01 serial: <filter> UEFI: Dell v: 1.9.0
date: 08/31/2018
CPU:
Info: Dual Core model: Intel Core i5-6200U bits: 64 type: MT MCP
arch: Skylake family: 6 model-id: 4E (78) stepping: 3 microcode: C6 cache:
L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 19200
Speed: 2701 MHz min/max: 400/2800 MHz Core speeds (MHz): 1: 2701 2: 2795
3: 2755 4: 2759
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
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 generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
./pinxi -MCazy1
Machine:
Type: Laptop
System: Dell
product: XPS 13 9350
v: N/A
serial: <superuser required>
Chassis:
type: 9
serial: <superuser required>
Mobo: Dell
model: 07TYC2
v: A01
serial: <superuser required>
UEFI: Dell
v: 1.9.0
date: 08/31/2018
CPU:
Info: Dual Core
model: Intel Core i5-6200U
bits: 64
type: MT MCP
arch: Skylake
family: 6
model-id: 4E (78)
stepping: 3
microcode: C6
cache:
L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB
desc: 2x256 KiB
L3: 3 MiB
desc: 1x3 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 4800
Speed (MHz):
avg: 2762
high: 2792
min/max: 400/2800
cores:
1: 2782
2: 2763
3: 2792
4: 2712
Vulnerabilities:
Type: itlb_multihit
status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown
mitigation: PTI
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 generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds
status: Vulnerable: No microcode
Type: tsx_async_abort
status: Not affected
Code:
./inxi -MCazy
Machine:
Type: ARM Device System: Pine64 RockPro64 v2.1 details: N/A serial: <filter>
CPU:
Info: 6-Core (2-Die) model: N/A variant-1: cortex-a53 variant-2: cortex-a72
bits: 64 type: MCP MCM arch: ARMv8 family: 8 model-id: 0 stepping: 4
features: Use -f option to see features bogomips: 0
Speed: 408 MHz min/max: 408/1512:2016 MHz Core speeds (MHz): 1: 408 2: 408
3: 408 4: 408 5: 408 6: 408
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: __user pointer sanitization
Type: spectre_v2 mitigation: Branch predictor hardening
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
./pinxi -MCazy1
Machine:
Type: ARM
System: Pine64 RockPro64 v2.1
details: N/A
serial: <filter>
CPU:
Info: 2x Quad Core
model: N/A
variant-1: cortex-a53
variant-2: cortex-a72
bits: 64
type: MCP SMP
arch: ARMv8
family: 8
model-id: 0
stepping: 4
features: Use -f option to see features
bogomips: N/A
Speed (MHz):
avg: 408
min/max: 408/1512:2016
cores:
1: 408
2: 408
3: 408
4: 408
5: 408
6: 408
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: __user pointer sanitization
Type: spectre_v2
mitigation: Branch predictor hardening
Type: srbds
status: Not affected
Type: tsx_async_abort
status: Not affected
Code:
./inxi -MCazy
Machine:
Type: Desktop System: LENOVO product: 90NC00J9US v: Legion T5 28IMB05
serial: <filter> Chassis: type: 3 serial: <filter>
Mobo: LENOVO model: 3717 v: SDK0R32862 WIN 3258192669537 serial: <filter>
UEFI: LENOVO v: O4NKT16A date: 09/03/2020
CPU:
Info: 8-Core model: Intel Core i7-10700 bits: 64 type: MT MCP
arch: Comet Lake family: 6 model-id: A5 (165) stepping: 5 microcode: C8
cache: L2: 16 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 92796
Speed: 4699 MHz min/max: 800/4800 MHz Core speeds (MHz): 1: 4699 2: 4696
3: 4630 4: 4639 5: 4700 6: 4697 7: 4710 8: 1521 9: 4701 10: 1365 11: 1154
12: 4700 13: 4701 14: 4706 15: 1369 16: 4699
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 status: Not affected
Type: tsx_async_abort status: Not affected
./pinxi -MCazy1
Machine:
Type: Desktop
System: LENOVO
product: 90NC00J9US
v: Legion T5 28IMB05
serial: <superuser required>
Chassis:
type: 3
serial: <superuser required>
Mobo: LENOVO
model: 3717
v: SDK0R32862 WIN 3258192669537
serial: <superuser required>
UEFI: LENOVO
v: O4NKT16A
date: 09/03/2020
CPU:
Info: 8-Core
model: Intel Core i7-10700
bits: 64
type: MT MCP
arch: Comet Lake
family: 6
model-id: A5 (165)
stepping: 5
microcode: C8
cache:
L1: 512 KiB
desc: d-8x32 KiB; i-8x32 KiB
L2: 2 MiB
desc: 8x256 KiB
L3: 16 MiB
desc: 1x16 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 5799
Speed (MHz):
avg: 4680
high: 4779
min/max: 800/4800
cores:
1: 4700
2: 4700
3: 4699
4: 4698
5: 4701
6: 4700
7: 4698
8: 4397
9: 4700
10: 4699
11: 4694
12: 4700
13: 4673
14: 4646
15: 4779
16: 4698
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
status: Not affected
Type: tsx_async_abort
status: Not affected
2 members found this post helpful.
12-01-2021, 07:43 PM
#128
Senior Member
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,987
Hope my
post 103 was useful. I have a Acer laptop I use for work (volunteer work, all work, no pay LOL). Since it's home for an upgraded, here is its pinxi output.
Code:
root@post4:~# ./pinxi --version | grep ^pinxi
pinxi 3.3.09-22 (2021-11-29)
root@post4:~# ./pinxi -MCazy
Machine:
Type: Laptop System: Acer product: Aspire E5-475 v: V1.19 serial: <filter>
Mobo: Acer model: AntMan_SK v: V1.19 serial: <filter> UEFI-[Legacy]: Insyde
v: 1.19 date: 09/22/2017
CPU:
Info: Dual Core model: Intel Core i3-7130U socket: U3E1 bits: 64
type: MT MCP arch: Amber/Kaby Lake note: check family: 6 model-id: 8E (142)
stepping: 9 microcode: 62 cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 5399
Speed (MHz): avg: 2700 min/max: 400/2700 base/boost: 2700/8300 volts: 0.9 V
ext-clock: 100 MHz cores: 1: 2700 2: 2700 3: 2700 4: 2700
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
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: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
Last edited by chrisretusn; 12-01-2021 at 07:44 PM .
12-01-2021, 08:02 PM
#129
Member
Registered: Mar 2018
Distribution: Debian Testing
Posts: 562
Original Poster
0XBF, there was a hack I couldn't remember what it was for, re AMD, that I'd bypassed in the new logic, but your pine64 system is what it was for, now I remember, basically those ARM cpus identify as having 2 cpus, not 2 dies, but they can have different topology per cpu type.
Can you upload:
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
to pastebin.com or somewhere, that will let me emulate that to figure out a way to better show the cpu layout.
Technically I think the original logic was better in terms of more intuitive, but the new logic fails to handle the case where each 'cpu' has different count of cores. At least I think that's what is going on.
With that data, I should be able to wrap up that corner case, which I was slightly aware of, I'd actually also noticed that testing on my phone, android/termux, it has a similar type cpu with 2 different types of cores, only mine had 4 cores each so the results were ok.
I might have to make the actual logic more granular, and simply note how many cores each 'cpu' has, I think this one is probably the biggest corner case left.
The other data I'll take a look at, trying to get some stuff worked out in pinxi at the moment, cleaning up looseends, but that arm one is significant. I can test that on my phone too, but not as well as with your system.
Thanks
12-01-2021, 09:36 PM
#130
Member
Registered: Mar 2018
Distribution: Debian Testing
Posts: 562
Original Poster
0XBF, I have to rewrite some of the core logic for this one, this is one I tried taking a shortcut with, didn't work. Have to make it fully able to handle any possible cpu/cpus topology, regardless.
1 members found this post helpful.
12-02-2021, 12:09 AM
#131
Member
Registered: Mar 2018
Distribution: Debian Testing
Posts: 562
Original Poster
pinxi 3.3.09-23 should hopefully have complicated cases like the pine64 above handled. That required a rewrite to fully dynamic cpu topology, I'd been trying to skip a few steps, but didn't work.
Seems to work:
Code:
CPU:
Info: 1x 2-Core, 1x 4-Core model: AArch64 bits: 64 type: SMP arch: aarch64
family: 8 model-id: A (10) stepping: 4
features: Use -f option to see features bogomips: N/A
Speed (MHz): avg: 1222 high: 1306 min/max: 300/1805:2016 cores: 1: 1306
2: 1306 3: 1306 4: 1306 5: 1056 6: 1056
This cpu Info: item will put out more complete topology data than before when it hits complicated situations, but will look fairly similar when it's a normal cpu.
Code:
pinxi -Ca
CPU:
Info: 6-Core (12-threads) model: AMD Ryzen 5 2600 bits: 64 type: MT MCP
arch: Zen+ family: 17 (23) model-id: 8 stepping: 2 microcode: 8008204
cache: L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB
L3: 16 MiB desc: 2x8 MiB
Code:
pinxi -Ca
CPU:
Info: 2x 16-Core (32-threads, 4-die) model: AMD EPYC 7281 bits: 64
type: MT MCP MCM SMP arch: Zen family: 17 (23) model-id: 1 stepping: 2
microcode: 8001250 cache: L1: 2x 1.5 MiB (3 MiB)
desc: d-16x32 KiB; i-16x64 KiB L2: 2x 8 MiB (16 MiB) desc: 16x512 KiB
L3: 2x 32 MiB (64 MiB) desc: 8x4 MiB
Code:
pinxi -C
CPU:
Info: 6-Core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP cache:
L2: 3 MiB
Last edited by h2-1; 12-02-2021 at 12:21 AM .
12-02-2021, 01:56 AM
#132
Senior Member
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 15.0 + Multilib
Posts: 2,159
h2-1 --
Slackware 15.0 on my new Laptop.
CPU: Intel Core i9-11900K
No additional microcode installed yet.
sdiff-src output of pinxi -vs- /usr/bin/inxi ( very wide lines below ! )
Looks good here.
Thanks for all your work !
-- kjh
Code:
# Diff Search = ' [\|] | < *$| > | > *$' # ( exclude leading and trailing ' )
# Wide Lines = ' [|] | < *$| > | > *$'
# Working Dir = /dld/15.0/pinixi
# #
# Command = /usr/bin/inxi --version | grep '^inxi \|pinxi ' -A10 # Command = /dld/15.0/pinxi/pinxi --version | grep '^inxi \|pinxi ' -A10
# #
inxi 3.3.06-00 (2021-07-21) | pinxi 3.3.09-24 (2021-12-01)
Copyright (C) 2008-2021 Harald Hope aka h2 Copyright (C) 2008-2021 Harald Hope aka h2
Forked from Infobash 3.02: Copyright (C) 2005-2007 Michiel de Boer aka locsmif. | Forked from Infobash 3.02:
> Copyright (C) 2005-2007 Michiel de Boer aka locsmif.
Using Perl version: 5.034000 Using Perl version: 5.034000
Program Location: /usr/bin | Program Location: /dld/15.0/pinixi
Website: https://github.com/smxi/inxi or https://smxi.org/ Website: https://github.com/smxi/inxi or https://smxi.org/
IRC: irc.oftc.net channel: #smxi IRC: irc.oftc.net channel: #smxi
Forums: https://techpatterns.com/forums/forum-33.html Forums: https://techpatterns.com/forums/forum-33.html
# ------------------------------------------------------------------------------- # ------------------------------------------------------------------------------
# Command = /usr/bin/inxi -MCazy |tee /tmp/inxi-MCazy.out # Command = /dld/15.0/pinixi/pinxi -MCazy |tee /tmp/pinxi-MCazy.out
# File = /tmp/inxi-MCazy.out # File = /tmp/pinxi-MCazy.out
# #
Machine: Machine:
Type: Laptop System: Notebook product: X170KM-G v: N/A serial: N/A Chassis: Type: Laptop System: Notebook product: X170KM-G v: N/A serial: N/A Chassis:
type: 10 serial: N/A type: 10 serial: N/A
Mobo: Notebook model: X170KM-G serial: N/A UEFI: INSYDE v: 1.07.06LS1 Mobo: Notebook model: X170KM-G serial: N/A UEFI: INSYDE v: 1.07.06LS1
date: 01/11/2020 date: 01/11/2020
CPU: CPU:
Info: 8-Core model: 11th Gen Intel Core i9-11900K socket: U3E1 bits: 64 | Info: 8-Core (16-threads) model: 11th Gen Intel Core i9-11900K socket: U3E1
type: MT MCP arch: Rocket Lake family: 6 model-id: A7 (167) stepping: 1 | bits: 64 type: MT MCP arch: Rocket Lake family: 6 model-id: A7 (167)
microcode: 40 cache: L2: 16 MiB | stepping: 1 microcode: 40 cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx | L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
bogomips: 112128 | flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Speed: 5112 MHz min/max: 800/5100 MHz base/boost: 3366/8500 volts: 0.9 V | bogomips: 7008
ext-clock: 100 MHz Core speeds (MHz): 1: 5112 2: 5112 3: 5114 4: 5111 | Speed (MHz): avg: 4597 high: 5312 min/max: 800/5100:5300
5: 5107 6: 5300 7: 5124 8: 5112 9: 4879 10: 5102 11: 1037 12: 5124 13: 3762 | base/boost: 3366/8500 volts: 0.9 V ext-clock: 100 MHz cores: 1: 2817 2: 5108
14: 3291 15: 5103 16: 4973 | 3: 5112 4: 5105 5: 962 6: 5312 7: 5112 8: 2845 9: 5112 10: 5101 11: 5100
Vulnerabilities: Type: itlb_multihit status: Not affected | 12: 5111 13: 5303 14: 5220 15: 5124 16: 5111
> Vulnerabilities:
> Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected Type: l1tf status: Not affected
Type: mds status: Not affected Type: mds status: Not affected
Type: meltdown status: Not affected Type: meltdown status: Not affected
Type: spec_store_bypass Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected Type: tsx_async_abort status: Not affected
Last edited by kjhambrick; 12-02-2021 at 01:57 AM .
Reason: fix h2-1 handle
12-02-2021, 02:00 AM
#133
Senior Member
Registered: Nov 2008
Location: USA
Distribution: Slackware, FreeBSD, Illumos, NetBSD, DragonflyBSD, Plan9, Inferno, OpenBSD, FreeDOS, HURD
Posts: 1,075
Rep:
Code:
root@9.cosmos:~# inxi -MCazy
Machine:
Type: Desktop Mobo: BIOSTAR model: X470GTA serial: N/A
BIOS: American Megatrends LLC. v: 5.17 date: 06/16/2021
CPU:
Info: 16-Core model: AMD Ryzen 9 5950X socket: AM4 bits: 64 type: MT MCP
arch: Zen 3 family: 19 (25) model-id: 21 (33) stepping: 0 microcode: A201016
cache: L1: 1024 KiB L2: 8 MiB L3: 64 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 217178
Speed: 4462 MHz min/max: 2200/3400 MHz base/boost: 3400/5050 boost: enabled
volts: 1.1 V ext-clock: 100 MHz Core speeds (MHz): 1: 4476 2: 4476 3: 4476
4: 4476 5: 4476 6: 4476 7: 4476 8: 4476 9: 4476 10: 4476 11: 4476 12: 4476
13: 4476 14: 4476 15: 4476 16: 4476 17: 4476 18: 4476 19: 4470 20: 4469
21: 4469 22: 4465 23: 4475 24: 4476 25: 4474 26: 4482 27: 4476 28: 4476
29: 4476 30: 4476 31: 4476 32: 4479
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
Code:
root@vanaheim:~# inxi -MCazy
Machine:
Type: Desktop Mobo: Gigabyte model: A520I AC serial: N/A
BIOS: American Megatrends LLC. v: F14e date: 10/13/2021
CPU:
Info: 16-Core (2-Die) model: AMD Ryzen 9 3950X socket: AM4 bits: 64
type: MT MCP MCM arch: Zen 2 family: 17 (23) model-id: 71 (113) stepping: 0
microcode: 8701021 cache: L1: 1024 KiB L2: 8 MiB L3: 64 MiB
flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 223997
Speed: 3844 MHz min/max: 2200/3500 MHz base/boost: 3500/4725 boost: enabled
volts: 1.1 V ext-clock: 100 MHz Core speeds (MHz): 1: 3868 2: 3868 3: 3868
4: 3868 5: 3867 6: 3867 7: 3867 8: 3867 9: 3868 10: 3868 11: 3868 12: 3868
13: 3868 14: 3867 15: 3867 16: 3867 17: 3867 18: 3868 19: 3868 20: 3868
21: 3868 22: 3867 23: 3867 24: 3867 25: 3867 26: 3882 27: 3867 28: 3867
29: 3867 30: 3867 31: 3867 32: 3871
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
Code:
root@darwinheim:~# inxi -MCazy
Machine:
Type: ARM Device System: Raspberry Pi 4 Model B Rev 1.4 details: BCM2711
rev: d03114 serial: <filter>
CPU:
Info: Quad Core model: ARMv7 v7l variant: cortex-a72 bits: 32 type: MCP
arch: v7l family: 7 model-id: 0 stepping: 3
features: Use -f option to see features bogomips: 1080
Speed: 1500 MHz min/max: 600/1500 MHz Core speeds (MHz): 1: 1500 2: 1500
3: 1500 4: 1500
Vulnerabilities: No CPU vulnerability/bugs data available.
Code:
root@darkelfheim:~# inxi -MCazy
Machine:
Type: ARM Device System: Raspberry Pi 3 Model B Rev 1.2 details: BCM2835
rev: a52082 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
features: Use -f option to see features bogomips: 307
Speed: 1200 MHz min/max: 600/1200 MHz Core speeds (MHz): 1: 1200 2: 1200
3: 1200 4: 1200
Vulnerabilities: No CPU vulnerability/bugs data available.
Code:
root@elfheim:~# inxi -MCazy
Machine:
Type: Desktop System: To be Filled product: To be Filled v: To be Filled
serial: <filter> Chassis: type: 3 v: To be Filled serial: <filter>
Mobo: Supermicro model: Intel 440BX/440GX v: Rev. 1 serial: <filter>
BIOS: American Megatrends v: 063100 date: 01/15/99
CPU:
Info: Single Core model: Pentium III (Coppermine) socket: LIF Socket (J203)
note: check bits: 32 type: MT arch: P6 III Coppermine family: 6 model-id: 8
stepping: 3 microcode: C cache: L1: 16 KiB L2: 256 KiB
flags: pae sse bogomips: 3207
Speed: 802 MHz min/max: N/A base/boost: 800/200 volts: 1.8 V
ext-clock: 100 MHz Core speeds (MHz): 1: 802 2: 802
Vulnerabilities: No CPU vulnerability/bugs data available.
I have some other Intel ones also, but some have vulnerabilities (even one with LibreBoot) so I'm wondering what I should do...
Last edited by dchmelik; 12-02-2021 at 02:09 AM .
12-02-2021, 09:50 AM
#134
Member
Registered: Nov 2018
Distribution: Slackware
Posts: 797
Edit: This just applies to the pine64
I updated pinxi with "./pinxi -U" this morning and it updated to version '3.3.09-24'.
Running './pinxi -Mcazy1' returns an error now:
Code:
Undefined subroutine &CpuItem::cpuinfo_grabber called at ./pinxi line 14394.
I also ran the './pinxi -Ca' command, which gave the following output:
Code:
CPU:
Info: 1x 2-Core, 1x 4-Core model: N/A variant-1: cortex-a53
variant-2: cortex-a72 bits: 64 type: SMP arch: ARMv8 family: 8 model-id: 0
stepping: 4
features: Use -f option to see features bogomips: N/A
Speed (MHz): avg: 408 min/max: 408/1512:2016 cores: 1: 408 2: 408 3: 408
4: 408 5: 408 6: 408
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: __user pointer sanitization
Type: spectre_v2 mitigation: Branch predictor hardening
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
I attached the cpuinfo data that you wanted as well.
Last edited by 0XBF; 12-02-2021 at 09:52 AM .
12-02-2021, 10:25 AM
#135
Member
Registered: Apr 2005
Location: Oklahoma, USA
Distribution: Slackware
Posts: 907
Quote:
Originally Posted by
0XBF
Edit: This just applies to the pine64
I updated pinxi with "./pinxi -U" this morning and it updated to version '3.3.09-24'.
Running './pinxi -Mcazy1' returns an error now:
Code:
Undefined subroutine &CpuItem::cpuinfo_grabber called at ./pinxi line 14394.
I don't know perl, but try this:
On line 14394 try changing "CpuItem::cpuinfo_grabber" to "cpuinfo_data_grabber" to see if it will work.
The other option is hs-1 forgot to include the subroutine "cpuinfo_grabber" in the CpuItem package (starting on line 8223), in which case you'll just have to wait for another update.
All times are GMT -5. The time now is 09:28 PM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News