Date: Fri, 6 Jun 2014 10:51:49 -0400 From: Ryan Stone <rysto32@gmail.com> To: Glen Barber <gjb@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: panic in deadlkres() on r267110 Message-ID: <CAFMmRNy7sxJA-=O%2Bpt=9Kr6Y03nxYZNYeRkmaSPYS1Pr5xypAQ@mail.gmail.com> In-Reply-To: <20140606141215.GE33882@hub.FreeBSD.org> References: <20140606141215.GE33882@hub.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 6, 2014 at 10:12 AM, Glen Barber <gjb@freebsd.org> wrote: > Two machines in the cluster panic last night with the same backtrace. > It is unclear yet exactly what was happening on the systems, but both > are port building machines using ports-mgmt/tinderbox. > > Any ideas or information on how to further debug this would be > appreciated. The first thing that I would do is try to figure out who holds the allproc_lock. If the lock is held exclusively then the pointer to the thread struct will be in allproc_lock.sx_lock. If the lock is held shared then it gets trickier. I'm not sure if there is a better possible way than doing a thread apply all bt in kgdb and finding which stack(s) could hold allproc_lock.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNy7sxJA-=O%2Bpt=9Kr6Y03nxYZNYeRkmaSPYS1Pr5xypAQ>