From owner-freebsd-current@FreeBSD.ORG Thu Dec 1 19:48:51 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 B35BE16A41F; Thu, 1 Dec 2005 19:48:51 +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 2563C43D4C; Thu, 1 Dec 2005 19:48:51 +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 D12C41A3C2D; Thu, 1 Dec 2005 11:48:50 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1C15A512D8; Thu, 1 Dec 2005 14:48:50 -0500 (EST) Date: Thu, 1 Dec 2005 14:48:49 -0500 From: Kris Kennaway To: Doug Ambrisko Message-ID: <20051201194849.GA4031@xor.obsecurity.org> References: <200511281626.33591.jhb@freebsd.org> <200512011932.jB1JWAG1014195@ambrisko.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <200512011932.jB1JWAG1014195@ambrisko.com> User-Agent: Mutt/1.4.2.1i Cc: Kris Kennaway , freebsd-current@freebsd.org, Darren Pilgrim 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: Thu, 01 Dec 2005 19:48:51 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 01, 2005 at 11:32:10AM -0800, Doug Ambrisko 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 > Is this is SMP on or off? I think it might be okay if SMP if off. With SMP, I don't recall if I tried it without. SMP is pretty useless on 4.x (often hurts more than it helps), so this may be an acceptable workaround for the OP. Kris --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDj1OhWry0BWjoQKURAlcuAKC76sWt+IHlDjmrzrCORt3uqEgwKgCgp/4V HRk1a0zTBbGZ8CJUUVLEU7c= =rfth -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv--