Lock order reversal [ newbie ] report [2nd one> more of ]
jbtakk at iherebuywisely.com
Sat Feb 25 14:59:48 UTC 2017
On Wed, 22 Feb 2017 21:06:32 -0600, Benjamin Kaduk <kaduk at mit.edu> wrote:
> Hi Jeffrey,
> Thank you for your enthusiasm in reporting these.
> Unfortunately, it is very likely that these two are "well-known" and
> believed to be harmless, so you have not discovered something
> terribly exciting.
> An old and no-longer particularly maintained listing of these and
> other LORs is at: http://sources.zabbadoz.net/freebsd/lor.html
> On Wed, Feb 22, 2017 at 06:20:08PM -0800, Jeffrey Bouquet wrote:
> > This one at boot:
> > #0 to #10
> > bufwait
> > /usr/src/sys/kern/vfs_bio.c:3500
> > dirhash
> > /usr/src/sys/ufs/ufs/ufs_dirhash.c:201
> > r313487 12.0-CURRENT Feb 13 2017
> > 1200020 FWIW
> > both the above and the below reports...
> > On Wed, 22 Feb 2017 15:37:21 -0800 (PST), "Jeffrey Bouquet" <jbtakk at iherebuywisely.com> wrote:
> > > #0 #16 follow:
> > > jotted down :
> > >
> > > 1. ufs /usr/src/sys/kern/vfs_syscalls.c:3364
> > > 2. bufwait /usr/src/sys/ufs/ffs/ffs_vnops.c:280
> > > 3. ufs /usr/src/sys/kern/vfs_subr.c:2600
> > >
> > > [ took roxterm out of the xinitrc, system stable seems more than yesterday... too
> > > early to tell, which is/was a 2nd issue... put in urxvt and st... based on TOP memory... ]
> > > _______________________________________________
> > > 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"
> > _______________________________________________
> > 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"
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
Found a few more in a debug custom kernel that has 9h 54m uptime as of now,
using nextboot, so are maybe not important... just a toy maybe to examine if
anyone has free time and/or has less than 9h uptime issues to remove a few
lock order reversals, in, say, amd64 (i386 here) if they are common to both but
would crash amd64 more reliably than the good uptime I have as of this
morning... r318487 Feb 13 2017 12.0-CURRENT 1200020
Thought to email them only because different 'subsystem' messages occur
during the boot verbose process... like 2016, 2017, 2016, 2015...
Maybe just newbie stuff. Thanks... ignore the 'speaker' stuff in it...
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the freebsd-current