Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Mar 2015 20:52:16 -0600
From:      Ian Lepore <ian@freebsd.org>
To:        Jason Birch <jbirch@jbirch.net>
Cc:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: BBB freebsd-current backtrace. why?
Message-ID:  <1426042336.33324.32.camel@freebsd.org>
In-Reply-To: <CAA=KUhsE5w85Whxxv0FDhmyC-Rz8YfOsL8MPhB%2BMcrd9QE5-_A@mail.gmail.com>
References:  <CAKE2PDvJ9dadCZpq7BdWfKUZyNUZ5O2e%2BD1yWaKYQ4TSCW8%2BEQ@mail.gmail.com> <CAA=KUhsE5w85Whxxv0FDhmyC-Rz8YfOsL8MPhB%2BMcrd9QE5-_A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2015-03-11 at 13:05 +1100, Jason Birch wrote:
> On Wed, Mar 11, 2015 at 11:35 AM, jungle Boogie <jungleboogie0@gmail.com>
> wrote:
> 
> > Hello All,
> >
> > Brand new download and install of -current on my beagle bone black and
> > getting below backtrace, but the portsnap extract is continuing. If
> > this is how it was on last weeks image, the backtrace will randomly
> > print something similar to what's below even when the BBB is inactive.
> >
> > Downloaded from:
> > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/11.0/
> >
> > Is this expected?
> >
> > root@beaglebone:~ # portsnap fetch extract update
> > Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
> > Fetching public key from isc.portsnap.freebsd.org... done.
> > Fetching snapshot tag from isc.portsnap.freebsd.org... done.
> > Fetching snapshot metadata... done.
> > Fetching snapshot generated at Tue Mar 10 00:05:13 UTC 2015:
> > 248798a3bfb5e11c4a642a6254d9ec1573982894936270100% of   71 MB 2297 kBps
> > 00m32s
> > Extracting snapshot... lock order reversal:
> >  1st 0xcd228ba0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3097
> >  2nd 0xc2fa0e00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285
> > KDB: stack backtrace:
> >
> 
> They're lock order reversals, as enabled by the WITNESS kernel option. You
> probably don't need to worry, but it's helpful to check if they've been
> reported and, if not, report them.
> 
> You might be running into this one:
> http://sources.zabbadoz.net/freebsd/lor/261.html

That website hasn't been updated for years.  The sad truth is that you
can report LORs all day long and nobody seems to care anymore.  But if
you try to turn it off by default in the kernel configs you get yelled
at about how important it is.  Bah.

-- Ian





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1426042336.33324.32.camel>