ACPI problems op ASrock

[Ian Smith]

On Sat, 26 Sep 2015 10:17:20 +0200, Arthur van der Peijl wrote:
 > Thank you for assistance: powerd must clearly not be my focus: the 
 > CPU stays high and thus cannot go into idle mode.

 > No need to change performance_cx_lowest as I just have a Pentium 
 > G3220 running.
 > 
 > [root at zfsguru /home/ssh]# cat /boot/loader.conf | grep hint.
 > hint.p4tcc.0.disabled="1"
 > hint.acpi_throttle.0.disabled="1"
 > 
 > Tried to change lowest level on running system: 
 > 
 > [root at zfsguru /home/ssh]# sysctl dev.cpu.0.cx_lowest=C8
 > dev.cpu.0.cx_lowest: C8 -> C8

You really need to set hw.acpi.cpu.cx_lowest=C8 instead; this is then 
propogated to dev.cpu.*.cx_lowest, updated when /etc/rc.d/power_profile 
runs on losing or regaining mains power.  However, that won't help here.

 > We're already there. The document described some other setting which 
 > could be read:
 > 
 > [root at zfsguru /home/ssh]# sysctl dev.cpu | grep cx
 > dev.cpu.1.cx_usage: 100.00% last 5us
 > dev.cpu.1.cx_lowest: C8
 > dev.cpu.1.cx_supported: C1/1/1
 > dev.cpu.0.cx_usage: 100.00% 0.00% last 4us
 > dev.cpu.0.cx_lowest: C8
 > dev.cpu.0.cx_supported: C1/1/1 C2/2/117
 > 
 > I don't inderstand this. 100% CPU is my main issue, created by 
 > {acpi_task} in the kernal. However -> CPU1 supports different states 
 > as CPU0? Or is this a summary of last states?

I don't follow this either, and don't recall seeing different C-states 
available on different CPUs?  If cpu1 has only C1, I can't see how cpu0 
could ever use C2 - with its real win in terms of power consumption - as 
all CPUs are now set to the same C-state (and P-state) as far as I know.

Is cpu1 a real CPU, or HTT? Perhaps show the CPU detection details from 
dmesg.  powerd with standard parameters will always run at top speed 
with the CPU usage/idle figures you quoted; you could get it to run 
slower if you adjusted -i and -r settings, as an immediate workaround.

But listen to John about debugging the ACPI tasks CPU usage issue ..

cheers, Ian