LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-28-2021, 07:59 AM   #61
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,371

Rep: Reputation: 2748Reputation: 2748Reputation: 2748Reputation: 2748Reputation: 2748Reputation: 2748Reputation: 2748Reputation: 2748Reputation: 2748Reputation: 2748Reputation: 2748

And now Methusela
Code:
# inxi -MCazy
Machine:
  Type: Desktop System: Dell product: Dell DM061 v: N/A serial: <filter> 
  Chassis: type: 6 serial: <filter> 
  Mobo: Dell model: 0WG864 serial: <filter> BIOS: Dell v: 2.4.0 
  date: 05/24/2007 
CPU:
  Info: Dual Core model: Intel Core2 6300 socket: Microprocessor bits: 64 
  type: MCP arch: Core Merom family: 6 model-id: F (15) stepping: 6 
  microcode: C6 cache: L1: 32 KiB L2: 2 MiB 
  flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 7447 
  Speed: 1862 MHz min/max: N/A base/boost: 1866/5200 volts: 1.8 V 
  ext-clock: 1066 MHz Core speeds (MHz): 1: 1862 2: 1596 
  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
  System: Dell
    product: Dell DM061
    v: N/A
    serial: <filter>
  Chassis:
    type: 6
    serial: <filter>
  Mobo: Dell
    model: 0WG864
    serial: <filter>
  BIOS: Dell
    v: 2.4.0
    date: 05/24/2007

CPU:
  Info: Dual Core
    model: Intel Core2 6300
    socket: Microprocessor
    bits: 64
    type: MCP
    arch: Core Merom
    family: 6
    model-id: F (15)
    stepping: 6
    microcode: C6
    cache:
      L1: 128 KiB
        desc: d-2x32 KiB; i-2x32 KiB
      L2: 2 MiB
        desc: 1x2 MiB
    flags: ht lm nx pae sse sse2 sse3 ssse3 vmx
    bogomips: 3723
  Speed (MHz):
    avg: 1729
    high: 1862
    min/max: N/A
    base/boost: 1866/5200
    volts: 1.8 V
    ext-clock: 1066 MHz
    cores:
      1: 1596
      2: 1862
  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 --version
pinxi 3.3.09-10 (2021-11-26)

Last edited by allend; 11-28-2021 at 08:01 AM.
 
Old 11-28-2021, 08:22 AM   #62
FTIO
Member
 
Registered: Mar 2015
Location: Las Vegas, NV
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618

Rep: Reputation: 359Reputation: 359Reputation: 359Reputation: 359
Here's mine, if it's of any help at all...

Code:
inxi -MCazy
Machine:
  Type: Desktop System: Micro-Star product: MS-7C35 v: 2.0
  serial: <superuser required>
  Mobo: Micro-Star model: MEG X570 UNIFY (MS-7C35) v: 2.0
  serial: <superuser required> UEFI: American Megatrends LLC. v: A.90
  date: 05/17/2021
CPU:
  Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2
  family: 17 (23) model-id: 71 (113) stepping: 0 microcode: 8701021 cache:
  L1: 512 KiB L2: 4 MiB L3: 32 MiB
  flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 115204
  Speed: 4197 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz):
  1: 4197 2: 4199 3: 4216 4: 4168 5: 4124 6: 4178 7: 4184 8: 4177 9: 4182
  10: 4178 11: 4172 12: 4152 13: 3927 14: 4192 15: 4196 16: 4202
  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
 
Old 11-28-2021, 10:24 AM   #63
JayByrd
Member
 
Registered: Aug 2021
Location: Seattle, WA
Distribution: Slackware
Posts: 300

Rep: Reputation: 309Reputation: 309Reputation: 309Reputation: 309
An HP laptop from 2014:

