From owner-freebsd-current@FreeBSD.ORG Wed Oct 23 14:30:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0024DE02; Wed, 23 Oct 2013 14:30:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CCB062366; Wed, 23 Oct 2013 14:30:40 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 60508B93B; Wed, 23 Oct 2013 10:30:37 -0400 (EDT) From: John Baldwin To: freebsd-ia64@freebsd.org, mexas@bris.ac.uk Subject: Re: deadlkres: possible deadlock detected for 0xe000000012aed200, blocked for 900014 ticks Date: Wed, 23 Oct 2013 08:36:19 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <201310230927.r9N9RAw5079054@mech-cluster241.men.bris.ac.uk> In-Reply-To: <201310230927.r9N9RAw5079054@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201310230836.19524.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 23 Oct 2013 10:30:37 -0400 (EDT) Cc: davide@freebsd.org, Konstantin Belousov , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 23 Oct 2013 14:30:41 -0000 On Wednesday, October 23, 2013 5:27:10 am Anton Shterenlikht wrote: > This time alllocks has lots of info. > > I updated the PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007 Hmm, unfortunately it seems like all the stack traces did not work. There are lots of threads blocked on VM-related locks, and CPU 0 is running vm_daemon. Probably would need a stack trace of that thread to see what it is doing (this is part of why a real crash dump would be far better than a textdump as you can get more info after the crash instead of having to know in advance everything you want). I saw earlier you had a thread to get textdumps to work. Did you ever have regular crashdumps working? -- John Baldwin