From owner-freebsd-current@FreeBSD.ORG Wed Feb 20 09:39:01 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 35EEC5DF; Wed, 20 Feb 2013 09:39:01 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by mx1.freebsd.org (Postfix) with ESMTP id 11886F42; Wed, 20 Feb 2013 09:39:00 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,699,1355126400"; d="scan'208";a="242733681" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx1-out.netapp.com with ESMTP; 20 Feb 2013 01:39:00 -0800 Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r1K9d07G026610; Wed, 20 Feb 2013 01:39:00 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0328.009; Wed, 20 Feb 2013 01:38:59 -0800 From: "Eggert, Lars" To: Adrian Chadd Subject: Re: system 20% busy at all times? Thread-Topic: system 20% busy at all times? Thread-Index: AQHODoSUIkOKNPDzb0yS23V/tl+kl5iBc1WAgAABSACAAAKwgIAABj+AgAABMwCAAAHkAIAADReAgAAQIgCAAADlAIAABhMAgAAOCwCAADrggIABF46A Date: Wed, 20 Feb 2013 09:38:58 +0000 Message-ID: References: <36DD2FB4-E26A-4F03-95D9-FFD855957269@my.gd> <8F861CF6-D0FA-4BD2-B73D-24CB247584A1@my.gd> <51235EA7.6000208@FreeBSD.org> <20130219121544.GU83110@e-new.0x20.net> In-Reply-To: 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="iso-8859-1" Content-ID: <02863F937BB2814EB100AD2CC282CB8A@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Lars Engels , "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: Wed, 20 Feb 2013 09:39:01 -0000 Hi, On Feb 19, 2013, at 17:58, Adrian Chadd wrote: > Try top -HS .. to try and break down the kernel threads. ACPI is eating the cycles, according to top: 0 root 8 0 0K 496K - 2 1:13 27.88% kernel{acpi= _task_2} 0 root 8 0 0K 496K - 0 1:13 25.68% kernel{acpi= _task_1} 0 root 8 0 0K 496K CPU1 1 1:07 23.68% kernel{acpi= _task_0} I got an off-list hint that the machine in question requires "device mptabl= e" instead of relying on ACPI. I will try that. As for dtrace, a complete buildworld/installworld cycle didn't change thing= s, I still get: # dtrace -n 'syscall:::entry { @num[execname] =3D count(); }' dtrace: invalid probe specifier syscall:::entry { @num[execname] =3D count(= ); }: "/usr/lib/dtrace/psinfo.d", line 90: failed to resolve type kernel`st= ruct thread * for identifier curthread: Module is no longer loaded Thanks for all the help! Lars=