Code:
mikebig@BOINC6:~$ inxi --version | grep ^inxi
inxi 3.3.09-00 (2021-11-22)
mikebig@BOINC6:~$ inxi -MCazy
Machine:
  Type: Laptop System: Hewlett-Packard product: HP Pavilion TS 15 Notebook PC
  v: 0974110002405E00000620180 serial: <superuser required> Chassis: type: 10
  serial: <superuser required>
  Mobo: Hewlett-Packard model: 216B v: 30.25 serial: <superuser required>
  UEFI: Insyde v: F.15 date: 06/03/2014
CPU:
  Info: Quad Core model: AMD A8-4555M APU with Radeon HD Graphics bits: 64
  type: MCP arch: Piledriver family: 15 (21) model-id: 10 (16) stepping: 1
  microcode: 6001119 cache: L1: 320 KiB L2: 8 MiB
  flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 12776
  Speed: 1600 MHz min/max: 1100/1600 MHz boost: enabled Core speeds (MHz):
  1: 1600 2: 1600 3: 1600 4: 1600
  Vulnerabilities: No CPU vulnerability/bugs data available.

mikebig@BOINC6:~$ ./pinxi --version | grep ^pinxi
pinxi 3.3.09-10 (2021-11-26)
mikebig@BOINC6:~$ ./pinxi -MCazy1
Machine:
  Type: Laptop
  System: Hewlett-Packard
    product: HP Pavilion TS 15 Notebook PC
    v: 0974110002405E00000620180
    serial: <superuser required>
  Chassis:
    type: 10
    serial: <superuser required>
  Mobo: Hewlett-Packard
    model: 216B
    v: 30.25
    serial: <superuser required>
  UEFI: Insyde
    v: F.15
    date: 06/03/2014

CPU:
  Info: Quad Core
    model: AMD A8-4555M APU with Radeon HD Graphics
    bits: 64
    type: MCP
    arch: Piledriver
    family: 15 (21)
    model-id: 10 (16)
    stepping: 1
    microcode: 6001119
    cache:
      L1: 192 KiB
        desc: d-4x16 KiB; i-2x64 KiB
      L2: 4 MiB
        desc: 2x2 MiB
    flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 3194
  Speed (MHz):
    avg: 1600
    min/max: 1100/1600
    boost: enabled
    cores:
      1: 1600
      2: 1600
      3: 1600
      4: 1600
  Vulnerabilities: No CPU vulnerability/bugs data available.
 
Old 11-28-2021, 10:43 AM   #64
JayByrd
Member
 
Registered: Aug 2021
Location: Seattle, WA
Distribution: Slackware
Posts: 300

Rep: Reputation: 309Reputation: 309Reputation: 309Reputation: 309
This one looks good--no discrepancies on cache reporting:

Code:
steph@claire-pc:~/tmp$ inxi --version | grep ^inxi
inxi 3.3.09-00 (2021-11-22)
steph@claire-pc:~/tmp$ inxi -MCazy
Machine:
  Type: Desktop System: Dell product: Dell DM061 v: N/A
  serial: <superuser required> Chassis: type: 6 serial: <superuser required>
  Mobo: Dell model: 0WG864 serial: <superuser required> BIOS: Dell v: 2.4.0
  date: 05/24/2007
CPU:
  Info: Dual Core model: Intel Pentium D bits: 64 type: MCP
  arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 7
  microcode: 3 cache: L1: 32 KiB L2: 2 MiB
  flags: ht lm nx pae sse sse2 sse3 bogomips: 11171
  Speed: 2793 MHz min/max: N/A Core speeds (MHz): 1: 2793 2: 2793
  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 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

steph@claire-pc:~/tmp$ ./pinxi --version | grep ^pinxi
pinxi 3.3.09-10 (2021-11-26)
steph@claire-pc:~/tmp$ ./pinxi -MCazy1
Machine:
  Type: Desktop
  System: Dell
    product: Dell DM061
    v: N/A
    serial: <superuser required>
  Chassis:
    type: 6
    serial: <superuser required>
  Mobo: Dell
    model: 0WG864
    serial: <superuser required>
  BIOS: Dell
    v: 2.4.0
    date: 05/24/2007

