From owner-freebsd-current@freebsd.org Sun Mar 25 04:35:45 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 5364AF6C6B8 for ; Sun, 25 Mar 2018 04:35:45 +0000 (UTC) (envelope-from jonlooney@gmail.com) 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 DEBC272DDB for ; Sun, 25 Mar 2018 04:35:44 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9C7F5F6C6B5; Sun, 25 Mar 2018 04:35:44 +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 7A5B8F6C6B4 for ; Sun, 25 Mar 2018 04:35:44 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CCA072DD8; Sun, 25 Mar 2018 04:35:43 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id i75so9786601wmf.0; Sat, 24 Mar 2018 21:35:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GM+zXPklKQmbOSOEKf+cH1cyobR6egMqCEqXz/S7mXU=; b=XQLA9Z+KF58HOOLonQNYsj3WW3MGSTkJo1NvcYqPkWKcDv/R47jOtG3Kn7fUkHVf9p u/vcsaVU+WexsEIgfm0mDN38MPtXA/sms6hgAJNIlw2bMMY7PCHRJE2vaoqP+pMdl+W0 KsbsGQX/GUQg7sMXUZFrUyeTkpBDi6V4xvZphRB7zpOwojSS9IeplD17n+hnmM3FVdvH dff9AfrPU2SfCA0d+SefFN7wI8VpzRPcmZ1OaHIGXM2K2FxXm85nwPSt3l/epRAa8g/2 kk604nv2csn5xjY7JTgsO2bJQraYBB6P9QK/vMlU2aPzAvmd0KpoSM2+5jTKGgmTKAt1 ijwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GM+zXPklKQmbOSOEKf+cH1cyobR6egMqCEqXz/S7mXU=; b=ACMuQccgZGq26lh3ZLXiE52lo8sdo3OpGn2fVY3a5VuaLSJZkDpPH2ZeeJ0KHU3ZDn bv2JTegeO7ACdfBRwXPIu3G943F6d7oimt5XTG9MH7AvDYWnhHxeGVZCJojQPV6VvskF lQtEGg4wPEw6aSo+au6VGh5EvugNQLRhtVWMNJxXb5XBmex9iUqsoenhvAICt70u/8c4 KC/ra6hvEvAIgr2w/UKn7/ERjrmvYRo5CcLw2c+oo/E9eu/kwe7Gks1x7ePOYblP3arc Yxzw6RmqRKuQRfrqUFn/IqDP9queO7t+d0vK+M9qZPOPfvyzInRO6gHv6i4KGrPudsG+ R8jQ== X-Gm-Message-State: AElRT7FsGe7NTb5wdMKWOHLIS/yfZMNUYp3GENhXg3px6lQ7K/KHqX9t W4Wyy2cW37hXPe4TPYobi88X1DXnUbTWXPLkUsazqQ== X-Google-Smtp-Source: AG47ELuygrzc/ML1IR0fo/H3NIC7njRDcM9n8kqaXDtIInUs5XKY7038a6PzwmtQ3Qo8Rffsly91ENtFIWzNLIExsbA= X-Received: by 10.28.125.84 with SMTP id y81mr12055039wmc.66.1521952541633; Sat, 24 Mar 2018 21:35:41 -0700 (PDT) MIME-Version: 1.0 References: <20180324035653.GA3411@Zen.ac-r.nu> <20180324232206.GA2457@Zen.ac-r.nu> <20180325032110.GA10881@Zen.ac-r.nu> In-Reply-To: <20180325032110.GA10881@Zen.ac-r.nu> From: Jonathan Looney Date: Sun, 25 Mar 2018 04:35:31 +0000 Message-ID: Subject: Re: 12-Current panics on boot (didn't a week ago.) To: Andrew Reilly Cc: FreeBSD Current , Warner Losh , jtl@freebsd.org X-Mailman-Approved-At: Sun, 25 Mar 2018 11:18:30 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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:35:45 -0000 For now, you can update through r331485 and then take TCP_BLACKBOX out of your kernel config file. That won=E2=80=99t really =E2=80=9Cfix=E2=80=9D an= ything, but should at least get you a booting system (assuming the new code from r331347 is really triggering a problem). I=E2=80=99ll take another look to see if I missed something in the commit. = But, at the moment, I=E2=80=99m hard-pressed to see how r331347 would cause the pro= blem you describe. Jonathan On Sat, Mar 24, 2018 at 9:17 PM Andrew Reilly wrote: > 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 ever= y > 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 > > > >