From owner-freebsd-current@freebsd.org Sun Mar 25 04:15:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03790F6B687 for ; Sun, 25 Mar 2018 04:15:09 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 92D7B72145 for ; Sun, 25 Mar 2018 04:15:08 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: by mailman.ysv.freebsd.org (Postfix) id 52565F6B686; Sun, 25 Mar 2018 04:15:08 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3EA43F6B685 for ; Sun, 25 Mar 2018 04:15:08 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nsstlmta23p.bpe.bigpond.com (nsstlmta23p.bpe.bigpond.com [203.38.21.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BB9F77213C; Sun, 25 Mar 2018 04:15:04 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from smtp.telstra.com ([10.10.24.4]) by nsstlfep20p-svc.bpe.nexus.telstra.com.au with ESMTP id <20180325032116.LRKI32504.nsstlfep20p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com>; Sun, 25 Mar 2018 14:21:16 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtgedrvdeggddviecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfupfevtfgpvffgnffuvfftteenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomheptehnughrvgifucftvghilhhlhicuoegrrhgvihhllhihsegsihhgphhonhgurdhnvghtrdgruheqnecukfhppeduvdegrdduledtrdegtddrudekvdenucfrrghrrghmpehhvghlohepkggvnhdrrggtqdhrrdhnuhdpihhnvghtpeduvdegrdduledtrdegtddrudekvddpmhgrihhlfhhrohhmpeeorghrvghilhhlhiessghighhpohhnugdrnhgvthdr X-RG-VS-CLASS: clean X-Authentication-Info: Submitted using ID areilly@bigpond.net.au Received: from Zen.ac-r.nu (124.190.40.182) by smtp.telstra.com (9.0.019.22-1) (authenticated as areilly@bigpond.net.au) id 5A4EB5561CC223CD; Sun, 25 Mar 2018 14:21:16 +1100 Date: Sun, 25 Mar 2018 14:21:10 +1100 From: Andrew Reilly To: Warner Losh Cc: FreeBSD Current , jtl@freebsd.org Subject: Re: 12-Current panics on boot (didn't a week ago.) Message-ID: <20180325032110.GA10881@Zen.ac-r.nu> References: <20180324035653.GA3411@Zen.ac-r.nu> <20180324232206.GA2457@Zen.ac-r.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 25 Mar 2018 04:15:09 -0000 OK, I've completed the search: r331346 works, r331347 panics somewhere in the initialization of random. In the 331347 change (Add the "TCP Blackbox Recorder") I can't see anything obvious to tweak, unfortunately. It's a fair chunk of new code but it's all network-stack related, and my kernel is panicking long before any network activity happens. Any suggestions? Cheers, Andrew On Sat, Mar 24, 2018 at 05:23:18PM -0600, Warner Losh wrote: > Thanks Andrew... I can't recreate this on my VM nor my real hardware. > > Warner > > On Sat, Mar 24, 2018 at 5:22 PM, Andrew Reilly > wrote: > > > So, r331464 crashes in the same place, on my system. r331064 still boots > > OK. I'll keep searching. > > > > One week ago there was a change to randomdev to poll for signals every so > > often, as a defence against very large reads. That wouldn't have > > introduced a race somewhere, > > or left things in an unexpected state, perhaps? That change (r331070) by > > cem@ is just a few revisions after the one that is working for me. I'll > > start looking there... > > > > Cheers, > > > > Andrew > > > > On Sun, Mar 25, 2018 at 07:49:17AM +1100, Andrew Reilly wrote: > > > Hi Warner, > > > > > > The breakage was in 331470, and at least one version earlier, that I > > updated past when it panicked. > > > > > > I'm guessing that kdb's inability to dump would be down to it not having > > found any disk devices yet, right? So yes, bisecting to narrow down the > > issue is probably the best bet. I'll try your r331464: if that works that > > leaves only four or five revisions. Of course the breakage could be > > hardware specific. > > > > > > Cheers, > > > -- > > > Andrew > >