From owner-freebsd-stable@FreeBSD.ORG Mon Nov 29 01:19:05 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF4AE16A4CE for ; Mon, 29 Nov 2004 01:19:05 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76FAF43D39 for ; Mon, 29 Nov 2004 01:19:05 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAT1MSsQ098471; Sun, 28 Nov 2004 18:22:28 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AA7921.9090703@freebsd.org> Date: Sun, 28 Nov 2004 18:19:29 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Willem Jan Withagen References: <41AA75A5.3050706@withagen.nl> In-Reply-To: <41AA75A5.3050706@withagen.nl> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: stable@freebsd.org Subject: Re: same interrupts on uhc and em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 01:19:05 -0000 Willem Jan Withagen wrote: > Hi, > > Got this intel r1300 dual processor server with 2 Em inerfaces and a lot > of usb ports, 2Gb and en Promise Fastrack TX2000 > > Problem is that when em0 gets an interrupt, it also shows up on the USB > controller. top shows the exact same amounts of interrupt at both every > time over. Which has a lickelyhood of less than zero. > > Is this more common, and if so: what might fix it. > > --WjW This is a common problem, and unfortunately there hasn't been much movement in fixing it. I'd highly suggest disabling USB in the BIOS if you don't need it. Scott