Use of uninitialized value in concatenation (.) or string at ./pinxi line 8303.
CPU:
  Info: Dual Core
    model: Intel Pentium D
    bits: 64
    type: MCP
    arch: Netburst Smithfield
    family: F (15)
    model-id: 4
    stepping: 7
    microcode: 3
    cache:
      L1: 32 KiB
        desc: d-2x16 KiB; i-
      L2: 2 MiB
        desc: 2x1024 KiB
    flags: ht lm nx pae sse sse2 sse3
    bogomips: 5585
  Speed (MHz):
    avg: 2793
    min/max: N/A
    cores:
      1: 2793
      2: 2793
  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
      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
OK, I'll stop now.
I do have four more Slackboxes (all Intel) I could post if you need/want more.

Last edited by JayByrd; 11-28-2021 at 10:45 AM.
 
Old 11-28-2021, 11:10 AM   #65
JayByrd
Member
 
Registered: Aug 2021
Location: Seattle, WA
Distribution: Slackware
Posts: 300

Rep: Reputation: 309Reputation: 309Reputation: 309Reputation: 309
I know I said I'd stop, but I found another one with L2 cache discrepancy:

Code:
who@precision:~/tmp/inxi$inxi --version | grep ^inxi
inxi 3.3.09-00 (2021-11-22)
who@precision:~/tmp/inxi$inxi -MCazy
Machine:
  Type: Desktop System: Dell product: Precision WorkStation 490 v: N/A
  serial: <superuser required> Chassis: type: 7 serial: <superuser required>
  Mobo: Dell model: 0GU083 v: A00 serial: <superuser required> BIOS: Dell
  v: A08 date: 04/25/2008
CPU:
  Info: 2x Dual Core model: Intel Xeon 5160 bits: 64 type: SMP
  arch: Core Merom family: 6 model-id: F (15) stepping: B (11) microcode: BC
  cache: L1: 2x 128 KiB (256 KiB) L2: 2x 8 MiB (16 MiB)
  flags: ht lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 23938
  Speed: 2992 MHz min/max: N/A Core speeds (MHz): 1: 2992 2: 2992 3: 2992
  4: 2992
  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 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


who@precision:~/tmp/inxi$./pinxi --version | grep ^pinxi
pinxi 3.3.09-10 (2021-11-26)
who@precision:~/tmp/inxi$./pinxi -MCazy1
Machine:
  Type: Desktop
  System: Dell
    product: Precision WorkStation 490
    v: N/A
    serial: <superuser required>
  Chassis:
    type: 7
    serial: <superuser required>
  Mobo: Dell
    model: 0GU083
    v: A00
    serial: <superuser required>
  BIOS: Dell
    v: A08
    date: 04/25/2008

CPU:
  Info: 2x Dual Core
    model: Intel Xeon 5160
    bits: 64
    type: SMP
    arch: Core Merom
    family: 6
    model-id: F (15)
    stepping: B (11)
    microcode: BC
    cache:
      L1: 2x 128 KiB (256 KiB)
        desc: d-2x32 KiB; i-2x32 KiB
      L2: 2x 4 MiB (8 MiB)
        desc: 1x4 MiB
    flags: ht lm nx pae sse sse2 sse3 ssse3 vmx
    bogomips: 5984
  Speed (MHz):
    avg: 2992
    min/max: N/A
    cores:
      1: 2992
      2: 2992
      3: 2992
      4: 2992
  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
      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

Last edited by JayByrd; 11-28-2021 at 11:12 AM.
 
Old 11-28-2021, 11:15 AM   #66
baumei
Member
 
Registered: Feb 2019
Location: USA; North Carolina
Distribution: Slackware 15.0 (replacing 14.2)
Posts: 365

Rep: Reputation: 124Reputation: 124
Since I read that "inxi" is a script, and I saw the filename said "noarch", I guessed it might also run just fine in Slackware 14.2. So, I used installpkg to install inxi, and inxi seems to have run properly. :-)

