From owner-freebsd-stable@FreeBSD.ORG Sun Apr 29 14:29:28 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BCA8A1065672; Sun, 29 Apr 2012 14:29:28 +0000 (UTC) (envelope-from kozlov@ravenloft.kiev.ua) Received: from ravenloft.kiev.ua (ravenloft.kiev.ua [94.244.131.95]) by mx1.freebsd.org (Postfix) with ESMTP id 71ABE8FC0C; Sun, 29 Apr 2012 14:29:28 +0000 (UTC) Date: Sun, 29 Apr 2012 17:29:27 +0300 From: Alex Kozlov To: Alexander Motin , freebsd-stable@freebsd.org Message-ID: <20120429142927.GA59818@ravenloft.kiev.ua> References: <4F9CCEF2.6050609@FreeBSD.org> <20120429155512.M91148@sola.nimnet.asn.au> <4F9CDE91.1060300@FreeBSD.org> <4F9D2F0C.4050501@FreeBSD.org> <20120429122714.GA56829@ravenloft.kiev.ua> <4F9D3DF8.9000800@FreeBSD.org> <20120429133056.GA58422@ravenloft.kiev.ua> <4F9D4491.2060007@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F9D4491.2060007@FreeBSD.org> Cc: Subject: Re: High load event idl. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2012 14:29:28 -0000 On Sun, Apr 29, 2012 at 04:39:29PM +0300, Alexander Motin wrote: > On 04/29/12 16:30, Alex Kozlov wrote: > > On Sun, Apr 29, 2012 at 04:11:20PM +0300, Alexander Motin wrote: > >> On 04/29/12 15:27, Alex Kozlov wrote: > >>> On Sun, Apr 29, 2012 at 03:07:40PM +0300, Alexander Motin wrote: > >>>> On 04/29/12 15:04, Oliver Pinter wrote: > >>>>> Removing dummynet from kernel don't chanage anything, that is releated > >>>>> to load average. The loadavg hold to 0.70 +/- 0.2. (single user : sh + > >>>>> top) > >>>> > >>>> New ktr dump? > >>> I have similar issue on one of my laptops. Should I provide ktr dump? > >>> http://lists.freebsd.org/pipermail/freebsd-current/2011-September/027133.html > >> In your case HPET also shares interrupt with other devices. I suspect > >> that may be a reason. Every time when swi thread runs loadavg, other CPU > >> runs shared interrupt handler, that is accounted as result. Please show > >> your verbose dmesg. > > Attached. > In your case HPET could solely use IRQ22 that seems free now. After > recent changes in ACPI code it is detected before PCI devices and so > doesn't avoids sharing. You may try to hint it specific IRQ by adding to > loader,conf line: > hint.hpet.0.allowed_irqs="0x00400000" Thanks, it helped. Still it would be nice, if loadavg accounting was fixed. -- Adios