Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    powerD only able to access one core

    General pfSense Questions
    2
    5
    274
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      puneet1984 last edited by puneet1984

      Hello

      I have a Dell optiplex 3050 micro system running pfsense v22.05 with intel i3 6100 2 core processor @3.7GHz.

      pfsense-powerd is able to manage only one core and second core shows no freq levels or current freq.

      $ sysctl -a | grep -i cpu
      
      kern.smp.cpus: 2
      kern.smp.maxcpus: 256
      FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
      cpu0: <ACPI CPU> on acpi0
      est0: <Enhanced SpeedStep Frequency Control> on cpu0
      <118>Launching the init system...Updating CPU Microcode...
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3695.99-MHz K8-class CPU)
      coretemp0: <CPU On-Die Thermal Sensors> on cpu0
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3700.00-MHz K8-class CPU)
      FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
      cpu0: <ACPI CPU> on acpi0
      hwpstate_intel0: <Intel Speed Shift> on cpu0
      hwpstate_intel1: <Intel Speed Shift> on cpu1
      <118>Launching the init system...Updating CPU Microcode...
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3695.99-MHz K8-class CPU)
      coretemp0: <CPU On-Die Thermal Sensors> on cpu0
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3700.00-MHz K8-class CPU)
      FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
      cpu0: <ACPI CPU> on acpi0
      hwpstate_intel0: <Intel Speed Shift> on cpu0
      hwpstate_intel1: <Intel Speed Shift> on cpu1
      <118>Launching the init system...Updating CPU Microcode...
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3695.99-MHz K8-class CPU)
      coretemp0: <CPU On-Die Thermal Sensors> on cpu0
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3700.00-MHz K8-class CPU)
      FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
      cpu0: <ACPI CPU> on acpi0
      hwpstate_intel0: <Intel Speed Shift> on cpu0
      hwpstate_intel1: <Intel Speed Shift> on cpu1
      <118>Launching the init system...Updating CPU Microcode...
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3695.99-MHz K8-class CPU)
      coretemp0: <CPU On-Die Thermal Sensors> on cpu0
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3700.00-MHz K8-class CPU)
      FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
      cpu0: <ACPI CPU> on acpi0
      hwpstate_intel0: <Intel Speed Shift> on cpu0
      hwpstate_intel1: <Intel Speed Shift> on cpu1
      <118>Launching the init system...Updating CPU Microcode...
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3695.99-MHz K8-class CPU)
      coretemp0: <CPU On-Die Thermal Sensors> on cpu0
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3696.18-MHz K8-class CPU)
      FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
      cpu0: <ACPI CPU> on acpi0
      est0: <Enhanced SpeedStep Frequency Control> on cpu0
      <118>Launching the init system...Updating CPU Microcode...
      CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3696.18-MHz K8-class CPU)
      coretemp0: <CPU On-Die Thermal Sensors> on cpu0
      kern.ccpu: 0
        <cpu count="2" mask="3,0,0,0">0, 1</cpu>
      kern.sched.cpusetsize: 32
      kern.pin_pcpu_swi: 0
      kern.racct.pcpu_threshold: 1
      cpu	HAMMER
      device	cpufreq
      kern.vt.splash_cpu_duration: 10
      kern.vt.splash_cpu_style: 2
      kern.vt.splash_ncpu: 0
      kern.vt.splash_cpu: 0
      vfs.ncpurgeminvnodes: 16
      net.inet.tcp.per_cpu_timers: 0
      debug.cpufreq.verbose: 0
      debug.cpufreq.lowest: 0
      debug.acpi.cpu_unordered: 0
      kdb.enter.default=textdump set; capture on; show registers ; run lockinfo; show pcpu; bt; ps; alltrace; capture off; textdump dump; reset
      hw.model: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
      hw.ncpu: 2
      hw.acpi.cpu.cx_lowest: C1
      hw.intrs: irq0: attimer0:3 @cpu0(domain0): 0
      dev.coretemp.1.%parent: cpu1
      dev.coretemp.1.%desc: CPU On-Die Thermal Sensors
      dev.coretemp.0.%parent: cpu0
      dev.coretemp.0.%desc: CPU On-Die Thermal Sensors
      dev.cpufreq.1.%parent: cpu1
      dev.cpufreq.1.%pnpinfo:
      dev.cpufreq.1.%location:
      dev.cpufreq.1.%driver: cpufreq
      dev.cpufreq.1.%desc:
      dev.cpufreq.0.%parent: cpu0
      dev.cpufreq.0.%pnpinfo:
      dev.cpufreq.0.%location:
      dev.cpufreq.0.%driver: cpufreq
      dev.cpufreq.0.%desc:
      dev.cpufreq.%parent:
      dev.est.1.%parent: cpu1
      dev.est.0.%parent: cpu0
      dev.acpi_perf.1.%parent: cpu1
      dev.acpi_perf.0.%parent: cpu0
      dev.cpu.1.temperature: 42.0C
      dev.cpu.1.coretemp.throttle_log: 0
      dev.cpu.1.coretemp.tjmax: 100.0C
      dev.cpu.1.coretemp.resolution: 1
      dev.cpu.1.coretemp.delta: 58
      dev.cpu.1.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc
      dev.cpu.1.cx_usage_counters: 6525862 0 0
      dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 34us
      dev.cpu.1.cx_lowest: C1
      dev.cpu.1.cx_supported: C1/1/1 C2/2/151 C3/3/256
      dev.cpu.1.%parent: acpi0
      dev.cpu.1.%pnpinfo: _HID=none _UID=0 _CID=none
      dev.cpu.1.%location: handle=\_PR_.CPU1
      dev.cpu.1.%driver: cpu
      dev.cpu.1.%desc: ACPI CPU
      dev.cpu.0.temperature: 42.0C
      dev.cpu.0.coretemp.throttle_log: 0
      dev.cpu.0.coretemp.tjmax: 100.0C
      dev.cpu.0.coretemp.resolution: 1
      dev.cpu.0.coretemp.delta: 58
      dev.cpu.0.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc
      dev.cpu.0.cx_usage_counters: 2762062 0 0
      dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 764us
      dev.cpu.0.cx_lowest: C1
      dev.cpu.0.cx_supported: C1/1/1 C2/2/151 C3/3/256
      dev.cpu.0.freq_levels: 3700/51000 3500/46853 3300/43343 3100/39492 2900/36242 2700/32660 2500/29668 2300/26786 2200/25175 2000/22476 1800/19477 1600/17005 1400/14259 1200/12011 1000/9867 800/7470
      dev.cpu.0.freq: 3300
      dev.cpu.0.%parent: acpi0
      dev.cpu.0.%pnpinfo: _HID=none _UID=0 _CID=none
      dev.cpu.0.%location: handle=\_PR_.CPU0
      dev.cpu.0.%driver: cpu
      dev.cpu.0.%desc: ACPI CPU
      dev.cpu.%parent:
      security.jail.param.cpuset.id: 0
      
      1 Reply Last reply Reply Quote 0
      • P
        puneet1984 last edited by

        there is no log for est0 on cpu1

        $ sysctl -a | grep -i est
        est0: <Enhanced SpeedStep Frequency Control> on cpu0
        est0: <Enhanced SpeedStep Frequency Control> on cpu0
        dev.est.1.freq_settings: 3700/51000 3500/46853 3300/43343 3100/39492 2900/36242 2700/32660 2500/29668 2300/26786 2200/25175 2000/22476 1800/19477 1600/17005 1400/14259 1200/12011 1000/9867 800/7470
        dev.est.1.%parent: cpu1
        dev.est.1.%pnpinfo:
        dev.est.1.%location:
        dev.est.1.%driver: est
        dev.est.1.%desc: Enhanced SpeedStep Frequency Control
        dev.est.0.freq_settings: 3700/51000 3500/46853 3300/43343 3100/39492 2900/36242 2700/32660 2500/29668 2300/26786 2200/25175 2000/22476 1800/19477 1600/17005 1400/14259 1200/12011 1000/9867 800/7470
        dev.est.0.%parent: cpu0
        dev.est.0.%pnpinfo:
        dev.est.0.%location:
        dev.est.0.%driver: est
        dev.est.0.%desc: Enhanced SpeedStep Frequency Control
        dev.est.%parent:
        dev.cpu.1.cx_lowest: C1
        dev.cpu.0.cx_lowest: C1
        
        $sysctl -a | grep -i cpu1
        hwpstate_intel1: <Intel Speed Shift> on cpu1
        hwpstate_intel1: <Intel Speed Shift> on cpu1
        hwpstate_intel1: <Intel Speed Shift> on cpu1
        hwpstate_intel1: <Intel Speed Shift> on cpu1
        irq257: hpet0:t1:243 @cpu1(domain0): 0
        dev.coretemp.1.%parent: cpu1
        dev.cpufreq.1.%parent: cpu1
        dev.est.1.%parent: cpu1
        dev.acpi_perf.1.%parent: cpu1
        dev.cpu.1.%location: handle=\_PR_.CPU1
        
        $sysctl -a | grep -i cpu.1
        dev.cpu.1.temperature: 42.0C
        dev.cpu.1.coretemp.throttle_log: 0
        dev.cpu.1.coretemp.tjmax: 100.0C
        dev.cpu.1.coretemp.resolution: 1
        dev.cpu.1.coretemp.delta: 58
        dev.cpu.1.cx_method: C1/mwait/hwc C2/mwait/hwc C3/mwait/hwc
        dev.cpu.1.cx_usage_counters: 6723948 0 0
        dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 5us
        dev.cpu.1.cx_lowest: C1
        dev.cpu.1.cx_supported: C1/1/1 C2/2/151 C3/3/256
        dev.cpu.1.%parent: acpi0
        dev.cpu.1.%pnpinfo: _HID=none _UID=0 _CID=none
        dev.cpu.1.%location: handle=\_PR_.CPU1
        dev.cpu.1.%driver: cpu
        dev.cpu.1.%desc: ACPI CPU
        
        stephenw10 1 Reply Last reply Reply Quote 0
        • stephenw10
          stephenw10 Netgate Administrator last edited by

          est(4) only ever operates on the first core, all cores use the same frequency.

          However in 23.01 the Intel Speed Shift driver is included by default. You must be running that because we can see it reported in the boot log. That can set the frequency per core and overrides powerd with est (Speedstep).

          Steve

          1 Reply Last reply Reply Quote 0
          • P
            puneet1984 last edited by

            ok thanks for the info..
            I thought something is wrong with my CPU/bios settings

            i have not upgraded to 23.01 and thus not able to use speedshift as there is issue with my WAN connection...it disconnects automatically (after 90 sec to 45 min) and then only reboot can bring WAN back.

            1 Reply Last reply Reply Quote 0
            • stephenw10
              stephenw10 Netgate Administrator @puneet1984 last edited by

              @puneet1984 said in powerD only able to access one core:

              $sysctl -a | grep -i cpu1
              hwpstate_intel1: <Intel Speed Shift> on cpu1
              hwpstate_intel1: <Intel Speed Shift> on cpu1
              hwpstate_intel1: <Intel Speed Shift> on cpu1
              hwpstate_intel1: <Intel Speed Shift> on cpu1

              You must have been running it when you took that sysctl output though?

              1 Reply Last reply Reply Quote 0
              • First post
                Last post