On Mon, Aug 10, 2015 at 09:33:11PM -0700, Tim Kientzle wrote:
> I have a guess, though: I noticed that the old bufwait/dirhash LOR is being
> triggered before this. Could the backtrace from that be teaching Witness a
> bogus ufs -> kld ordering?
I do not see how it could.
The (directory) buff
> On Aug 10, 2015, at 12:39 AM, Konstantin Belousov wrote:
>
> On Sun, Aug 09, 2015 at 05:24:13PM -0700, Tim Kientzle wrote:
>>
>>> On Aug 9, 2015, at 11:10 AM, Konstantin Belousov
>>> wrote:
>>>
>>> On Sun, Aug 09, 2015 at 10:53:20AM -0700, Tim Kientzle wrote:
I suspect the LOR i
On Sun, Aug 09, 2015 at 05:24:13PM -0700, Tim Kientzle wrote:
>
> > On Aug 9, 2015, at 11:10 AM, Konstantin Belousov
> > wrote:
> >
> > On Sun, Aug 09, 2015 at 10:53:20AM -0700, Tim Kientzle wrote:
> >>
> >> I suspect the LOR is new.
> >>
> >> It looks like the panic is occurring when WITNESS
> On Aug 9, 2015, at 11:10 AM, Konstantin Belousov wrote:
>
> On Sun, Aug 09, 2015 at 10:53:20AM -0700, Tim Kientzle wrote:
>>
>> I suspect the LOR is new.
>>
>> It looks like the panic is occurring when WITNESS tries to print the
>> backtrace for the LOR. I???m not familiar with that code;
On Sun, Aug 09, 2015 at 10:53:20AM -0700, Tim Kientzle wrote:
>
> I suspect the LOR is new.
>
> It looks like the panic is occurring when WITNESS tries to print the
> backtrace for the LOR. I???m not familiar with that code; does it use the
> kernel linker?
>
It indeed locks the linker lock
> On Aug 8, 2015, at 11:47 PM, Konstantin Belousov wrote:
>
> On Sat, Aug 08, 2015 at 05:24:37PM -0700, Tim Kientzle wrote:
>> I???m seeing the following crash quite consistently on r286438. It looks
>> like the recent work on the kernel linker locking still has some issues.
>>
>> Any suggest
On Sat, Aug 08, 2015 at 05:24:37PM -0700, Tim Kientzle wrote:
> I???m seeing the following crash quite consistently on r286438. It looks
> like the recent work on the kernel linker locking still has some issues.
>
> Any suggested workarounds?
>
> Tim
>
> log trace ===
> ...
> Starting fil
I’m seeing the following crash quite consistently on r286438. It looks like
the recent work on the kernel linker locking still has some issues.
Any suggested workarounds?
Tim
log trace ===
...
Starting file system checks:
/dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/mmcsd0s2a: