From owner-freebsd-stable@FreeBSD.ORG Fri Nov 7 22:07:40 2008 Return-Path: Delivered-To: FreeBSD-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3F2110656A4 for ; Fri, 7 Nov 2008 22:07:39 +0000 (UTC) (envelope-from rorya+freebsd.org@TrueStep.com) Received: from Tserver.TrueStep.com (Tserver.TrueStep.com [64.253.96.188]) by mx1.freebsd.org (Postfix) with ESMTP id 9D91C8FC1D for ; Fri, 7 Nov 2008 22:07:39 +0000 (UTC) (envelope-from rorya+freebsd.org@TrueStep.com) Received: from Cypher.TrueStep (Cypher.TrueStep [10.101.1.8]) (authenticated bits=0) by Tserver.TrueStep.com (8.14.2/8.14.2) with ESMTP id mA7M7TrQ046605 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 7 Nov 2008 17:07:34 -0500 (EST) (envelope-from rorya+freebsd.org@TrueStep.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=TrueStep.com; s=default; t=1226095655; bh=t3Ayud9UjfkaiPaJ+9YhBouOLUqRaIlIcWijKAz N7ww=; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References; b=Mk9B34brUWKLcmMIPHqXLk0GzeRzviXh40yUatg7grG2JJiLTVmMEi+/pehWkCBbe ZY8xHNGMssX46Q5A8+CshkIzVRCotN0PMQgjt1blAug26e96am15Uui9tOduX51VQwe QTN+Dl1tPFCxiRhK5tEiP6UyZl2Ah9m7F7mIZPk= Message-Id: <510F0121-0E24-42C0-BC77-D61DF9FEA46C@TrueStep.com> From: Rory Arms To: Ken Smith In-Reply-To: <1226078239.37011.37.camel@bauer.cse.buffalo.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Fri, 7 Nov 2008 17:07:29 -0500 References: <9592E887-75F3-473F-9581-F9C22A9936A6@TrueStep.com> <1226078239.37011.37.camel@bauer.cse.buffalo.edu> X-Mailer: Apple Mail (2.929.2) Cc: FreeBSD-stable@FreeBSD.org Subject: Re: 6.4-RC2 crashes after a few minutes of uptime X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2008 22:07:40 -0000 On 2008-11-07, at 12:17 , Ken Smith wrote: > On Fri, 2008-11-07 at 00:00 -0500, Rory Arms wrote: >> Well, if I can assist with further debugging, let me know. > > The person who followed up with a list of things that *may* have made > the problem go away mentioned one of the things was disabling powerd. > Do you have that enable, and if yes would you mind disabling it to see > if that's the culprit? Hi Ken, No, it's not running powerd. Looking at the process list, it looks like GNOME has some power related processes, but I assume that's different. I don't think I'd ever even heard of powerd till now, and have now read the manual to learn about it. Well, I wonder if the panic I had yesterday a few minutes after booting RC2 was a fluke. The computer has been running so far without problems, using GNOME, on that second RC2 bootup, for almost 24 hours now. However, I still find it concerning that kgdb(1) on 6.4, hasn't been able to open any of the core dump though. If this is broken, it will be difficult to provide bug reports. I wonder if it's just something about this particular code path to panic, that's generating this, I guess, corrupt core file. Is there a key sequence, or sysctl knob perhaps, that I can use to force an artificial panic to see if the coredump generated is any different? - rory