This laptop was probably made in 2012. Below are two outputs for it.
Code:
user1@darkstar:~$ inxi
CPU: Dual Core Intel Atom N2600 (-MT MCP-) speed/min/max: 600/600/1600 MHz
Kernel: 4.4.276-smp i686 Up: 44d 20h 54m Mem: 884.7/991.3 MiB (89.2%)
Storage: 298.09 GiB (44.7% used) Procs: 194 Shell: Bash inxi: 3.3.09
Code:
user1@darkstar:~$ inxi -MCazy
Machine:
  Type: Laptop System: ASUSTeK product: 1025C v: x.x
  serial: <superuser required> Chassis: type: 10 v: x.x
  serial: <superuser required>
  Mobo: ASUSTeK model: 1025C v: x.xx serial: <superuser required>
  BIOS: American Megatrends v: 1025C.1301 date: 08/16/2013
CPU:
  Info: Dual Core model: Intel Atom N2600 bits: 32 type: MT MCP arch: Saltwell
  family: 6 model-id: 36 (54) stepping: 1 microcode: 10C cache: L1: 112 KiB
  L2: 1024 KiB
  flags: ht nx pae sse sse2 sse3 ssse3 bogomips: 12771
  Speed: 600 MHz min/max: 600/1600 MHz Core speeds (MHz): 1: 600 2: 600 3: 800
  4: 1600
  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
According to my understanding, this processor has two cores and each core has two threads. In the output above I see the speeds of the four threads are not all the same. Is it really possible for two threads on a particular core to run at different speeds? I wonder if the script is reading the four speeds as closely together as possible, and storing the results for later use in the inxi script.

