On Mon, Oct 14, 2013 at 10:21 AM, Anton Shterenlikht <me...@bris.ac.uk> wrote: > >From davide.itali...@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. > > I still haven't got it right, but I now collected manually > some (hopefully) useful info (see below). >
This is fair enough -- If you're still at the ddb prompt, please print the whole panic message (or at least the address of the lock reported as deadlocked by DEADLKRES), so that we can at least have a candidate. -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri Poincare _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
