Date: Wed, 10 Aug 2016 13:40:20 -0400 From: Ryan Stone <rysto32@gmail.com> To: Hooman Fazaeli <hoomanfazaeli@gmail.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: 9.3-RELEASE panic: spin lock held too long Message-ID: <CAFMmRNwKWkuJJ%2BU_xVgmrUweFbJkN7UN_U0HUR1aJWoNHx0WgQ@mail.gmail.com> In-Reply-To: <57AB632D.4000501@gmail.com> References: <57AB349B.2010805@gmail.com> <20160810141948.GP83214@kib.kiev.ua> <57AB462A.2080608@gmail.com> <CAFMmRNw3hFWy0dqwvnQn4wdYdWvU=-73N4gYffvj2HGrvefk7Q@mail.gmail.com> <57AB632D.4000501@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 10, 2016 at 1:23 PM, Hooman Fazaeli <hoomanfazaeli@gmail.com> wrote: > No. I have panics involving 'turnstile lock' (see the original post) and > 'sched lock 2' too. > That doesn't necessarily mean that the root cause isn't due to sched lock 0 being leaked. You'd have to dig into the cores and look at the chain of dependent locks to be sure. Give the patch a try; it should panic quite quickly if it's the issue I am thinking of.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNwKWkuJJ%2BU_xVgmrUweFbJkN7UN_U0HUR1aJWoNHx0WgQ>