From owner-freebsd-current@FreeBSD.ORG Sat Jan 21 17:13:38 2006 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 C97FE16A41F for ; Sat, 21 Jan 2006 17:13:38 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 609EF43D45 for ; Sat, 21 Jan 2006 17:13:38 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp6-g19.free.fr (Postfix) with ESMTP id 7B08917EF1 for ; Sat, 21 Jan 2006 18:13:37 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id k0LHDU1w012544; Sat, 21 Jan 2006 18:13:32 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Sat, 21 Jan 2006 18:13:22 +0100 User-Agent: KMail/1.9.1 References: <200601211159.50768.nb_root@videotron.ca> In-Reply-To: <200601211159.50768.nb_root@videotron.ca> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200601211813.23782.thierry@herbelot.com> Cc: Nicolas Blais Subject: Re: -CURRENT freeze at boot after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2006 17:13:38 -0000 Le Saturday 21 January 2006 17:59, Nicolas Blais a écrit : > Hi, > [SNIP freeze] one way to gather more info is to boot the kernel in verbose mode (-v) - you could know where some probe is broken (then, cross-check with the latest CVS commits). another more involved way would be to boot directly in DDB, and proceed from there. TfH