From owner-freebsd-current@freebsd.org Tue Jul 11 17:09:06 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 A5D3ADA6D05 for ; Tue, 11 Jul 2017 17:09:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7EAC87D866 for ; Tue, 11 Jul 2017 17:09:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7DEDBDA6D04; Tue, 11 Jul 2017 17:09:06 +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 7BEA3DA6D03 for ; Tue, 11 Jul 2017 17:09:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 401117D865 for ; Tue, 11 Jul 2017 17:09:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id v202so69548227itb.0 for ; Tue, 11 Jul 2017 10:09:06 -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=hIHi70b5yKVL4TpzaHgTYRqFzS4QZyWlT5UPAxnwmKE=; b=Jh6mHC8WI5daE3ugPEjEQXm+OG/maoxYEZfVf7/7Omzrp//DS217o+4k+iER4sLV4W i6Ridp18pAzIE39AUJm24YdPvKfAeCFY6NQckEoHTCjvxUA3qf6e+EaUvyBZKgNOidiX fawdSrW4w56LEkA4Mq2VB2S19HSgt9KHncgBInjA3LGBsZL7uAH0i8pffSobFCaz+XJy IMGvb3enACvVFgsbdX8GWypt87oDy7bF/Y7PzvjzEEdaEqnpX8XgetrHGWdHjSbzSyNn 84+jYbWuN9qu5cRBtu8wQ2ImGvK2DntK1GArN+JJMhcfyzPLXSDphuNoYPf90Hfr+FCl hLVg== 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=hIHi70b5yKVL4TpzaHgTYRqFzS4QZyWlT5UPAxnwmKE=; b=Xjq5dcMhChMvjvsYtnjMrbHFYAkWK+iiSfNXvaw+mNOitEYmcCsLVtIG4avf4rJBbN sTMDzijXvev8ypwwLcyC2UTFwdJP+Ie1eVY4AYZfar9XumZIzVLt1652/TtHmcEzflHr kvDcDuOyrK/aomj9MYIS34O7aJx+kDD0zU7LOIGAGdURbxkP6aEU/R31iFKK7EghryCa i9ZNB5ZrOuk5fPu0vHtt1ldNWbW3ZE7eevNW4i/BlHTih6nnsaHmLLMDq6a34elRzlUX MNbqh/K65y1HUjmPpyQa6nmROuUFcfSLgmF9JYsJVRJw3vF2zFj7hlLNb6c0XfyLh06z z4zg== X-Gm-Message-State: AIVw110TOqUZrey0/8wr41OCtcqOFBUmj5N+Fu1ZORs5Mr7E61dRmGqd OBMuIccyZSaCNDPByyvW6ajH9JqMYcDp X-Received: by 10.107.180.5 with SMTP id d5mr1196699iof.56.1499792945533; Tue, 11 Jul 2017 10:09:05 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.212.167 with HTTP; Tue, 11 Jul 2017 10:09:05 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> From: Warner Losh Date: Tue, 11 Jul 2017 11:09:05 -0600 X-Google-Sender-Auth: YnrsxgOAUL9TBTTuW9C0tHc0KoM Message-ID: Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: Michael Butler Cc: 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 17:09:06 -0000 On Tue, Jul 11, 2017 at 10:47 AM, Michael Butler wrote: > On 7/11/17 10:32 AM, Warner Losh wrote: > >> On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill >> wrote: >> >>> 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? >> > > On a machine with SDHCI, a clean rebuild (after "r -rf /usr/obj") refuses > to find /dev/ada0 :-( > Take sdhci out of the kernel and try again. If that works, it tells us one thing (need to troubleshoot sdhci stuff more). If not it tells us another (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY command? Does it try multiple times per AHCI port? What AHCI device do you have? You may need to scroll back with the screen-lock / pageup keys to see these messages. Plus we know we have at least one bug in meta-mode rebuilding since not everything is being rebuilt that should be across this change. The change itself didn't change CAM except for copying one set of data it didn't used to, into a structure whose size grew (which is why we're seeing crashes / failures for a 'cross-threaded' rebuild). There's nothing else that changed (especially after I removed the bogus debug printfs) that I can see in auditing the change. I was really hoping David's machine would exhibit the behavior since we're co-workers and have a shared infrastructure for debugging we can leverage. Warner