Lock order reversal errors during boot

[mokhi]

I see this LOR often too.
I thought maybe this is happening because of my Virtual Box setting :) (?!?)

On 5/21/16, Will Brokenbourgh <will_brokenbourgh at yahoo.com> wrote:
> On 05/16/16 00:44, Bjoern A. Zeeb wrote:
>>> On 15 May 2016, at 07:44 , Kurt Jaeger <lists at opsec.eu> wrote:
>>>
>>> Hi!
>>>
>>>> I am seeing 'lock order reversal' errors during boot on 11-CURRENT -
>>>> r298793.  A sample error:
>>>>
>>>> lock order reversal:
>>>>   1st 0xfffff8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498
>>>>   2nd 0xfffffe01ca539400 bufwait (bufwait) @
>>>> /usr/src/sys/ufs/ffs/ffs_vnops.c:263
>>>>   3rd 0xfffff80112a23b78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498
>>>> stack backtrace:
>>>> #0 0xffffffff80a94bf0 at witness_debugger+0x70
>>>> #1 0xffffffff80a94ae4 at witness_checkorder+0xe54
>>>> #2 0xffffffff80a0fdd6 at __lockmgr_args+0x4d6
>>>> #3 0xffffffff80ce9626 at ffs_lock+0xa6
>>>> [...snip...]
>>>>
>>>> I'm not sure if this is even something I should report, but better safe
>>>> than sorry, yes?
>>> Yes, and there's even a page to compare your LOR against other ones:
>>>
>>> http://sources.zabbadoz.net/freebsd/lor.html
>>>
>>> Can you try if you find your LOR there ? If not, can you add it
>>> to that page ?
>> No he can’t and I haven’t in years either.   Searching bugs might however
>> be a good idea;  there is a LOR category or tag somewhere.
>>
>> /bz
> Thank you for the replies.
>
> I'm getting these LORs pretty frequently.  Is this a normal occurrence
> for 11-CURRENT or is it only me having this problem?
>
> Thanks
>
> Will Brokenbourgh
>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"