From owner-freebsd-ia64@FreeBSD.ORG Thu Oct 24 10:09:55 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 D5E1A636 for ; Thu, 24 Oct 2013 10:09:55 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog125.obsmtp.com (eu1sys200aog125.obsmtp.com [207.126.144.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 38AAA2E66 for ; Thu, 24 Oct 2013 10:09:55 +0000 (UTC) Received: from mail-wi0-f179.google.com ([209.85.212.179]) (using TLSv1) by eu1sys200aob125.postini.com ([207.126.147.11]) with SMTP ID DSNKUmjx18yp2CZ4GKRxB0HJ7K8571ffr4cT@postini.com; Thu, 24 Oct 2013 10:09:55 UTC Received: by mail-wi0-f179.google.com with SMTP id hm4so2255904wib.12 for ; Thu, 24 Oct 2013 03:09:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:message-id:to:subject:cc :reply-to:in-reply-to; bh=dd7jy65KQtV29O9gAJK71Vgp3mDjybHJricw+Xv3SRc=; b=R7VTGra6aqiiMHJnPBm+3L6ubNwh9IJ/vVtLEBcTeAjQrTyFogVbk9pVOgxZk+if4I 0AH3GMyky89xqmQxFoY+et73dcxfhQXlu/eOujwu3D35n0xR03tYUuj1SrCJCE+s/OW5 yvukiPhn9yDdyHJgH/qNht3b78i1DLbTFJQrCJHr/byTSIHe7izm44aLIL5Yr3j3FYGs LazOKYg4C5eQ8u6v+NT388G4ZLynzEXRRm/UV36DOAJv/uwQpB/DW0RfZ/SmZGV/n3Cn 982dke36n/HePqJWDNnsUaFgEPZQlAYmc5EjDjO9IbapvLMTjcvl352PQ+sA8Fprw2u1 bXuQ== X-Gm-Message-State: ALoCoQkEvok4LopMrLv3U16/pWEpUJSBexws8cEMk8PAJTEE7s8MO0tfoPUGiLCa8igmQuv8DZBqWCpsvaC1W4u0bAPJNEPn6z8Xp0Q27ZdcLsPUUrp0ANLFXkS8749YdvevQLEWIvoepHv0LqbEI259cVqIa4e+eWiGwwFZ+sTth28NLcL8qHE= X-Received: by 10.180.108.131 with SMTP id hk3mr1515678wib.10.1382609367524; Thu, 24 Oct 2013 03:09:27 -0700 (PDT) X-Received: by 10.180.108.131 with SMTP id hk3mr1515662wib.10.1382609367398; Thu, 24 Oct 2013 03:09:27 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id ft19sm1906246wic.5.2013.10.24.03.09.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Oct 2013 03:09:26 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r9OA9O00037513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 24 Oct 2013 11:09:24 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r9OA9OPM037512; Thu, 24 Oct 2013 11:09:24 +0100 (BST) (envelope-from mexas) Date: Thu, 24 Oct 2013 11:09:24 +0100 (BST) From: Anton Shterenlikht Message-Id: <201310241009.r9OA9OPM037512@mech-cluster241.men.bris.ac.uk> To: freebsd-ia64@freebsd.org, jhb@freebsd.org, mexas@bris.ac.uk Subject: Re: deadlkres: possible deadlock detected for 0xe000000012aed200, blocked for 900014 ticks In-Reply-To: <201310231456.56359.jhb@freebsd.org> Cc: davide@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-ia64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bris.ac.uk List-Id: Porting FreeBSD to the IA-64 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2013 10:09:56 -0000 >From jhb@freebsd.org Wed Oct 23 21:10:30 2013 >> >> >> >> 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? yes: # ls -al /var/crash/*6* -rw------- 1 root wheel 27206 Oct 24 09:57 /var/crash/core.txt.6 -rw------- 1 root wheel 543 Oct 24 09:26 /var/crash/info.6 -rw------- 1 root wheel 5853138944 Oct 24 09:31 /var/crash/vmcore.6 # I added it to the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007 Is this any use? Also, since the panic is perfectly reproducible, I can cause it again, and run some commands in ddb, if you give explicit instructions. Many thanks Anton