From owner-freebsd-current@freebsd.org Wed Jan 27 15:17:54 2016 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 15EDEA7051E for ; Wed, 27 Jan 2016 15:17:54 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2a00:d1e0:1000:c00::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D48F4113D; Wed, 27 Jan 2016 15:17:53 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cloud.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 3pr7pl17tMz4y6b; Wed, 27 Jan 2016 15:17:51 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cloud.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id vmA-w0nR-IYe; Wed, 27 Jan 2016 15:17:50 +0000 (UTC) Received: from [IPv6:2001:470:dca9:2::3] (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 3pr7pk32zZz4xWY; Wed, 27 Jan 2016 15:17:50 +0000 (UTC) Subject: Re: Bad GPTZFSBOOT? To: Larry Rosenman , Freebsd current References: Cc: imp@freebsd.org From: Niclas Zeising Message-ID: <56A8DF5B.2070704@freebsd.org> Date: Wed, 27 Jan 2016 16:16:43 +0100 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Wed, 27 Jan 2016 15:17:54 -0000 On 2016-01-27 04:07, Larry Rosenman wrote: > Can someone(tm) look at > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206659 for me? Just to get the same information here as in the PR. This seems to have broken between r294750 and r294770. There were a series of commits to the boot loaders in that interval. Hopefully this will be resolved soon. Regards! -- Niclas