From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 08:47:03 2005 Return-Path: X-Original-To: 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 DA60E16A41F; Wed, 23 Nov 2005 08:47:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FB7A43D6B; Wed, 23 Nov 2005 08:46:58 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 12E651A3C1C; Wed, 23 Nov 2005 00:46:54 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6DE1751593; Wed, 23 Nov 2005 03:46:53 -0500 (EST) Date: Wed, 23 Nov 2005 03:46:53 -0500 From: Kris Kennaway To: John Polstra Message-ID: <20051123084653.GA90927@xor.obsecurity.org> References: <20051123030304.GA84202@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: net@freebsd.org, current@freebsd.org, Kris Kennaway 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 08:47:04 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote: >=20 > On 23-Nov-2005 Kris Kennaway wrote: > > I am seeing the em driver undergoing an interrupt storm whenever the > > amr driver receives interrupts. In this case I was running newfs on > > the amr array and em0 was not in use: > >=20 > > 28 root 1 -68 -187 0K 8K CPU1 1 0:32 53.98% irq16= : em0 > > 36 root 1 -64 -183 0K 8K RUN 1 0:37 27.75% irq24= : amr0 > >=20 > ># vmstat -i > > interrupt total rate > > irq1: atkbd0 2 0 > > irq4: sio0 199 1 > > irq6: fdc0 32 0 > > irq13: npx0 1 0 > > irq14: ata0 47 0 > > irq15: ata1 931 5 > > irq16: em0 6321801 37187 > > irq24: amr0 28023 164 > > cpu0: timer 337533 1985 > > cpu1: timer 337285 1984 > > Total 7025854 41328 > >=20 > > When newfs finished (i.e. amr was idle), em0 stopped storming. > >=20 > > MPTable: >=20 > This is the dreaded interrupt aliasing problem that several of us have > experienced with this chipset. High-numbered interrupts alias down to > interrupts in the range 16..19 (or maybe 16..23), a multiple of 8 less > than the original interupt. >=20 > Nobody knows what causes it, and nobody knows how to fix it. This would be good to document somewhere so that people don't either accidentally buy this hardware, or know what to expect when they run it. Kris --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhCx8Wry0BWjoQKURAoSZAJ45iXxWGfFc7G8++HwAmr9wAD0OpgCfQp4t pDBtasCrA64KmsHmt8UqJ3M= =2hmE -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP--