From owner-freebsd-current@freebsd.org Sun Jul 16 01:20:44 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 43721B94496 for ; Sun, 16 Jul 2017 01:20:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::22d]) (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 ED69265E6C for ; Sun, 16 Jul 2017 01:20:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua0-x22d.google.com with SMTP id j53so69004135uaa.2 for ; Sat, 15 Jul 2017 18:20:43 -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=/3grlRkCc82UHlSF/tRyA2lgAJiVcm/eD6tC6ZdxiXM=; b=J6l3055dKgNq8jcT798Vs8Pq/jXkGVheo35QMSYomHsKrKjqU7tvXmIIuzSE2QKic6 PN5ovHN3tb6FXJALpCdi+yIsXt1MTcBz4cjd5HSsta+qB0h2ibnE85F/X965bq+d9QI+ ZiLH2LCag4pSkIuNG8vGWqn5+UGwzs56CB/qTGcehOsvC5L2NmDthk+LdenJlERas4G9 VkaqN20eWB7wUMzgReXpWo4XlyzeKfj/bHuW8wQ0tc+kfXWXkzagJqygKcuaTQVa+Ji+ HQqRHaOojfw+VaOV+f64Yg++1aWBdnkLXX/XwKZae/5+nJlImjAvmDh0+LWbrAuay5S5 cQgg== 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=/3grlRkCc82UHlSF/tRyA2lgAJiVcm/eD6tC6ZdxiXM=; b=Ef6k2ou64An7srt3AH2lxdY3gU4FBgaBr5NfvyghK6r8fuXFAUrnJBMIRhfNvdIcZq 8QLQ1Nh86CEL8Q6tWftCaBsMBwESY4541eeJdTEi6ZW/vJG24tDd4tcl2ljXwVQHhAaI Lz4plwNpI4f/hjc1gB+NcU8oJAQ8/HB5knzqEk3n5cBdYkVdbozJnCzBEtzJaF7T7HTT JfjKZH9Ju8bswoKGZ3tEvU/PXxPeyVK7+GlXV1JFy1y8RXoVVJPiuE13mqssCI6wx1cV AqY0vfI8aI0G712SjB9js7QUzm0kMAkpl2vkznKA7EMGVLsUbEhL+qW0VLfCb5B73w5Z qvew== X-Gm-Message-State: AIVw11268YZmsLli3rjuu3PiYzDUziZMZApgkugHc3lBJRALCjrkLWiv i4QSUb3gHJPxvDKSX29Y1P1y+DcPoob4 X-Received: by 10.176.25.45 with SMTP id v45mr1359472uag.16.1500168042854; Sat, 15 Jul 2017 18:20:42 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.103.36.1 with HTTP; Sat, 15 Jul 2017 18:20:42 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <384E5639-17C0-4151-A6EB-6239D810C01F@dsl-only.net> From: Warner Losh Date: Sat, 15 Jul 2017 19:20:42 -0600 X-Google-Sender-Auth: izugne_qocqlrDY-IyDU-usDP-U Message-ID: Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: Michael Butler Cc: Mark Millard , 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: Sun, 16 Jul 2017 01:20:44 -0000 On Sat, Jul 15, 2017 at 6:49 PM, Michael Butler wrote: > On 07/15/17 20:39, Mark Millard wrote: > >> FYI for Michael B.: the incomplete kernel rebuild problem has a fix: >> -r320919 . >> See the fix (to the building problem that was created in -r320220 ): >> >> https://lists.freebsd.org/pipermail/svn-src-head/2017-July/102622.html >> >> If the KDE problem persists based on a -r320919 or later build, it would >> be appropriate to report it again as a separate issue. >> >> Unfortunately various odd problems have shown up over -r320220 through >> -r320918 from incorrect rebuilds (and other oddities overlapping in the >> time frame). >> >> Of course if you built (or build) -r320844 based on a empty directory in >> the first place so that it was a full-build but the KDE problem persisted >> when using the rebuilt kernel then the above material does not apply. In >> such a case reporting that about the context for the KDE problem would be >> appropriate. >> >> You may well have other things to be doing instead of what the above >> suggests. If so, just take the above as background information. >> > > Prior to testing this, I did 'rm -rf /usr/obj/*' so it is a clean build. I > can run with user-land at SVN r321021 but any kernel at or after r320844 > fails :-( > Right. We need to find out what, exactly, is failing to make progress. I have exactly one guess as to what might be going on, and it's a long shot at best. To gather more evidence, I need to know if the kde thing that's segfaulting is accessing /dev/pass* or /dev/xpt*. If you can confirm that it is, then we'll need to see how to fix that. Also, you'll need an installworld as well as an installkernel so the new headers are installed prior to running kde. If that fixes it, then my guess goes from a long shot to close to a sure thing. Warner