From owner-freebsd-current@freebsd.org Sat Mar 24 23:23:22 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 207ABF55711 for ; Sat, 24 Mar 2018 23:23:22 +0000 (UTC) (envelope-from wlosh@bsdimp.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 98BDE858D4 for ; Sat, 24 Mar 2018 23:23:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 595F6F55705; Sat, 24 Mar 2018 23:23:21 +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 34CC9F55704 for ; Sat, 24 Mar 2018 23:23:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 C14F8858D3 for ; Sat, 24 Mar 2018 23:23:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22f.google.com with SMTP id d13-v6so6633280itf.0 for ; Sat, 24 Mar 2018 16:23:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=8B7KOsrojjIOCQl7a9eOhJb5uJtynV4tZJrwYscYYzY=; b=uELplQ+kT4/zQYxLMlfX5uG52e+YPmUdkoY0JT2ipqf/U1WNhrvQza6ptWe2sshi4y rYDgWktObtrTTV6CkYeI78nkqOyJ41cTNohffbL5nsfo4WcOfSuC4X2VO7efZX8LIVir OMOB2UsDWmdoPAASDK+KZudwxgXGwgNPjd4pUW6oB97AHvgps6Xk/DhDcc5lQUvePrPd FOUdlx1U3HVwQ7Dr+18ZljDeCoW1rQclgVS8YdXcoR+MVj1nyj4aDQWI2lT+qhWwi7Ic RP/uNdo/Ol564GnOYwpbquVraBO/gpu3qAYdDm0XtN8inIMYxFNeBWX4BKVp38gT3Z/k Kn6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=8B7KOsrojjIOCQl7a9eOhJb5uJtynV4tZJrwYscYYzY=; b=g/EMGN37KNgg8fGFtOeAsaXDWbmb0imdsvCx23JvRBPJjlYl4K7944DF4bbIQpbl6q ReGe/DdsQisJe5bmcyhaKS6IxmfXbw2u/7GnkZ8GDrGBryZVDO+oS7z2znqUeKQzZyqS VPp7/9WL1Cd0TuJnq9NmePU8pnC7OyXKVWejoVgt7CEag9ubozcYq+/IqHiLSuu3HccN BKAreUL+ecfe8pXkWhAv8YxIC/1qD93SsHCg/64mER1Zf3P65SLegqp6Ry8kDOOvX2au bYWTPqAa5/uOQgKu5DTQP9YUQcBqtbDuwpPG0SrSQBAslLEgUqzumov2KImLc3XmSnKh GZSg== X-Gm-Message-State: AElRT7E464/0gl7mIn025wYyeltb6dRS7U5dNqTqMcfl/BJXAEWtn3Dq Et0BdcdexX+Yfwnk+0TvFXbywpAhxEh4oRWPmLdMpQ== X-Google-Smtp-Source: AG47ELun+TN6g8j031lB/dOu0ViIZUA5lXORVwWkb3wAqXdgk3GgOBQXwCqjQhwT9D9j2M5azzsVa6PmEIbGtVa7FtU= X-Received: by 2002:a24:fa83:: with SMTP id v125-v6mr18297134ith.36.1521933799640; Sat, 24 Mar 2018 16:23:19 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Sat, 24 Mar 2018 16:23:18 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180324232206.GA2457@Zen.ac-r.nu> References: <20180324035653.GA3411@Zen.ac-r.nu> <20180324232206.GA2457@Zen.ac-r.nu> From: Warner Losh Date: Sat, 24 Mar 2018 17:23:18 -0600 X-Google-Sender-Auth: n-cIsZoM-k7GfbeycYhnJ3UYzyg Message-ID: Subject: Re: 12-Current panics on boot (didn't a week ago.) To: Andrew Reilly Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" 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: Sat, 24 Mar 2018 23:23:22 -0000 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 >