According to my understanding, the N2600 is a 64bit processor which can run in 32bit mode --- and for this particular line of laptops ASUS chose to have the processor to run in 32bit mode. :-(

According to something I read somewhere a while back, this processor has (where K = 1024): L1 = two 56 KB; and L2 = two 512 KB.

-----------------------------------------------
[Edit: found "pinxi"; added the section below.]

Using "pinxi 3.3.09-18 (2021-11-28)":
Code:
user1@darkstar:/tmp$ ./pinxi -MCazy
Machine:
  Type: Laptop System: ASUSTeK product: 1025C v: x.x
  serial: <superuser required> Chassis: type: 10 v: x.x
  serial: <superuser required>
  Mobo: ASUSTeK model: 1025C v: x.xx serial: <superuser required>
  BIOS: American Megatrends v: 1025C.1301 date: 08/16/2013
CPU:
  Info: Dual Core model: Intel Atom N2600 bits: 32 type: MT MCP arch: Saltwell
  family: 6 model-id: 36 (54) stepping: 1 microcode: 10C cache: L1: 112 KiB
  desc: d-2x24 KiB; i-2x32 KiB L2: 1024 KiB desc: 2x512 KiB
  flags: ht nx pae sse sse2 sse3 ssse3 bogomips: 3192
  Speed (MHz): avg: 900 high: 1600 min/max: 600/1600 cores: 1: 600 2: 800
  3: 1600 4: 600
  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

Last edited by baumei; 11-29-2021 at 09:56 PM.
 
Old 11-28-2021, 01:34 PM   #67
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928

Rep: Reputation: 515Reputation: 515Reputation: 515Reputation: 515Reputation: 515Reputation: 515
inxi 3.3.09-00 (2021-11-22)

pinxi 3.3.09-09 (2021-11-26)

An old HP notebook with Slackware64 14.2 (kernel 5.4.160)
Code:
./inxi -MCazy
Machine:
  Type: Laptop System: Hewlett-Packard
  product: Compaq Presario CQ40 Notebook PC v: 0393120000200D10000000000
  serial: <filter> Chassis: type: 10 serial: N/A
  Mobo: Hewlett-Packard model: 3607 v: 99.C3 serial: <filter> BIOS: Insyde
  v: F.66 date: 05/18/2010
CPU:
  Info: Single Core model: Intel 585 bits: 64 type: MCP arch: Core Merom
  family: 6 model-id: F (15) stepping: D (13) microcode: A3 cache: L1: 64 KiB
  L2: 1024 KiB
  flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 4322
  Speed: 2161 MHz min/max: N/A base/boost: 2166/2166 volts: 1.6 V
  ext-clock: 667 MHz Core speed (MHz): 1: 2161
  Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
  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
Code:
./pinxi -MCazy1
Machine:
  Type: Laptop
  System: Hewlett-Packard
    product: Compaq Presario CQ40 Notebook PC
    v: 0393120000200D10000000000
    serial: <filter>
  Chassis:
    type: 10
    serial: N/A
  Mobo: Hewlett-Packard
    model: 3607
    v: 99.C3
    serial: <filter>
  BIOS: Insyde
    v: F.66
    date: 05/18/2010

CPU:
  Info: Single Core
    model: Intel 585
    bits: 64
    type: MCP
    arch: Core Merom
    family: 6
    model-id: F (15)
    stepping: D (13)
    microcode: A3
    cache:
      L1: 64 KiB
        desc: d-1x32 KiB; i-1x32 KiB
      L2: 1024 KiB
        desc: 1x1024 KiB
    flags: lm nx pae sse sse2 sse3 ssse3
    bogomips: 4322
  Speed (MHz): 2161
    min/max: N/A
    base/boost: 2166/2166
    volts: 1.6 V
    ext-clock: 667 MHz
    core:
      1: 2161
  Vulnerabilities:
    Type: itlb_multihit
      status: KVM: Vulnerable
    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

A more up-to-date machine(signature machine), my main desktop with Slackware64 -current
Code:
inxi -MCazy
Machine:
  Type: Desktop Mobo: Gigabyte model: 970A-DS3P v: x.x serial: N/A
  BIOS: American Megatrends v: FD date: 02/26/2016
CPU:
  Info: 8-Core model: AMD FX-8320E socket: AM3 bits: 64 type: MCP
  arch: Bulldozer family: 15 (21) model-id: 2 stepping: 0 microcode: 6000822
  cache: L1: 640 KiB L2: 16 MiB L3: 8 MiB
  flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 51439
  Speed: 1405 MHz min/max: 1400/3200 MHz base/boost: 3200/3200 boost: enabled
  volts: 1.1 V ext-clock: 200 MHz Core speeds (MHz): 1: 1516 2: 2009 3: 1423
  4: 1532 5: 1406 6: 1393 7: 2204 8: 1425
  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, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Code:
./pinxi -MCazy1
Machine:
  Type: Desktop
  Mobo: Gigabyte
    model: 970A-DS3P
    v: x.x
    serial: N/A
  BIOS: American Megatrends
    v: FD
    date: 02/26/2016

CPU:
  Info: 8-Core
    model: AMD FX-8320E
    socket: AM3
    bits: 64
    type: MCP
    arch: Bulldozer
    family: 15 (21)
    model-id: 2
    stepping: 0
    microcode: 6000822
    cache:
      L1: 384 KiB
        desc: d-8x16 KiB; i-4x64 KiB
      L2: 8 MiB
        desc: 4x2 MiB
      L3: 8 MiB
        desc: 1x8 MiB
    flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 6429
  Speed (MHz):
    avg: 1579
    high: 2123
    min/max: 1400/3200
    base/boost: 3200/3200
    boost: enabled
    volts: 1.1 V
    ext-clock: 200 MHz
    cores:
      1: 1399
      2: 1393
      3: 1402
      4: 1405
      5: 2123
      6: 2105
      7: 1400
      8: 1406
  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, STIBP: disabled, RSB filling
    Type: srbds
      status: Not affected
    Type: tsx_async_abort
      status: Not affected
I tried to run inxi/pinxi in an old Pentium 233 but it seems dmidecode didn't find BIOS information.
It was running a severe crippled Slackware 14.1 install due to the 3GB IDE hard drive.
 
Old 11-28-2021, 01:49 PM   #68
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 556

Original Poster
Rep: Reputation: 316Reputation: 316Reputation: 316Reputation: 316
I'll be back later today, I'll obviously have to get a bit more organized in these checks based on the spectacular results and feedback, but preliminary results show that there may be something unhandled with L1 cache checks, and certain ARM cpu/processor count scenarios, as a base minimum. Also I think the way I handled stepping vs revision for x86 vs ARM/PPC/MIPS may have been a mistake, in addition to the original bugs that stepping had that have been corrected.

I can't thank you all enough, this is far better than I could have hoped for.
 
2 members found this post helpful.
Old 11-28-2021, 02:54 PM   #69
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 556

Original Poster
Rep: Reputation: 316Reputation: 316Reputation: 316Reputation: 316
pinxi 3.3.09-11 has fixes for PowerPC showing 'stepping:' instead of 'rev:', and also internally separates stepping values and string revision values. I think this more or less corrects the issues with stepping vs revision and being set to hex without being treated as hex internally.

I'll go through the rest of this stuff in a few hours, thanks again.
 
Old 11-28-2021, 03:18 PM   #70
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,337

Rep: Reputation: 4051Reputation: 4051Reputation: 4051Reputation: 4051Reputation: 4051Reputation: 4051Reputation: 4051Reputation: 4051Reputation: 4051Reputation: 4051Reputation: 4051
Code:
blackstar:/tmp:# ./pinxi -V | grep pinxi
pinxi 3.3.09-11 (2021-11-27)
Code:
blackstar:/tmp:# ./pinxi -MCazy         
Machine:
  Type: Laptop System: Dell product: Inspiron 5515 v: 1.5.0 serial: <filter>
  Chassis: type: 10 v: 1.5.0 serial: <filter>
  Mobo: Dell model: 0KDKG8 v: A00 serial: <filter> UEFI: Dell v: 1.5.0
  date: 09/07/2021
CPU:
  Info: 8-Core model: AMD Ryzen 7 5700U with Radeon Graphics socket: FP6
  bits: 64 type: MT MCP arch: Zen 2 family: 17 (23) model-id: 68 (104)
  stepping: 1 microcode: 8608103 cache: L1: 512 KiB
  desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB
  desc: 2x4 MiB
  flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 3593
  Speed (MHz): avg: 1982 high: 3882 min/max: 1400/1800 base/boost: 1800/4350
  boost: enabled volts: 1.2 V ext-clock: 100 MHz cores: 1: 1422 2: 1390
  3: 1826 4: 1366 5: 3447 6: 1397 7: 1934 8: 1427 9: 2339 10: 2600 11: 1803
  12: 1568 13: 1398 14: 1498 15: 2415 16: 3882
  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: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected


Code:
Level 1 cache size  ? 	8 x 32 KB 8-way set associative instruction caches
8 x 32 KB 8-way set associative data caches
Level 2 cache size  ? 	8 x 512 KB 8-way set associative unified caches
Level 3 cache size	2 x 4 MB shared caches
https://www.cpu-world.com/CPUs/Zen/A...e%205700U.html

Last edited by marav; 11-28-2021 at 03:19 PM.
 
Old 11-28-2021, 03:22 PM   #71
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,844

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
From inxi 3.3.09-00 (2021-11-22)

Code:
michael@darkstar:~$ inxi
CPU: 6-Core AMD FX-6300 (-MCP-) speed/min/max: 1712/1400/3500 MHz Kernel: 5.15.4 x86_64 Up: 6d 20h 57m
Mem: 3010.6/16006.2 MiB (18.8%) Storage: 1.82 TiB (18.1% used) Procs: 250 Shell: Bash inxi: 3.3.09
Code:
michael@darkstar:~$ inxi -MCazy
Machine:
  Type: Desktop Mobo: MSI model: 760GMA-P34(FX) (MS-7641) v: 5.0
  serial: <superuser required> BIOS: American Megatrends v: 25.1
  date: 04/20/2015
CPU:
  Info: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer
  family: 15 (21) model-id: 2 stepping: 0 microcode: 600081C cache:
  L1: 480 KiB L2: 12 MiB L3: 8 MiB
  flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 41999
  Speed: 1748 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz):
  1: 2822 2: 2157 3: 1418 4: 1414 5: 1459 6: 1543
  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, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
 
