From owner-freebsd-current@FreeBSD.ORG Tue Feb 19 10:21:21 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4F0B8EFE for ; Tue, 19 Feb 2013 10:21:21 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id D9C79201 for ; Tue, 19 Feb 2013 10:21:20 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id o1so4579317wic.11 for ; Tue, 19 Feb 2013 02:21:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=CzgsnYXrHYRRs2uCN+6jJJtLv2lDz6O4ixc0Y//4cvs=; b=VFJDPtQPTSnSy6RhkYMOYjZLMohjoy0QNX2szyb4GkAmZjCgoKmckdFF3Wlji5U2x/ UBXnJ823gZSWogCMjqxA3I2YPMuCoeAPTDAl0iH9Cctcf+06BFzSYtp27d/hZh4AQtFu VDSKpV6xlfoYDJY04fZQLhzisr+hfWbzY971dm0o3QxeYduH0MF/cfPncUb9ndsz9WiP 0fNXIAIPhWxFyDgXQV+DBetWz8P7oTcEH1W3Mrgkx3g6ASYhOBhsUsr1PNJbuiAu4SIu Z5olwGEseD7uXZSmOvaOzyJdG8WY8YO81evafCkQdiGY8Pnv5IBRuoGg6dugJOCpUjqz YWbA== X-Received: by 10.194.108.229 with SMTP id hn5mr25169313wjb.8.1361269270142; Tue, 19 Feb 2013 02:21:10 -0800 (PST) Received: from dfleuriot-at-hi-media.com ([83.167.62.196]) by mx.google.com with ESMTPS id m6sm26829947wic.2.2013.02.19.02.21.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Feb 2013 02:21:09 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: system 20% busy at all times? From: Fleuriot Damien In-Reply-To: Date: Tue, 19 Feb 2013 11:21:10 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8F861CF6-D0FA-4BD2-B73D-24CB247584A1@my.gd> References: <36DD2FB4-E26A-4F03-95D9-FFD855957269@my.gd> To: "Eggert, Lars" X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQnKBeGpQjKMBgNTLR4yETf+FRpKPiSk0q4bKn9RSeLge9mRdzLOL13ySaYkGHR+AD0qOMg5 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:21:21 -0000 On Feb 19, 2013, at 11:16 AM, "Eggert, Lars" wrote: > Hi, >=20 > 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 = blabla.." >=20 > nope. The only odd ACPI-related messages I see in dmesg are these: >=20 > ACPI Error: [\134_SB_.PCI0.LPC0.BCMD] Namespace lookup failure, = AE_NOT_FOUND (20130117/psargs-393) > ACPI Error: Method parse/execution failed [\134_PR_.CPU0._OSC] (Node = 0xfffffe0007630c00), AE_NOT_FOUND (20130117/psparse-560) > ACPI Error: [\134_SB_.PCI0.LPC0.BCMD] Namespace lookup failure, = AE_NOT_FOUND (20130117/psargs-393) > ACPI Error: Method parse/execution failed [\134_PR_.CPU0._OSC] (Node = 0xfffffe0007630c00), AE_NOT_FOUND (20130117/psparse-560) > ACPI Error: Method parse/execution failed [\134_PR_.CPU0._PDC] (Node = 0xfffffe0007630c40), AE_NOT_FOUND (20130117/psparse-560) >=20 > Nothing in syslog. >=20 >> =46rom 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 = disabled >> on your system due to a blacklist entry for your BIOS, you = can >> set this to 0 to re-enable ACPI for testing. >>=20 >> Any chance you could reboot the host with ACPI disabled ? >=20 > If I do that, I get an early kernel crash: >=20 > Loading 10.11.12.13/~elars/kernel/kernel:0x200000/7634255 = 0xb47d50/473552 0xbbb720/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 >=20 >=20 > 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 >=20 >=20 >> 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. >=20 > Done, but it doesn't really result in any additional messages: >=20 > # 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_FOUND (20130117/psargs-393) > ACPI Error: Method parse/execution failed [\134_PR_.CPU0._OSC] (Node = 0xfffffe0007630c00), AE_NOT_FOUND (20130117/psparse-560) > ACPI Error: [\134_SB_.PCI0.LPC0.BCMD] Namespace lookup failure, = AE_NOT_FOUND (20130117/psargs-393) > ACPI Error: Method parse/execution failed [\134_PR_.CPU0._OSC] (Node = 0xfffffe0007630c00), AE_NOT_FOUND (20130117/psparse-560) > ACPI Error: Method parse/execution failed [\134_PR_.CPU0._PDC] (Node = 0xfffffe0007630c40), 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 >=20 Jeez, I certainly hope people more knowledgeable than me about the = kernel will be able to make something of all this. What about a newly build kernel without the line "device acpi" and = without the options ACPI_DEBUG ? Hoping that this kernel: 1/ won't crash on boot 2/ will make the 20% cpu load and high interrupt rates disappear