From owner-freebsd-current@FreeBSD.ORG Tue Feb 19 10:16:56 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3591AD81 for ; Tue, 19 Feb 2013 10:16:56 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 19D151B9 for ; Tue, 19 Feb 2013 10:16:55 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,694,1355126400"; d="scan'208";a="23761864" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 19 Feb 2013 02:16:55 -0800 Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r1JAGt0c024203; Tue, 19 Feb 2013 02:16:55 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0328.009; Tue, 19 Feb 2013 02:16:55 -0800 From: "Eggert, Lars" To: Fleuriot Damien Subject: Re: system 20% busy at all times? Thread-Topic: system 20% busy at all times? Thread-Index: AQHODoSUIkOKNPDzb0yS23V/tl+kl5iBc1WAgAABSACAAAKwgIAABj+A Date: Tue, 19 Feb 2013 10:16:54 +0000 Message-ID: References: <36DD2FB4-E26A-4F03-95D9-FFD855957269@my.gd> In-Reply-To: <36DD2FB4-E26A-4F03-95D9-FFD855957269@my.gd> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2013 10:16:56 -0000 Hi, On Feb 19, 2013, at 10:54, Fleuriot Damien wrote: > And indeed we find your answer here, acpi0 firing up a lot of interrupts. >=20 > Don't you get any message about that in dmesg -a or /var/log/messages ? >=20 > I'd expect something like "interrupt storm blabla=85 source throttled bla= bla.." nope. The only odd ACPI-related messages I see in dmesg are these: ACPI Error: [\134_SB_.PCI0.LPC0.BCMD] Namespace lookup failure, AE_NOT_FOUN= D (20130117/psargs-393) ACPI Error: Method parse/execution failed [\134_PR_.CPU0._OSC] (Node 0xffff= fe0007630c00), AE_NOT_FOUND (20130117/psparse-560) ACPI Error: [\134_SB_.PCI0.LPC0.BCMD] Namespace lookup failure, AE_NOT_FOUN= D (20130117/psargs-393) ACPI Error: Method parse/execution failed [\134_PR_.CPU0._OSC] (Node 0xffff= fe0007630c00), AE_NOT_FOUND (20130117/psparse-560) ACPI Error: Method parse/execution failed [\134_PR_.CPU0._PDC] (Node 0xffff= fe0007630c40), AE_NOT_FOUND (20130117/psparse-560) Nothing in syslog. > From man 4 acpi , in /boot/loader.conf : > hint.acpi.0.disabled=3D1 > Set this to 1 to disable all of ACPI. If ACPI has been disab= led > on your system due to a blacklist entry for your BIOS, you ca= n > set this to 0 to re-enable ACPI for testing. >=20 > Any chance you could reboot the host with ACPI disabled ? If I do that, I get an early kernel crash: Loading 10.11.12.13/~elars/kernel/kernel:0x200000/7634255 0xb47d50/473552 0= xbbb720/890736 Entry at 0x802746f0 Closing network. Starting program at 0x802746f0 GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb panic: running without device atpic requires a local APIC cpuid =3D 0 KDB: stack backtrace: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x0 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff805c2973 stack pointer =3D 0x28:0xffffffff80c9a960 frame pointer =3D 0x28:0xffffffff80c9aa80 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 0 () [ thread pid 0 tid 0 ] Stopped at 0xffffffff805c2973: movzbl (%rdi),%ecx > If that helps your CPU load, try setting this in /boot/loader.conf : > hw.acpi.verbose=3D1 > Turn on verbose debugging information about what ACPI is doing. Done, but it doesn't really result in any additional messages: # dmesg | grep -i acpi Features=3D0xbfebfbff ACPI APIC Table: acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 ACPI Error: [\134_SB_.PCI0.LPC0.BCMD] Namespace lookup failure, AE_NOT_FOUN= D (20130117/psargs-393) ACPI Error: Method parse/execution failed [\134_PR_.CPU0._OSC] (Node 0xffff= fe0007630c00), AE_NOT_FOUND (20130117/psparse-560) ACPI Error: [\134_SB_.PCI0.LPC0.BCMD] Namespace lookup failure, AE_NOT_FOUN= D (20130117/psargs-393) ACPI Error: Method parse/execution failed [\134_PR_.CPU0._OSC] (Node 0xffff= fe0007630c00), AE_NOT_FOUND (20130117/psparse-560) ACPI Error: Method parse/execution failed [\134_PR_.CPU0._PDC] (Node 0xffff= fe0007630c40), AE_NOT_FOUND (20130117/psparse-560) cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 atrtc0: port 0x70-0x71 irq 8 on acpi0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib3: at device 4.0 on pci0 pci3: on pcib3 pcib4: mem 0xdeb00000-0xdeb1ffff irq 16 at device 0.0= on pci3 pci4: on pcib4 pcib7: irq 5 at device 8.0 on pci4 pci7: on pcib7 pcib29: irq 16 at device 28.0 on pci0 pci29: on pcib29 pcib30: irq 16 at device 28.4 on pci0 pci30: on pcib30 pcib31: irq 17 at device 28.5 on pci0 pci31: on pcib31 pcib32: at device 30.0 on pci0 pci32: on pcib32 acpi_button0: on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 Lars