From owner-freebsd-stable@FreeBSD.ORG Wed Mar 21 23:44:18 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2768106566C for ; Wed, 21 Mar 2012 23:44:18 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id A5AB28FC14 for ; Wed, 21 Mar 2012 23:44:18 +0000 (UTC) Received: from [192.168.43.26] (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.5/8.14.4) with ESMTP id q2LNiHGG030250; Wed, 21 Mar 2012 19:44:17 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <4F6A67C0.7000909@sentex.net> Date: Wed, 21 Mar 2012 19:44:00 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Matt Thyer References: In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.71 on 64.7.153.18 Cc: freebsd-stable@freebsd.org Subject: Re: 157k interrupts per second causing 60% CPU load on idle system 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: Wed, 21 Mar 2012 23:44:19 -0000 On 3/20/2012 1:26 AM, Matt Thyer wrote: > I've upgraded my FreeBSD-STABLE NAS from r225723 (22nd Sept 2011) to > r232477 (4th Mar 2012) and am finding that a system process called "intr" > is now constantly using about 60% of 1 CPU starting a short time after > reboot (possibly triggered by use of the samba server). > > When this starts, systat -vm 1 says that the system is 85% idle and 14% > interrupt handling. > It says that there's around 157k interrupts per second. > > Any idea what could be the cause ? This sounds like the problem I had with my intel board. BIOS update fixed it. What chipset and MB vendor do you have ? /usr/ports/sysutils/dmidecode is handy for digging up BIOS and chipset info http://lists.freebsd.org/pipermail/freebsd-questions/2012-March/239394.html ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/