From owner-freebsd-questions@FreeBSD.ORG Sun Aug 7 23:28:19 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 4923B106566B for ; Sun, 7 Aug 2011 23:28:19 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id F15118FC0A for ; Sun, 7 Aug 2011 23:28:18 +0000 (UTC) Received: by yib19 with SMTP id 19so376287yib.13 for ; Sun, 07 Aug 2011 16:28:18 -0700 (PDT) Received: by 10.236.190.42 with SMTP id d30mr5777203yhn.258.1312759698256; Sun, 07 Aug 2011 16:28:18 -0700 (PDT) Received: from papi.localnet ([187.112.28.27]) by mx.google.com with ESMTPS id j65sm1698388yhm.40.2011.08.07.16.28.15 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 07 Aug 2011 16:28:17 -0700 (PDT) From: Mario Lobo To: bf1783@gmail.com Date: Sun, 7 Aug 2011 20:28:09 -0300 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.2; amd64; ; ) References: In-Reply-To: X-KMail-Markup: true MIME-Version: 1.0 Message-Id: <201108072028.09658.lobo@bsd.com.br> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: High interrupt rate X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2011 23:28:19 -0000 On Sunday 07 August 2011 18:34:27 b. f. wrote: > > 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. Thanks b. ! [~]>sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) ACPI-safe(850) i8254(0) dummy(-1000000) kern.timecounter.hardware: ACPI-safe kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 65535 kern.timecounter.tc.i8254.counter: 39201 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.ACPI-safe.mask: 16777215 kern.timecounter.tc.ACPI-safe.counter: 1055460 kern.timecounter.tc.ACPI-safe.frequency: 3579545 kern.timecounter.tc.ACPI-safe.quality: 850 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 1200011080 kern.timecounter.tc.TSC.frequency: 1995401152 kern.timecounter.tc.TSC.quality: -100 kern.timecounter.smp_tsc: 0 kern.timecounter.invariant_tsc: 1 [~]>sysctl kern.hz kern.hz: 1000 [~]>sysctl kern.eventtimer sysctl: unknown oid 'kern.eventtimer' I'll wait for your views on those before disabling polling on the kernel and hz=100. Thanks again. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winblows FREE)