From owner-freebsd-sparc64@FreeBSD.ORG Thu Feb 9 04:50:13 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9453E106566C for ; Thu, 9 Feb 2012 04:50:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 835AB8FC13 for ; Thu, 9 Feb 2012 04:50:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q194oDXl054946 for ; Thu, 9 Feb 2012 04:50:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q194oDFo054945; Thu, 9 Feb 2012 04:50:13 GMT (envelope-from gnats) Date: Thu, 9 Feb 2012 04:50:13 GMT Message-Id: <201202090450.q194oDFo054945@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Kurt Lidl Cc: Subject: Re: sparc64/164226: [cd] Data corruption on 9.0-RELEASE when reading from CDROM X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kurt Lidl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2012 04:50:13 -0000 The following reply was made to PR sparc64/164226; it has been noted by GNATS. From: Kurt Lidl To: bug-followup@FreeBSD.org Cc: cpghost@cordula.ws Subject: Re: sparc64/164226: [cd] Data corruption on 9.0-RELEASE when reading from CDROM Date: Wed, 8 Feb 2012 23:43:41 -0500 I was able to create a release build from the 9.0-CURRENT sources earlier today (20120208), and successfully booted the release.iso on a spare netra-t105. While, I didn't install from the disk, I was able to select "Shell", and then use "sha256" on all .txz files in /usr/freebsd-dist, and all the checksums matched those in the MANIFEST file. I was unable to get the sha256 checksums to match like this on the 9.0-RELEASE kernel. (Or 9.0-RC3 for that matter, where I first noticed it failing.) I think that turning off the DMA access for the cdrom works around the corruption issue. -Kurt