Old 11-28-2021, 10:14 PM   #72
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 556

Original Poster
Rep: Reputation: 316Reputation: 316Reputation: 316Reputation: 316
mlangdn, missing the pinxi, but that was another good one, the bulldozer id was wrong, it's piledriver, that was a bug in inxi, so good one.

pinxi 3.3.09-13 fixes that false arch for bulldozer/piledriver, but also fixes a host of issues with failing cpu core counts. Also has a big global redo of the risc cpu detections and handlers, all are now merged into one global that is far easier to test than the way I had done it previously, which led to random failures for a given RISC cpu type that was different from a different, say, ARM test, now it's a global test, which should make more stuff 'just work', though that always takes empirical data and testing per processor type since the data is always different. But it should be better, though there may also be some errors you didn't see before, but some values will also be seen that were not seen before.

For the risc-v system now shows:

Code:
CPU:
  Info: Quad Core
    model: N/A
    bits: 64
    type: MCP
    arch: riscv64
    family: N/A
    model-id: N/A
    cache:
      L1: 256 KiB
        desc: d-4x32 KiB; i-4x32 KiB
      L2: 2 MiB
        desc: 1x2 MiB
    bogomips: 0
  Speed: N/A
    min/max: N/A
    cores: No per core speed data found.
  Features: N/A
  Vulnerabilities: No CPU vulnerability/bugs data available.
