From owner-freebsd-questions@FreeBSD.ORG Sun Aug 7 21:34:29 2011 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 016981065670 for ; Sun, 7 Aug 2011 21:34:29 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id 5E8798FC15 for ; Sun, 7 Aug 2011 21:34:28 +0000 (UTC) Received: by pzk33 with SMTP id 33so3877294pzk.18 for ; Sun, 07 Aug 2011 14:34:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=Bd6cYsei6NdeeK5xczQDQVQis4JzrX3cYTcMadmm1Qk=; b=sbYNysTJi4bZ1806PVgfNnEtn2SM4ACNKmgI93qiguYT1aFnxyS2tw2EkNoFUNCduC vybTiUvtG6cRBD5evTwwlGJC6JAqHpzvr7Eq7fhl9yJJZ4H6epZGoHcn5Yfg8ajLMbj2 jtPbdFOG/v/GBXL3EiXFbfVpQjDkiM0Ijahcs= MIME-Version: 1.0 Received: by 10.142.48.20 with SMTP id v20mr5144155wfv.115.1312752867853; Sun, 07 Aug 2011 14:34:27 -0700 (PDT) Received: by 10.68.43.133 with HTTP; Sun, 7 Aug 2011 14:34:27 -0700 (PDT) Date: Sun, 7 Aug 2011 17:34:27 -0400 Message-ID: From: "b. f." To: Mario Lobo , freebsd-questions@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: High interrupt rate X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2011 21:34:29 -0000 > > I know 75% idle is not bad but this machine, when not under load on a saturday > night like today, used to be at around 98% idle 99% of the time. Now its is at > 72% idle 99.9% of the time. It has been like this all day. > > The only things with a high interrupt rate are > > cpu0: timer 46922025 2000 > cpu1: timer 46918117 1999 > > What could be causing this? I don't know that 2 timer interrupts per-cpu, per kern.hz, is altogether unexpected for some configurations, under some conditions. What happens if you boot with kern.hz="100" in /boot/loader.conf, or set via the loader command line? What happens if you remove the DEVICE_POLLING option from your kernel (and _not_ just disable polling per-device)? What is the output from "sysctl kern.timecounter kern.eventtimer"? b.