From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 21:55:12 2005 Return-Path: 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 A4D7F16A41F; Mon, 28 Nov 2005 21:55:12 +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 5B73A43D5F; Mon, 28 Nov 2005 21:55:12 +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 401971A3C28; Mon, 28 Nov 2005 13:55:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9799F515B3; Mon, 28 Nov 2005 16:55:11 -0500 (EST) Date: Mon, 28 Nov 2005 16:55:11 -0500 From: Kris Kennaway To: John Baldwin Message-ID: <20051128215511.GA29717@xor.obsecurity.org> References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley> <20051124062711.GA15961@xor.obsecurity.org> <200511281626.33591.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline In-Reply-To: <200511281626.33591.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, Darren Pilgrim , 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: Mon, 28 Nov 2005 21:55:12 -0000 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 04:26:32PM -0500, John Baldwin wrote: > On Thursday 24 November 2005 01:27 am, Kris Kennaway wrote: > > On Wed, Nov 23, 2005 at 03:02:05PM -0800, Darren Pilgrim wrote: > > > Until this gets "fixed" in FreeBSD, what should those of us who are > > > effectively stuck with this hardware do to avoid the problem? Does t= he > > > problem exist in RELENG_4? > > > > Yes, on the same machine I first mentioned. >=20 > This is the first I've heard that the problem occurs on 4.x as well. :( Yeah..maybe the problem is not what was first believed, since that would apparently exclude 4.x? Kris --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDi3y/Wry0BWjoQKURAvDLAKDjhve63sD7K9sHKHDTmoKoNlTfkwCgku0Q xCKkNgtzyAV0iB7FQKoHgmI= =KGRw -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--