Date: Thu, 24 Nov 2005 01:27:11 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Darren Pilgrim <dmp@bitfreak.org> Cc: freebsd-current@freebsd.org, 'Kris Kennaway' <kris@obsecurity.org> Subject: Re: em interrupt storm Message-ID: <20051124062711.GA15961@xor.obsecurity.org> In-Reply-To: <002801c5f081$f01ff200$642a15ac@smiley> References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley>
next in thread | previous in thread | raw e-mail | index | archive | help
--mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 the > problem exist in RELENG_4? Yes, on the same machine I first mentioned. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhV0/Wry0BWjoQKURAt4KAJ4zpYsWNW72WMIzjYOwu60RoKJyfACgsuWS ERRlxQOPs2iwLE4xFNwXvu8= =FSlf -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051124062711.GA15961>