From owner-freebsd-i386@FreeBSD.ORG Fri Sep 27 19:40:01 2013 Return-Path: Delivered-To: freebsd-i386@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 76D07297 for ; Fri, 27 Sep 2013 19:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6485826AD for ; Fri, 27 Sep 2013 19:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r8RJe1Ae067545 for ; Fri, 27 Sep 2013 19:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r8RJe1jX067544; Fri, 27 Sep 2013 19:40:01 GMT (envelope-from gnats) Date: Fri, 27 Sep 2013 19:40:01 GMT Message-Id: <201309271940.r8RJe1jX067544@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org Cc: From: Scott Mraz Subject: Re: i386/151122: [boot] BTX 1.02 crashes on boot X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Scott Mraz List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Sep 2013 19:40:01 -0000 The following reply was made to PR i386/151122; it has been noted by GNATS. From: Scott Mraz To: bug-followup@FreeBSD.org, renato.camarao@gmail.com Cc: Subject: Re: i386/151122: [boot] BTX 1.02 crashes on boot Date: Fri, 27 Sep 2013 12:38:07 -0700 --089e013c66da3634de04e762a039 Content-Type: text/plain; charset=ISO-8859-1 This still appears to be broken in 9.1, has anyone an update on a work around / resolution? -Scott --089e013c66da3634de04e762a039 Content-Type: text/html; charset=ISO-8859-1

This still appears to be broken in 9.1, has anyone an update on a work around / resolution?


-Scott
--089e013c66da3634de04e762a039--