Date: Mon, 28 Nov 2005 16:55:11 -0500 From: Kris Kennaway <kris@obsecurity.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org, Darren Pilgrim <dmp@bitfreak.org>, Kris Kennaway <kris@obsecurity.org> Subject: Re: em interrupt storm Message-ID: <20051128215511.GA29717@xor.obsecurity.org> In-Reply-To: <200511281626.33591.jhb@freebsd.org> References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley> <20051124062711.GA15961@xor.obsecurity.org> <200511281626.33591.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051128215511.GA29717>