Project

General

Profile

Bug #2524

SNMP only shows one processor on a dual core system

Added by Jonathan Black over 8 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
06/26/2012
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0.1
Affected Architecture:
amd64

Description

The output of "dmesg | grep -i cpu" is:

CPU: Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz (2199.97-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
SMP: AP CPU #1 Launched!

Output from Top:

PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
27596 root 1 64 20 5836K 1488K select 1 0:14 0.00% apinger
7309 root 1 44 0 25768K 5500K kqread 0 0:09 0.00% lighttpd

The "C" column indicates the system is using both CPUs.

However when I run "snmpwalk -v2c -cpublic 192.168.1.1 1.3.6.1.2.1.25.3.3.1.1" it only shows a single CPU:

HOST-RESOURCES-MIB::hrProcessorFrwID.7 = OID: SNMPv2-SMI::zeroDotZero

I have another system with a dual core processor (E2140) and it shows two CPUs when probing with SNMP.

History

#1 Updated by Jonathan Black over 8 years ago

I have a second system that is doing this now too.

When I type dmesg | grep -i cpu it shows:

CPU: AMD Athlon(tm) Dual Core Processor 4450B (2310.53-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
powernow0: <PowerNow! K8> on cpu0
powernow1: <PowerNow! K8> on cpu1
SMP: AP CPU #1 Launched!

When I run the snmpwalk command above it shows a single CPU.

Top also shows that the system has 2 CPUs and it is assigning threads to both CPUs.

#2 Updated by Chris Buechler almost 7 years ago

  • Status changed from New to Resolved

this was fixed quite some time ago

Also available in: Atom PDF