From owner-freebsd-current@freebsd.org Sat Dec 9 19:17:24 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 87061E95540 for ; Sat, 9 Dec 2017 19:17:24 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 576EC71E2B for ; Sat, 9 Dec 2017 19:17:24 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P0P00I00H7PF900@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Sat, 09 Dec 2017 18:17:04 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1512843424; bh=Rg5Rl0Or56kivQz34hd8JwfeZ/zrduSslI0QDeTs7yU=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=ULK629S9Uq7aFblV8sAYpirYCoSLLcBbwUM4gVipMJljo+MuRkIPh+pzJ/akd61v3 7p9YR9It9aXjavzWWdkYstang3Q2JpQpTkhVWVuZn3HmkiBCTrxrRN5M0WHw+L3FMB E4q9Jegw2bvftsVxHLMsfHao2TBpPaiiQ2z0V6uleY6gdznXtmCgHmZgJ1avRtjTUl UFLeEmLGl+8ooYW4DdQ0lbEWfOkDd2IV0qD4yhhCGR4ITpImKDxc7ZOcyI7CCt6rLp 3c+ha7AMdbY+siYhRQpAf535zDuP1RNyMFOrqim0ouSw8qv/Baq92BEjnOtBhNFq/B lypJCAcK246jA== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P0P00811HGAUS10@st13p35im-asmtp002.me.com>; Sat, 09 Dec 2017 18:17:00 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-12-09_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=4 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1712090264 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: GPTZFSBOOT in Current r326622 has problems From: Toomas Soome In-reply-to: Date: Sat, 09 Dec 2017 20:16:57 +0200 Cc: FreeBSD Current , Warner Losh Content-transfer-encoding: quoted-printable Message-id: References: <20171206164801.GA1055@mail.laus.org> <20171206222155.GA1792@mail.laus.org> <20171207001720.GA2058@mail.laus.org> <20171209023153.GA9904@mail.laus.org> To: lausts@acm.org X-Mailer: Apple Mail (2.3445.4.7) 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, 09 Dec 2017 19:17:24 -0000 > On 9 Dec 2017, at 19:56, Warner Losh wrote: >=20 > On Sat, Dec 9, 2017 at 7:12 AM, Thomas Laus wrote: >=20 >> On 12/08/17 22:06, Warner Losh wrote: >>>=20 >>> Clean build? >>>=20 >> It was a clean build. I performed a rm -rf /usr/obj/* before = starting >> the buildworld after cvs updating to r326720. >>=20 >> A couple of notes on my hardware: >>=20 >> I am not using UEFI and my CPU is an early Intel i5 Skylake that has = the >> Silicon Debug flag turned on as a default. Most operating systems >> including FreeBSD turn off this flag during the boot process because = of >> security concerns. Since BTX is very early in the boot process, the >> computer is powered up with SDBG turned on. >=20 >=20 > OK. I don't recall seeing a screen shot of the entire boot. Can you = send > that too (privately if you like) so I know exactly what's failing? Is = it > gptzfsboot loading /boot/loader? Is it early in /boot/laoder or ???? >=20 With BIOS boot you can try to press key (space or anything else except = enter) - if boot1 is good, you will get boot: prompt. rgds, toomas