Date: Wed, 23 Oct 2013 08:36:19 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-ia64@freebsd.org, mexas@bris.ac.uk Cc: davide@freebsd.org, Konstantin Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org Subject: Re: deadlkres: possible deadlock detected for 0xe000000012aed200, blocked for 900014 ticks Message-ID: <201310230836.19524.jhb@freebsd.org> In-Reply-To: <201310230927.r9N9RAw5079054@mech-cluster241.men.bris.ac.uk> References: <201310230927.r9N9RAw5079054@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201310230836.19524.jhb>