From owner-freebsd-current@freebsd.org Sun Jul 16 00:49:56 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 44B11B7F538 for ; Sun, 16 Jul 2017 00:49:56 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1424464ED3 for ; Sun, 16 Jul 2017 00:49:56 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1500166194; bh=/nxNMQ55 xr3C9Bi8i501hzHBO2+LrBieM0sW5tJCP/E=; b=i7BG6jJ20cJPX7M9lCRj/qas PKwpMJzZuEO0bFdLd8/arxvWV5fqCdSJFwC7YKLSHB+BzqjZ/Ou+g945pRUPJHIh e9f/VafeKdlHq2th5qZqIPf59tWCZHvHF1/ERI5hFQ+pqpswS1trsgrFSqacutKv 30wE/8MV9kSA2vRynGA= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 37D4CFF57; Sat, 15 Jul 2017 20:49:54 -0400 (EDT) Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: Mark Millard , FreeBSD Current References: <384E5639-17C0-4151-A6EB-6239D810C01F@dsl-only.net> From: Michael Butler Message-ID: Date: Sat, 15 Jul 2017 20:49:53 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <384E5639-17C0-4151-A6EB-6239D810C01F@dsl-only.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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 00:49:56 -0000 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 :-( imb