From owner-freebsd-current@freebsd.org Tue Jul 11 14:32:28 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4870DDA13D4 for ; Tue, 11 Jul 2017 14:32:28 +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 23AE376376 for ; Tue, 11 Jul 2017 14:32:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 22F7ADA13D3; Tue, 11 Jul 2017 14:32:28 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22885DA13D1 for ; Tue, 11 Jul 2017 14:32:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 E143176374 for ; Tue, 11 Jul 2017 14:32:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id v202so64923159itb.0 for ; Tue, 11 Jul 2017 07:32:27 -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; bh=UPRjeFl87CFehb/Eupa3xG51PP8yeCc6oS1TARymGuQ=; b=xyzxFZG56uKCximy9B0rdpkiYckgFGoXbrMuxth0fmOgLrBpvSkzyIReCJ9MXAiUYk s/zXWEKNHSFvjy8QhqQ1nV4mOd6imCdQfZyExf4JOXw0ZGuDM2grHDSiwMq+3hUMgi2W LPUyCqRj5dxhVHrQPku4FUlP2YtfthucNHosSdNQt78Eij2IIo9kBWAcyjcLD8m2yEgq 0L/rd3IbBROrAmDhY3R8M4VmKHEOWOYcXl/wVpXQl/GECmIq60mKbvF8HqRHQskETvJ9 egAPMSomyw4Ur12DDQ7MBVm/8nNU/6uRcd+jqxDwyRPMmBIuYNUYU14CQNpDg2rF5U4S C3Hw== 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; bh=UPRjeFl87CFehb/Eupa3xG51PP8yeCc6oS1TARymGuQ=; b=C0gGjeQ/7u8KQALtAK2spnq+kvhRz6XbmUJkpg353XnvCddax+cyJJlkgduoXQnHJr Y2RPI2JxJOybguV6kNtM9jujz3o5EQuaaEtOkPT98UQJ/RWYWu4ZwemjnNAexW5t4q3J 93w6ARMnkkhFd4bDjCJHIbDM0F0tLzCVqwnU+g/QL+X0lNZBXsPZTzhFvSU1pm5vm57A GRHBJQdkkk/q1clocP8hVpANX0S4UVnGaArseb91Ta5y75tmRfLzcfV64XeJerVExGf7 BM4dzcHvBSa22gA8bxnXIibyj2UkDKuCV1d0IjXxIxwZlNX1rEIWASIim0cWR/zzpSP2 ZW4g== X-Gm-Message-State: AIVw111+VhbTBU4qQQrd/Q2P6dy52plFkiBuVgFRiTMBaVmiPr4EgWvG p8OFIKSDZ+XNVvLgTMWmaDIPqR/9u5EH X-Received: by 10.36.120.1 with SMTP id p1mr17875839itc.20.1499783547102; Tue, 11 Jul 2017 07:32:27 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.212.167 with HTTP; Tue, 11 Jul 2017 07:32:26 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <20170711121311.GI1177@albert.catwhisker.org> References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> From: Warner Losh Date: Tue, 11 Jul 2017 08:32:26 -0600 X-Google-Sender-Auth: kFSbbM_xvRAbrtddjIe37-i8kaA Message-ID: Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: David Wolfskill , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 11 Jul 2017 14:32:28 -0000 On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill wrote: > On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote: > > Pnic occurred prior to mounting file systems.... > > While O. Hartmann had written to indicate the he had identified r320844 > as the culprit, and I had other reason to suspect it, I was a bit busy > at work yesterday, and unable to determine this for myself empirically. > > I went ahead and updated my "head" sources to r320884 (without > attempting to revert r320844), while running head @r320827. > > On reboot, I (again) had a panic on the laptop that looked similar > to the one from yesterday (r320869). > > On the build machine, however, I encountered the "mountroot" issue that > O. Hartmann had described. > > I have again created screenshots; they may be found in > . For the > laptop, the last of them shows the backtrace; the one previous shows > the panic message. For the build machine ("freebeast"), the last > shows that when I asked for a list of "valid disk boot devices," > what was presented was an empty list. (I found a working keyboard for > it.) > > The most recent verbnose dmesg.boot from a successful boot of the > laptop (running head) may still be found at > . > For the build machine, it is > . > > I believe that each of the machines has an MMC slot, but I also believe > that in each case, it is empty. > > Is there anything else I might be able to do to help resolve this? > Try building a kernel without sdhci in it. It's looking like the scans for ata devices are returning errors on the desktop machine you have, which shouldn't have been happening. Also, can you try a 100% clean build of GENERIC to make sure there's not a meta-mode bug? Warner