From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 20 04:35:07 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D760516A4DD for ; Thu, 20 Jul 2006 04:35:07 +0000 (UTC) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 656C043D45 for ; Thu, 20 Jul 2006 04:35:07 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) by blake.polstra.com (8.13.6/8.13.6) with ESMTP id k6K4Z2SR019069; Wed, 19 Jul 2006 21:35:03 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <44BB9D21.3010400@dial.pipex.com> Date: Wed, 19 Jul 2006 21:35:02 -0700 (PDT) From: John Polstra To: Alex Zbyslaw Cc: freebsd-hackers@freebsd.org Subject: RE: [Fwd: Interrupts question] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 04:35:07 -0000 On 17-Jul-2006 Alex Zbyslaw wrote: > I was monitoring a machine with "systat -vmstat" and noticed something > about the interrupts and I don't know if it's a problem or not. If it > is a problem, is there anything I can do about it? > > The interrupts for the network interface (em0) on irq 64 exactly match > those for a uhc device on irq 16. > > And the interrupts for the hardware raid (amr) on irq 46 exactly match > those for a uhc device on irq 18. The problem involving the "em" device was solved in -current around January by making the device use a fast interrupt handler. If you can update to the latest driver from -current (if it will build on whatever version you are running), you can solve that part of the problem. I don't think there's an equivalent fix for the "amr" driver, though. John