This is using fake data injected in, so there may be a few values that are off, but most should be right.

For the PowerPC failures:

Code:
PU:
  Info: 16-Core
    model: N/A
    bits: 64
    type: MCP
    arch: ARMv8
    family: 8
    model-id: 0
    stepping: 3
    cache:
      L1: 1.2 MiB
        desc: d-16x32 KiB; i-16x48 KiB
      L2: 8 MiB
        desc: 8x1024 KiB
      L3: 8 MiB
        desc: 1x8 MiB
    bogomips: 0
  Speed: N/A
    min/max: N/A
    cores: No per core speed data found.
  Features: aes asimd cpuid crc32 evtstrm fp pmull sha1 sha2
  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
Both of these highlighted a series of possible failure cases, so I thought it was worth totally fixing the underlying cause rather than just adding more test types, that may or may not break specific risc type systems, but in general, it should improve the stuff I think, hope anyway.

I'm going to start on all the new samples as well now, but wanted to get these significant failure cases handled before doing anything else.
 
1 members found this post helpful.
Old 11-28-2021, 11:16 PM   #73
h2-1
Member
 
Registered: Mar 2018
Distribution: Debian Testing
Posts: 556

Original Poster
Rep: Reputation: 316Reputation: 316Reputation: 316Reputation: 316
pinxi 3.3.09-14 gets some more sensors data from the power nv sensors, and enables showing gpu sensor data even if the main sensors detections failed.

This is from the PowerPC data:

Code:
Sensors:
  System Temperatures:
    cpu: 68.0 C
    mobo: N/A
    gpu: amdgpu
      temp: 74.0 C
  Fan Speeds (RPM): N/A
    gpu: amdgpu
      fan: 351
 
Old 11-29-2021, 12:40 AM   #74
z80
Member
 
Registered: Jul 2019
Location: Europe
Distribution: Slackware64-current
Posts: 135

Rep: Reputation: 99
Pinxi 3.3.09-14 detects a quad core CPU (which is correct) but then shows eight cores:

Code:
Machine:
  Type: Desktop
  System: Hewlett-Packard
    product: HP Z200 SFF Workstation
    v: N/A
    serial: <filter>
  Chassis:
    type: 4
    serial: <filter>
  Mobo: Hewlett-Packard
    model: 0B48h
    serial: <filter>
  BIOS: Hewlett-Packard
    v: 786H4 v01.19
    date: 02/11/2016

