From owner-freebsd-current@FreeBSD.ORG  Thu Nov 24 07:14:08 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 36F6316A41F
	for <freebsd-current@freebsd.org>; Thu, 24 Nov 2005 07:14:08 +0000 (GMT)
	(envelope-from barney@pit.databus.com)
Received: from pit.databus.com (p72-0-224-2.acedsl.com [72.0.224.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6662D43D58
	for <freebsd-current@freebsd.org>; Thu, 24 Nov 2005 07:14:07 +0000 (GMT)
	(envelope-from barney@pit.databus.com)
Received: from pit.databus.com (localhost [127.0.0.1])
	by pit.databus.com (8.13.4/8.13.4) with ESMTP id jAO7E6Bg022454;
	Thu, 24 Nov 2005 02:14:06 -0500 (EST)
	(envelope-from barney@pit.databus.com)
Received: (from barney@localhost)
	by pit.databus.com (8.13.4/8.13.3/Submit) id jAO7E6A3022453;
	Thu, 24 Nov 2005 02:14:06 -0500 (EST) (envelope-from barney)
Date: Thu, 24 Nov 2005 02:14:06 -0500
From: Barney Wolff <barney@databus.com>
Message-ID: <20051124071405.GA15743@pit.databus.com>
References: <002801c5f081$f01ff200$642a15ac@smiley>
	<4384F807.6050105@samsco.org>
	<14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de>
User-Agent: Mutt/1.5.11
Cc: freebsd-current@freebsd.org
Subject: Re: em interrupt storm
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2005 07:14:08 -0000

I've observed the interrupt aliasing problem on an Asus A7M266-D
with 2 Athlon 2200-MPs, so it's not confined to the Intel chipset.
Here's the evidence (there is nothing connected to ehci0):
lab:/home/barney $ vmstat -i
interrupt                          total       rate
irq6: fdc0                            10          0
irq13: npx0                            1          0
irq14: ata0                     12380884          6
irq15: ata1                           58          0
irq16: ehci0                   212494994        109
irq17: pcm0                      4551325          2
irq18: ohci1                     4275754          2
irq19: fxp0 ohci0+                124765          0
irq20: em0                     210064498        108
irq21: ahc0                      4245565          2
irq22: ahc1                      4261858          2
cpu0: timer                   3877840775       1999
cpu1: timer                   3877813525       1999
Total                         8208054012       4233
lab:/home/barney $ uname -a
FreeBSD lab.databus.com 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu Oct 20 16:16:12 EDT 2005     toor@lab.databus.com:/usr/obj/usr/src/sys/LAB  i386

It's been there for a long time - I just assumed it was a hw issue.

-- 
Barney Wolff         http://www.databus.com/bwresume.pdf
I never met a computer I didn't like.