Date: Thu, 24 Nov 2005 01:26:25 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Stefan Bethke <stb@lassitu.de> Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm Message-ID: <20051124062624.GA15944@xor.obsecurity.org> In-Reply-To: <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 06:24:17AM +0100, Stefan Bethke wrote: > Am 24.11.2005 um 00:15 schrieb Scott Long: >=20 > >I've directly observed it on 7501WV2 and 7520BD2 boards. I don't =20 > >know if it's a problem that will affect other board configurations =20 > >or cousin chipsets like the 7505 and 7525. >=20 > We've got a Tyan i7501 Pro that we have had stability issues with =20 > since the beginning. Is it thinkable that the interrupt masking =20 > could lead to a hard lock (no break to debugger possible)? Sounds like a different problem. Enable KDB_STOP_NMI in your kernel, which should let you break to DDB. Kris --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhV0QWry0BWjoQKURApE3AKCyHGk5MoV0PsDCdoYVQq5uLOlsnACfaTCz oXaEtrAYyOw0kDXXGCQ2EN8= =SQyC -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051124062624.GA15944>