From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 9 02:01:46 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B10A7DB for ; Fri, 9 Nov 2012 02:01:46 +0000 (UTC) (envelope-from nitroboost@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id C93168FC0A for ; Fri, 9 Nov 2012 02:01:45 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id x43so1934064wey.13 for ; Thu, 08 Nov 2012 18:01:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=xh/pxK2cFfTfOAXlXyLJXSFYFKLtyTOxGHoUxF6fUy8=; b=b9QUZbHC48Myh5uct31URY2fxEAOkk5cMghYD7h90FfzTcwcB+YSmFAVhb2DULInWL 59tYxyPE8kww6m5z6zuRnvWuGZjFxj7gw3aFRiT1YWYGmu2gm0s0JZhtwbvb267Xshbg ZXW5ldFeUN17oH1z10cNX7+77jHu4hSbMPDnQ9Mt4A5hDxm58GCtC04OHsB5Ol+4QpgV BcCg2gs7sCONNgmp0v4HP/gPqa/6OQnHrg69CqmrZXjDqfKrPHv9Bisgsc7EYcsuuiD1 essQS0tinNH+WTE64f/aHn0R67bIfd25odXwlkF56Sw2vRLKwNMRQ+OkW6npI+Lr9o1Z gcXA== MIME-Version: 1.0 Received: by 10.180.108.38 with SMTP id hh6mr280574wib.0.1352426499382; Thu, 08 Nov 2012 18:01:39 -0800 (PST) Received: by 10.194.15.196 with HTTP; Thu, 8 Nov 2012 18:01:39 -0800 (PST) Date: Thu, 8 Nov 2012 19:01:39 -0700 Message-ID: Subject: High ACPI CPU usage on a Supermicro X9DRT-HF+ From: Jason Wolfe To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 02:01:46 -0000 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} 1583 squid 49 0 1378M 1299M kqread 2 1:26 10.50% squid 12 root -68 - 0K 528K WAIT 2 0:15 2.49% intr{irq258: igb0:que} 12 root -68 - 0K 528K WAIT 1 0:12 2.29% intr{irq257: igb0:que} 12 root -68 - 0K 528K WAIT 0 0:14 1.95% intr{irq256: igb0:que} 12 root -68 - 0K 528K WAIT 5 0:12 1.66% intr{irq261: igb0:que} 12 root -68 - 0K 528K WAIT 3 0:13 1.27% intr{irq259: igb0:que} 12 root -68 - 0K 528K WAIT 4 0:12 1.07% intr{irq260: igb0:que} 0 root -16 0 0K 320K sched 1 413:17 0.00% kernel{swapper} Thanks! Jason