From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 16 14:12:26 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F17F106566B for ; Tue, 16 Sep 2008 14:12:26 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) by mx1.freebsd.org (Postfix) with ESMTP id BD3828FC14 for ; Tue, 16 Sep 2008 14:12:25 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.17] (helo=7.mx.freenet.de) by mout1.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #65) id 1KfbHz-000813-RE; Tue, 16 Sep 2008 16:12:23 +0200 Received: from m9078.m.pppool.de ([89.49.144.120]:11142 helo=peedub.jennejohn.org) by 7.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #65) id 1KfbHz-0005jI-JB; Tue, 16 Sep 2008 16:12:23 +0200 Date: Tue, 16 Sep 2008 16:12:22 +0200 From: Gary Jennejohn To: "Scott Gasch" Message-ID: <20080916161222.125d15f5@peedub.jennejohn.org> In-Reply-To: References: X-Mailer: Claws Mail 3.5.0 (GTK+ 2.10.14; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: irq19 interrupt storm? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 14:12:26 -0000 On Mon, 15 Sep 2008 22:57:38 -0700 "Scott Gasch" wrote: > Hi, > > I'm running freebsd 7.0-RELEASE-p4 on a 4-core amd64 box. Nearly 100% of > 1 cpu is constantly being used handling irq19: uhci4 interrupts. This > seems to happen both with and without any USB devices plugged in: > > vmstat -i > interrupt total rate > irq1: atkbd0 5 0 > irq6: fdc0 1 0 > irq17: mskc0 dc0 1180547 18 > irq18: skc0 uhci2* 163250699 2512 > irq19: uhci4++ 3187989508 49072 I think the ++ here indicates that two or more devices are sharing this interrupt. Try doing "grep irq.*19 /var/run/dmesg.boot" to see which ones. One of these devices could be the culprit. --- Gary Jennejohn