slackware -current on a xeon CPU E3-1220 v3 @ 3.10GHz
lscpu htop inxi and /proc/cpuinfo all show a single core instead of 4.
ive got no idea where to even start on this

On BIOS.

Usually, the Intel motherboards have an option to choose the number of active cores.

bios shows "active processor cores All". thats the only thing i see related

Hello,

Check if ACPI is enabled and post the output of dmesg.

--
SeB

acpi is enabled and dmesg is too long to post. anything specific i should grep it for?

sudo dmesg |grep cpu

[ 0.117535] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:1 nr_node_ids:1
[ 0.117916] percpu: Embedded 52 pages/cpu s176128 r8192 d28672 u2097152
[ 0.117935] pcpu-alloc: s176128 r8192 d28672 u2097152 alloc=1*2097152
[ 0.117943] pcpu-alloc: [0] 0
[ 0.279750] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=1.
[ 0.279763] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.331083] cpuidle: using governor ladder
[ 0.331263] cpuidle: using governor menu
[ 0.338604] cryptd: max_cpu_qlen set to 1000
[ 11.224115] [drm] GART: num cpu pages 262144, num gpu pages 262144

bash-5.1$ sudo dmesg |grep processor
[ 0.000000] tsc: Detected 3093.075 MHz processor
[ 0.324166] smpboot: Total of 1 processors activated (6186.15 BogoMIPS)

Try this:

For me I see this:
If that is not what is expected maybe you should review blacklists and boot parameters. (I use lilo which is the default for 14.2)

On my system I have 2 cores with 4 cpus, which agrees with /proc/cpuinfo

Hello,

You can save the output of dmesg in a .txt file (256k max) and attach it.

Can you give more info on the system and especially on the motherboard. Is the bios is up-to-date ?

Is the issue specific to -current ?

Do you experience same issue with another slackware version, or linux flavor. If you have a 14-2 install cd/dvd/usb at hand, check if dmesg returns same (cpu) info.

--
SeB

dmesg.txt




dmesg|grep smpboot

[ 0.102418] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.352475] smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 1090
[ 0.352616] smpboot: CPU0: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz (family: 0x6, model: 0x3c, stepping: 0x3)
[ 0.354332] smpboot: Max logical packages: 1
[ 0.354430] smpboot: Total of 1 processors activated (6185.86 BogoMIPS)


lscpu

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz
CPU family: 6
Model: 60
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Stepping: 3
CPU max MHz: 3500.0000
CPU min MHz: 800.0000
BogoMIPS: 6185.86
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_ts
c cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse
4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpc
id_single pti ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep
bmi2 erms invpcid xsaveopt dtherm ida arat pln pts
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 32 KiB (1 instance)
L1i: 32 KiB (1 instance)
L2: 256 KiB (1 instance)
L3: 8 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0
Vulnerabilities:
Itlb multihit: KVM: Mitigation: VMX disabled
L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Meltdown: Mitigation; PTI
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling
Srbds: Vulnerable: No microcode
Tsx async abort: Not affected

mobo is an asus p9d-m
cpu is an Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz

the issue does not seem to be specific to -current as ive tried other distros and same thing

just updated bios this morning

So, we debug a Debian kernel?

huh? im running slackware -current

You are sure? The quote was the beginning of your dmesg.txt file from:

https://www.linuxquestions.org/quest...chmentid=36690

huh? im running slackware -current

dmesg1.txt


i dont know where debian came from... here is slackwares dmesg

my bad