From owner-freebsd-ia64@FreeBSD.ORG Wed Oct 23 18:57:11 2013 Return-Path: Delivered-To: freebsd-ia64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3B991B95; Wed, 23 Oct 2013 18:57:11 +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 1523A2553; Wed, 23 Oct 2013 18:57:11 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 279ADB93B; Wed, 23 Oct 2013 14:57:10 -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 14:56:56 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <201310231756.r9NHu1T9006700@mech-cluster241.men.bris.ac.uk> In-Reply-To: <201310231756.r9NHu1T9006700@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201310231456.56359.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 23 Oct 2013 14:57:10 -0400 (EDT) Cc: davide@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-ia64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the IA-64 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 18:57:11 -0000 On Wednesday, October 23, 2013 1:56:01 pm Anton Shterenlikht wrote: > >From jhb@freebsd.org Wed Oct 23 16:54:12 2013 > > > >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? > > No. I have another deadlock panic when savecore > is running. That panic dumps core, then on reboot > when savecore is running I get another deadlock > panic, and so on. However, I do get about 8-10gb vmcore* > files before the panic happens. Presumably these > are truncated somehow. > Do you think these incomplete vmcores can still > be useful? If you send some instructions on what > to try, I'll give it a go, or I can post a vmcore > somewhere. Does you get corresponding core.txt.N files from crashinfo? -- John Baldwin