From owner-freebsd-stable@FreeBSD.ORG Mon Jan 16 23:55:01 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4FB81065720 for ; Mon, 16 Jan 2012 23:55:01 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id A307C8FC0A for ; Mon, 16 Jan 2012 23:55:01 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so2273447obc.13 for ; Mon, 16 Jan 2012 15:55:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.116.38 with SMTP id jt6mr12890625obb.52.1326758101016; Mon, 16 Jan 2012 15:55:01 -0800 (PST) Received: by 10.182.150.69 with HTTP; Mon, 16 Jan 2012 15:55:00 -0800 (PST) X-Originating-IP: [93.221.190.159] In-Reply-To: <4F149FAE.4090101@cello.com> References: <4F149FAE.4090101@cello.com> Date: Tue, 17 Jan 2012 00:55:00 +0100 Message-ID: From: "C. P. Ghost" To: Kurt Lidl Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: Can't boot 9.0-RELEASE on sparc64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2012 23:55:01 -0000 On Mon, Jan 16, 2012 at 11:07 PM, Kurt Lidl wrote: > I noted that booting off a cdrom image was broken for the 9.0-RC3 images > as well: > > http://lists.freebsd.org/pipermail/freebsd-current/2011-December/030747.html > > There was no followup. > > I've since managed to netboot that machine from the 9.0 release, and get a > 9.0-STABLE world built and installed onto it. I've managed to source upgrade from 8.2 to 9.0 as well, and found that the 9.0 kernel (/dev/cd0) silently corrupts data when reading from CDROM, while the 8.2 kernel (/dev/acd0) didn't. Not being able to install 9.0 from CDROM is just a consequence of this bug in 9.0's /dev/cd0. There's probably some bug(s) lurking there, that is(are) only triggered on big endian machines. > -Kurt Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/