From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 14:49:40 2004 Return-Path: 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 7E44C16A4CE for ; Sun, 12 Sep 2004 14:49:40 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E3B443D54 for ; Sun, 12 Sep 2004 14:49:40 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i8CEnSht052394; Sun, 12 Sep 2004 10:49:28 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i8CEnSo2052391; Sun, 12 Sep 2004 10:49:28 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 12 Sep 2004 10:49:28 -0400 (EDT) From: Andre Guibert de Bruet To: sam In-Reply-To: <4140FF73.7090800@authtec.net> Message-ID: <20040912104104.R84468@alpha.siliconlandmark.com> References: <4140FF73.7090800@authtec.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: Current crash with db prompt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 12 Sep 2004 14:49:40 -0000 On Fri, 10 Sep 2004, sam wrote: > After updated the source dated as (09-09-2004), and finished make buildworkd, > and installkernel, the system crashed into a db> prompt. > Does anyone had this problem? should I download the source again? I m not > sure whether I download the source in a bad time or not.. Getting to the db> prompt isn't of interest, it is the messages that are printed at the console right before you are dropped to the kernel debugger that we are after. They usually give a pretty good idea of what went wrong. Downloading fresher sources may or may not resolve your problem, depending upon whether the bug was caught and fixed or masked by another commit. In the future, please attach the panic string along with any messages printed at panic time with your bug report. You might be interested in setting up a serial console to capture these messages without writing everything down manually. There's a detailed section in the handbook on how to do this. Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >