From owner-freebsd-current@FreeBSD.ORG Sun Mar 11 04:40:34 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 77A7316A403 for ; Sun, 11 Mar 2007 04:40:34 +0000 (UTC) (envelope-from tillman@seekingfire.com) Received: from mail.seekingfire.com (thoth.seekingfire.com [24.89.83.9]) by mx1.freebsd.org (Postfix) with ESMTP id 2E2B613C441 for ; Sun, 11 Mar 2007 04:40:34 +0000 (UTC) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id C80CD39850; Sat, 10 Mar 2007 22:40:33 -0600 (CST) Date: Sat, 10 Mar 2007 22:40:33 -0600 From: Tillman Hodgson To: freebsd-current@freebsd.org Message-ID: <20070311044033.GB1256@seekingfire.com> References: <20070308125927.GA1265@seekingfire.com> <20070308204041.GA55240@xor.obsecurity.org> <20070310153206.GF1230@seekingfire.com> <3bbf2fe10703100749h14e9b075wb6d730ed7c9189f8@mail.gmail.com> <20070310161423.GA1256@seekingfire.com> <20070310193946.GA96514@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070310193946.GA96514@xor.obsecurity.org> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.14 (2007-02-12) 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: Sun, 11 Mar 2007 04:40:34 -0000 On Sat, Mar 10, 2007 at 02:39:47PM -0500, Kris Kennaway wrote: > 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, I greatly respect your work and I'm glad to have you involved in the thread. I'm familiar with your email style and while I could be reading you wrong I'm detecting curtness and a bit of hostility in your posts to this thread. I sincerely apologize for being inexperienced at this. I'm a fast learner and I've been involved with FreeBSD for a some time, but that obviously can't compensate for my lack of knowledge in this area. In response to your question, I've already posted to this thread the documents that I looked for and was following and the Developers Handbook wasn't among them. I'll read over it now, of course. Please keep in mind that it has been 56 hours between when I first posted and this post from you. If I'm inexperienced and followed the wrong documentation, great -- someone with kernel debugging experience could point that out to me and I can get to work getting the information the developers need. I don't think it's reasonable to expect someone to leave a machine in the debugger for 56 hours before even getting a pointer to the correct docs though, especially when the problem re-occurs somewhat regularly. Now that I have the documentation that you'd like me to follow (I assume it's section 11.5 and especially 11.9 of the Developers Handbook), it's easiest to simply wait for it to hang again. Shouldn't take more than a day or two to get the info requested in 11.9. I suggest that the doc team be brought into the loop so that the FAQ 5.8 and 18.14 can be updated to point to the correct documentation. This should make it easier for other folks who are looking for the same information, especially since those FAQ entries are both official documentation and one of the top Google hits. -T -- If the world was without any natural evil and suffering we wouldn't have the opportunity, or nearly as much opportunity, to show courage, patience and sympathy. -- Richard Swinburne, _The Philosophers' Magazine_