Date: Sun, 9 Aug 2015 21:10:04 +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: <20150809181004.GK2072@kib.kiev.ua> In-Reply-To: <350C3412-910F-4B08-A903-A51D18474DAF@kientzle.com> References: <CC793A5E-83D2-4169-AECB-9690572A00D0@kientzle.com> <20150809064704.GH2072@kib.kiev.ua> <350C3412-910F-4B08-A903-A51D18474DAF@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 to resolve symbols. So it seems to be even more useful to make the linker lock recursive locally, then you should be able to see the backtrace for LOR.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150809181004.GK2072>