Date: Thu, 11 Aug 2016 03:43:22 +0430 From: Hooman Fazaeli <hoomanfazaeli@gmail.com> To: Ryan Stone <rysto32@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: <57ABB512.4030503@gmail.com> In-Reply-To: <CAFMmRNwKWkuJJ%2BU_xVgmrUweFbJkN7UN_U0HUR1aJWoNHx0WgQ@mail.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> <CAFMmRNwKWkuJJ%2BU_xVgmrUweFbJkN7UN_U0HUR1aJWoNHx0WgQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-08-10 22:10, Ryan Stone wrote: > On Wed, Aug 10, 2016 at 1:23 PM, Hooman Fazaeli <hoomanfazaeli@gmail.com <mailto: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. Sure, I will. BTW, what do you exactly mean by lock leaking? Is there a list for the possible causes of 'spin lock held too long' panics? I mean, what sorts of coding bugs may cause a thread to hold a spin lock for a long time? Such a list would provide me an starting point for diagnostics. And, How much long is 'too long'? What is the justification behind the few million for() loop iterations that _mtx_lock_spin waits to grab a spin lock? Thanks. -- Best regards Hooman Fazaeli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57ABB512.4030503>