Date: Tue, 11 Aug 2015 07:43:23 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Tim Kientzle <tim@kientzle.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Consistent crash of BeagleBone kernel Message-ID: <20150811044323.GU2072@kib.kiev.ua> In-Reply-To: <3CCB9E6A-EC5B-4A25-92B9-0850403BC657@kientzle.com> References: <CC793A5E-83D2-4169-AECB-9690572A00D0@kientzle.com> <20150809064704.GH2072@kib.kiev.ua> <350C3412-910F-4B08-A903-A51D18474DAF@kientzle.com> <20150809181004.GK2072@kib.kiev.ua> <F179DE32-D95B-4817-BBFB-97F2E79D4843@kientzle.com> <20150810073947.GN2072@kib.kiev.ua> <3CCB9E6A-EC5B-4A25-92B9-0850403BC657@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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) buffer lock is after the directory vnode lock, and both of them should be after the kld_sx. If some buffer lock appears before kld_sx, this is the same problem as with the vnode lock.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150811044323.GU2072>