From owner-freebsd-current@FreeBSD.ORG Mon Jun 20 07:02:25 2011 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B013106566B; Mon, 20 Jun 2011 07:02:25 +0000 (UTC) (envelope-from ache@vniz.net) Received: from vniz.net (vniz.net [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id 99D468FC15; Mon, 20 Jun 2011 07:02:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vniz.net (8.14.4/8.14.4) with ESMTP id p5K72MxT075199; Mon, 20 Jun 2011 11:02:22 +0400 (MSD) (envelope-from ache@vniz.net) Received: (from ache@localhost) by localhost (8.14.5/8.14.5/Submit) id p5K72MjK075197; Mon, 20 Jun 2011 11:02:22 +0400 (MSD) (envelope-from ache) Date: Mon, 20 Jun 2011 11:02:22 +0400 From: Andrey Chernov To: "Justin T. Gibbs" Message-ID: <20110620070222.GA74009@vniz.net> Mail-Followup-To: Andrey Chernov , "Justin T. Gibbs" , Eir Nym , current@FreeBSD.ORG, "Kenneth D. Merry" , will@FreeBSD.ORG References: <20110619160148.GA35431@vniz.net> <20110619165328.GA35872@vniz.net> <20110619232307.GA57530@vniz.net> <20110620001912.GA60252@vniz.net> <4DFEAD4F.1040603@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DFEAD4F.1040603@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Eir Nym , "Kenneth D. Merry" , current@FreeBSD.ORG, will@FreeBSD.ORG Subject: Re: Exactly that commit (was Re: Latest -current 100% hang at the late boot stage) 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: Mon, 20 Jun 2011 07:02:25 -0000 On Sun, Jun 19, 2011 at 08:15:43PM -0600, Justin T. Gibbs wrote: > On 6/19/11 6:19 PM, Andrey Chernov wrote: > > Exactly that commit is responsible for boot hang. > > Please fix. > > BTW, I have MBR on SATA disk (CAM emulated), ICH9. > > Since it works for me, you'll need to provide more information. Can you > at least drop into kdb to determine the likely source of the hang by > getting a stack trace of all processes to see where they are sleeping > and dumping lock information? I drop into DDB and put 'bt' console photo in the very first message of this thread - nothing unusual seen in the main stack. Could you please specify exact DDB commands you want to be issued by me? No dump can be provided since nothing is mounted yet including swap, BTW, I remember I saw previously unseen warnings with post Jun 14 kernels: "xpt_action_default: CCB type 0xe not supported" 'ps' inside DDB shows [xpt_thrd] at "ccb_scan" wmesg state and [g_event] at "caplck" wmesg state, [kernel] at "g_waitid" state. Even don't know, if it matters. -- http://ache.vniz.net/