Date: Tue, 15 Oct 2013 09:35:58 +0100 (BST) From: Anton Shterenlikht <mexas@bris.ac.uk> To: davide@freebsd.org, mexas@bris.ac.uk Cc: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Subject: Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks Message-ID: <201310150835.r9F8ZwZk043224@mech-cluster241.men.bris.ac.uk> In-Reply-To: <CACYV=-GEaL4whdSmiY51U8pqgaidpWbMyOVshENWHb7TDh5V_w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>From davide.italiano@gmail.com Fri Oct 11 15:39:49 2013 > >If you're not able to get a full dump, a textdump would be enough. >In your DDB scripts just remove the 'call doadump' step and you should >be done, unless I'm missing something. >Please adjust the script as well to include all the informations >requested as mentioned in my previous link, e.g. 'show lockedvnods' is >not mentioned on the example section of textdump(4) manpage but it >could be useful to ease debugging. It seems "call doadump" is always needed. At least it is included in textdump(4) examples. Also, this tutorial incluldes it: http://www.etinc.com/122/Using-FreeBSD-Text-Dumps I think I still haven't got textdump right, because instead of savecore: writing core to textdump.tar.0 I see: savecore: writing core to /var/crash/vmcore.9 Thanks Anton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201310150835.r9F8ZwZk043224>