From owner-freebsd-stable@FreeBSD.ORG Wed Mar 19 18:06:30 2008 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 61960106566B for ; Wed, 19 Mar 2008 18:06:29 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 595998FC12 for ; Wed, 19 Mar 2008 18:06:29 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 481971CC060; Wed, 19 Mar 2008 11:06:29 -0700 (PDT) Date: Wed, 19 Mar 2008 11:06:29 -0700 From: Jeremy Chadwick To: freebsd-stable@FreeBSD.ORG, root@ha-web1.hockeyarena.net Message-ID: <20080319180629.GA29308@eos.sc1.parodius.com> References: <669936444.20080319100148@rulez.sk> <200803191753.m2JHraI5092556@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200803191753.m2JHraI5092556@lurza.secnetix.de> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Subject: Re: Weird system cpu usage 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, 19 Mar 2008 18:06:30 -0000 On Wed, Mar 19, 2008 at 06:53:36PM +0100, Oliver Fromme wrote: > Charlie Root wrote: > > root@[ha-web1 ~]# vmstat -i > > interrupt total rate > > irq1: atkbd0 12 0 > > irq16: ohci0 1 0 > > irq17: ohci1 ohci3 1 0 > > irq18: ohci2 ohci4 1 0 > > irq20: em0 86255835 1361 > > irq22: em1 atapci0 18611379049 293795 > > Now that looks unusual indeed. Do you get that rate > on irq22 right after boot, before the services have > started? It looks like either hardware or driver > problems. Do you have polling enabled on em1? Also, I believe there was a report from another user who saw similar issues with em(4), and found that disabling MSI fixed the storm in question. I believe you can disable MSI/MSIX by placing the following in /boot/loader.conf, then reboot: hw.pci.enable_msi="0" hw.pci.enable_msix="0" -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |