9.3-RELEASE panic: spin lock held too long

[Hooman Fazaeli]

On 2016-08-10 22:10, Ryan Stone wrote:
> On Wed, Aug 10, 2016 at 1:23 PM, Hooman Fazaeli <hoomanfazaeli at gmail.com <mailto:hoomanfazaeli at 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