i5-2500 only using 3 cores instead of 4?

boggie1688

Explorer
Joined
Jul 9, 2015
Messages
58
Hi!

I just upgraded my freenas build's motherboard and cpu from an AMD Phenom 3 core to a Intel i5-2500K 4 core. Booted up fine, but I noticed in the reporting section of the system, it only lists:
Cpu0
Cpu1
Cpu2

Cpu3 is missing.
Freenas correctly detects that I now have a Intel i5 2500 4 core, but it appears to not be using the 4th core.

I ran:
dmesg | grep -i cpu

I received the following output:
Code:
CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (3309.79-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (3309.79-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (3309.79-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3


I don't claim to completely understand everything there, but I imagine I should also be seeing "SMP: AP CPU #4 Launched!".

Anyone know how I might go about getting Freenas to use the 4th core?
 

anmnz

Patron
Joined
Feb 17, 2018
Messages
286
Those log entries are normal for a 4-core system. The system initially starts up using 1 CPU core, and then the "SMP: AP CPU launched" messages are telling you that it has found the others. You can then see all 4 CPU cores in the later messages. They are named "cpu0", "cpu1", "cpu2", "cpu3".
 

boggie1688

Explorer
Joined
Jul 9, 2015
Messages
58
Those log entries are normal for a 4-core system. The system initially starts up using 1 CPU core, and then the "SMP: AP CPU launched" messages are telling you that it has found the others. You can then see all 4 CPU cores in the later messages. They are named "cpu0", "cpu1", "cpu2", "cpu3".

Ahh ok, thank you for explaining that!
 

boggie1688

Explorer
Joined
Jul 9, 2015
Messages
58
Those log entries are normal for a 4-core system. The system initially starts up using 1 CPU core, and then the "SMP: AP CPU launched" messages are telling you that it has found the others. You can then see all 4 CPU cores in the later messages. They are named "cpu0", "cpu1", "cpu2", "cpu3".


Wait hold on, under reporting I can only see temps for cpu0, cpu1 and cpu2. Should I see a cpu3 too?
 

anmnz

Patron
Joined
Feb 17, 2018
Messages
286
I would imagine so but without seeing anything it's hard to know. As this seems to be a reporting problem, rather than an OS functionality problem, can I suggest you start a new thread and provide screenshots?
 
Top