CPU:
  Info: Quad Core
    model: Intel Core i7 870
    socket: XU1 PROCESSOR
    bits: 64
    type: MT MCP
    arch: Nehalem
    family: 6
    model-id: 1E (30)
    stepping: 5
    microcode: 8
    cache:
      L1: 256 KiB
        desc: d-4x32 KiB; i-4x32 KiB
      L2: 1024 KiB
        desc: 4x256 KiB
      L3: 8 MiB
        desc: 1x8 MiB
    flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
    bogomips: 5852
  Speed (MHz):
    avg: 1364
    high: 1668
    min/max: 1199/3066
    base/boost: 2933/6000
    boost: enabled
    volts: 1.2 V
    ext-clock: 133 MHz
    cores:
      1: 1211
      2: 1439
      3: 1197
      4: 1213
      5: 1197
      6: 1615
      7: 1668
      8: 1374
  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: Not affected
    Type: tsx_async_abort
      status: Not affected
 
Old 11-29-2021, 12:53 AM   #75
bw42
Member
 
Registered: Feb 2011
Distribution: Slackware
Posts: 65

Rep: Reputation: 51
Updated pinxi and ran it again.
Here's what its showing for my POWER9 now with the -CMay1zfs flags.

Code:
Machine:
  Type: PPC
  System: C1P9S01 REV 1.01
    details: N/A

CPU:
  Info: 8-Core
    model: POWER9 altivec supported
    bits: 64
    type: MT MCP
    arch: ppc64le
    family: N/A
    model-id: N/A
    rev: 2.2 (pvr 004e 1202)
    cache:
      L1: 512 KiB
        desc: d-8x32 KiB; i-8x32 KiB
      L2: 4 MiB
        desc: 8x512 KiB
      L3: 80 MiB
        desc: 8x10 MiB
    bogomips: N/A
  Speed (MHz):
    avg: 2560
    high: 3800
    min/max: 2166/3800
    boost: enabled
    cores:
      1: 2166
      2: 2183
      3: 2166
      4: 2166
      5: 2166
      6: 2166
      7: 2166
      8: 2166
      9: 2166
      10: 2166
      11: 2166
      12: 2166
      13: 2350
      14: 2350
      15: 2350
      16: 2350
      17: 2350
      18: 2350
      19: 2166
      20: 2166
      21: 3800
      22: 3800
      23: 3800
      24: 3800
      25: 3800
      26: 3800
      27: 3800
      28: 2166
      29: 2183
      30: 2183
      31: 2183
      32: 2183
  Features: N/A
  Vulnerabilities:
    Type: itlb_multihit
      status: Not affected
    Type: l1tf
      mitigation: RFI Flush, L1D private per thread
    Type: mds
      status: Not affected
    Type: meltdown
      mitigation: RFI Flush, L1D private per thread
    Type: spec_store_bypass
      mitigation: Kernel entry/exit barrier (eieio)
    Type: spectre_v1
      mitigation: __user pointer sanitization, ori31 speculation barrier enabled
    Type: spectre_v2
      mitigation: Indirect branch cache disabled, Software link stack flush
    Type: srbds
      status: Not affected
    Type: tsx_async_abort
      status: Not affected

Sensors:
  System Temperatures:
    cpu: 50.0 C
    mobo: N/A
    gpu: amdgpu
      temp: 59.0 C
  Fan Speeds (RPM): N/A
    gpu: amdgpu
      fan: 342
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
pinxi/inxi huge BSD updates, testers? h2-1 *BSD 0 03-08-2021 11:54 PM
Testersfeedback for new pinxi/inxi feature -E/--bluetooth h2-1 Slackware 2 01-29-2021 06:53 PM
Huge inxi/pinxi upgrade, new features, Logical volumes, raid rewrite, beta testers? h2-1 Slackware 12 12-17-2020 05:04 PM
Beta testers for Perl inxi requested h2-1 Slackware 147 12-14-2020 09:00 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:35 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration