From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 06:26:26 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 4D11116A41F for ; Thu, 24 Nov 2005 06:26:26 +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 D8AAC43D53 for ; Thu, 24 Nov 2005 06:26:25 +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 C39A91A3C1A; Wed, 23 Nov 2005 22:26:25 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2D1B3515B2; Thu, 24 Nov 2005 01:26:25 -0500 (EST) Date: Thu, 24 Nov 2005 01:26:25 -0500 From: Kris Kennaway To: Stefan Bethke Message-ID: <20051124062624.GA15944@xor.obsecurity.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org 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, 24 Nov 2005 06:26:26 -0000 --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--