High ACPI CPU usage on a Supermicro X9DRT-HF+

[Andriy Gapon]

on 09/11/2012 04:01 Jason Wolfe said the following:
> Hi,
> 
> I'm having an issue with a large pool of Supermicro X9DRT-HF+ servers in
> which the ACPI processes basically burn up a whole CPU.  I have ACPI debug
> mode compiled/enabled, but as I'm not actually having any issues per se,
> I'm having trouble with the next steps.  This is fairly new Sandy Bridge
> hardware, so I figure it's possible something needs to be fleshed out in
> the code.  Every BIOS option relating to ACPI has been flipped back and
> forth, and booting without ACPI support causes a panic.
> 
> Here is the verbose boot log as well as the acpidump -dt output, and other
> interesting bits:
> 
> http://nitrology.com/dmesg.acpi
> http://nitrology.com/jason-X9DRT-HF.asl
> 
> sysctl hw.acpi:
> hw.acpi.supported_sleep_state: S1 S4 S5
> hw.acpi.power_button_state: S5
> hw.acpi.sleep_button_state: S1
> hw.acpi.lid_switch_state: NONE
> hw.acpi.standby_state: S1
> hw.acpi.suspend_state: NONE
> hw.acpi.sleep_delay: 1
> hw.acpi.s4bios: 0
> hw.acpi.verbose: 1
> hw.acpi.disable_on_reboot: 0
> hw.acpi.handle_reboot: 1
> hw.acpi.reset_video: 0
> hw.acpi.cpu.cx_lowest: C1
> 
> vmstat -i:
> interrupt total rate
> irq9: acpi0 12170706 14610
> cpu0: timer 1662074 1995
> cpu3: timer 1644465 1974
> cpu4: timer 1644529 1974
> cpu1: timer 1644423 1974
> cpu5: timer 1644498 1974
> cpu2: timer 1644479 1974
> 
> top -SHb:
> last pid: 1979; load averages: 1.39, 1.35, 0.90 up 0+00:13:54 18:46:27
> 160 processes: 8 running, 119 sleeping, 33 waiting
> 
> Mem: 2355M Active, 11G Inact, 7431M Wired, 216K Cache, 6559M Buf, 41G Free
> Swap: 24G Total, 24G Free
> 
> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND
> 11 root 171 ki31 0K 96K RUN 4 11:52 89.70% idle{idle: cpu4}
> 11 root 171 ki31 0K 96K CPU5 5 11:55 86.67% idle{idle: cpu5}
> 11 root 171 ki31 0K 96K CPU2 2 11:14 84.08% idle{idle: cpu2}
> 11 root 171 ki31 0K 96K CPU3 3 9:56 76.76% idle{idle: cpu3}
> 11 root 171 ki31 0K 96K CPU1 1 9:09 70.90% idle{idle: cpu1}
> 11 root 171 ki31 0K 96K RUN 0 9:24 70.07% idle{idle: cpu0}
> 12 root -52 - 0K 528K WAIT 3 3:25 27.29% intr{irq9: acpi0}
> 0 root 8 0 0K 320K CPU4 4 3:39 25.59% kernel{acpi_task_2}
> 0 root 8 0 0K 320K - 2 3:40 25.39% kernel{acpi_task_0}
> 0 root 8 0 0K 320K - 5 3:39 25.20% kernel{acpi_task_1}

As a first step please add the following to the loader.conf and see what gets
reported and at what frequency:
debug.acpi.layer="ACPI_EVENTS"
debug.acpi.level="ACPI_LV_INFO

Also, is your system DTrace-enabled?

-- 
Andriy Gapon