From owner-freebsd-current@FreeBSD.ORG Sat Mar 10 19:39:48 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B2BFC16A404 for ; Sat, 10 Mar 2007 19:39:48 +0000 (UTC) (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 9D87813C461 for ; Sat, 10 Mar 2007 19:39:48 +0000 (UTC) (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 78D071A3C1C; Sat, 10 Mar 2007 11:39:48 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5D889513AE; Sat, 10 Mar 2007 14:39:47 -0500 (EST) Date: Sat, 10 Mar 2007 14:39:47 -0500 From: Kris Kennaway To: Tillman Hodgson Message-ID: <20070310193946.GA96514@xor.obsecurity.org> References: <20070308125927.GA1265@seekingfire.com> <20070308204041.GA55240@xor.obsecurity.org> <20070310153206.GF1230@seekingfire.com> <3bbf2fe10703100749h14e9b075wb6d730ed7c9189f8@mail.gmail.com> <20070310161423.GA1256@seekingfire.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <20070310161423.GA1256@seekingfire.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@freebsd.org Subject: Re: Experiencing hangs on SMP box with no console messages given for clues. Details inside. 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: Sat, 10 Mar 2007 19:39:48 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Mar 10, 2007 at 10:14:23AM -0600, Tillman Hodgson wrote: > If I'm understanding what I'm reading, this isn't all that helpful > because it's just saying that I broke into the kernel debugger and then > issued a manual panic (which is true, that's how I got the core). Is > there a way to obtain information on what was happening before I broke > into the debugger? Well you really needed to investigate some things in DDB before rebooting, e.g. the lock states. I thought this was described in the developers handbook - did you look for it? Kris --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF8wmCWry0BWjoQKURAq0GAJ9sQdcMHzLQIEkhEXXX4aWz9CRnigCeJaKi XamwiCmEIaQEcKDjBO4SHOw= =Wd1u -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm--