From owner-freebsd-current@freebsd.org Sat May 2 18:36:38 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 218AD2D6F44 for ; Sat, 2 May 2020 18:36:38 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49DyWV05Vlz4VTx; Sat, 2 May 2020 18:36:37 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by fc.opsec.eu with local (Exim 4.93.0.4 (FreeBSD)) (envelope-from ) id 1jUx06-000927-Pn; Sat, 02 May 2020 20:36:34 +0200 Date: Sat, 2 May 2020 20:36:34 +0200 From: Kurt Jaeger To: Grzegorz Junka Cc: Kurt Jaeger , bzeeb+freebsd+lor@zabbadoz.net, freebsd-current@freebsd.org Subject: Re: lock order reversal and poudriere Message-ID: <20200502183634.GA90255@fc.opsec.eu> References: <68514e96-f1a5-0c8d-998f-bf81034ed61d@gjunka.com> <20200502095404.GN39563@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 49DyWV05Vlz4VTx X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.64 / 15.00]; TAGGED_RCPT(0.00)[freebsd,lor]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.85)[-0.852,0]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; NEURAL_HAM_LONG(-0.79)[-0.788,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2020 18:36:38 -0000 Hi! > > > I am compiling some packages with poudriere on 13-current kernel. I > > > noticed some strange messages printed into the terminal and dmesg: > > > > > > lock order reversal: > > [...] > > > Are those the debug messages that aren't visible on non-current kernel > > > and should they be reported? > > Yes, they should be checked and reported. > > > > For more details see: > > > > http://sources.zabbadoz.net/freebsd/lor.html > > > > There's a webpage with a list of all known LORs and a way to > > report new LORs. > Thanks Kurt. I can't find those two specific LORs in the list on that > page. The page also says to report them using a link, which leads to 404 > :-), or on this mailing list, which I did. I am not sure what else should > I do. I don't know, either 8-} bz@ is in Cc:, so he'll probably know what to do. > How do I know if I have got a backtrace? > > Are those errors: > > pid 43297 (conftest), jid 5, uid 0: exited on signal 11 > > related or it's a different issue? I think that's a different issue. -- pi@FreeBSD.org +49 171 3101372 Now what ?