From owner-freebsd-stable@FreeBSD.ORG Thu Jul 7 11:53:06 2011 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 ED0211065670 for ; Thu, 7 Jul 2011 11:53:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 418358FC1A for ; Thu, 7 Jul 2011 11:53:06 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA19961; Thu, 07 Jul 2011 14:52:56 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E159E18.7070903@FreeBSD.org> Date: Thu, 07 Jul 2011 14:52:56 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Jeremy Chadwick References: <4E154A63.90600@sentex.net> <4E15620A.9030608@FreeBSD.org> <20110707082027.GX48734@deviant.kiev.zoral.com.ua> <4E159959.2070401@sentex.net> <20110707114122.GA8459@icarus.home.lan> In-Reply-To: <20110707114122.GA8459@icarus.home.lan> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , FreeBSD-STABLE Mailing List Subject: Re: panic: spin lock held too long (RELENG_8 from today) 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: Thu, 07 Jul 2011 11:53:07 -0000 on 07/07/2011 14:41 Jeremy Chadwick said the following: > 1. info threads > 2. Find the index value that matches the tid in question (in the above > spin lock panic, that'd be tid 100109). The index value will be > the first number shown on the left > 3. thread {index} Just in case, in kgdb there is a command 'tid' that does all of the above steps in one go. > 4. bt > > If this doesn't work, alternatively you can try (from the beginning) > "thread apply all bt" and provide the output from that. (It will be > quite lengthy, and at this point I think tid 100109 is the one of > interest in this crash, based on what Andriy said earlier) -- Andriy Gapon