From owner-freebsd-sparc64@FreeBSD.ORG Mon Jan 16 16:59:48 2012 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCD73106564A; Mon, 16 Jan 2012 16:59:48 +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 8FBFC8FC0C; Mon, 16 Jan 2012 16:59:48 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so1712887obc.13 for ; Mon, 16 Jan 2012 08:59:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.116.38 with SMTP id jt6mr11718146obb.52.1326733187223; Mon, 16 Jan 2012 08:59:47 -0800 (PST) Received: by 10.182.150.69 with HTTP; Mon, 16 Jan 2012 08:59:47 -0800 (PST) X-Originating-IP: [93.221.190.159] In-Reply-To: References: Date: Mon, 16 Jan 2012 17:59:47 +0100 Message-ID: From: "C. P. Ghost" To: freebsd-sparc64 Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable Subject: Re: Reading from CDROM broken on 9.0-RELEASE/sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2012 16:59:48 -0000 On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote: > Hello, > > I think that reading from CDROM is actually broken > in 9.0-RELEASE/sparc64. > > On FreeBSD 8.2-RELEASE/sparc64, mounting a physical > CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso > and running sha256 on usr/freebsd-dist/*.txz yields the same > results as listed in usr/freebsd-dist/MANIFEST. > > However, on FreeBSD 9.0-RELEASE/sparc64, mounting the > same CDROM (using /dev/cd0), and running sha256 on the > same usr/freebsd-dist/*.txz files yields completely different results: > > SHA256 (base.txz) = > a96e255a9379ec1a58b756c3e788e34345fd79e35234925df842d700ccb10e1a > SHA256 (doc.txz) = > 54674bb68b111c3465b0beca8893a6b514b80e20dc22f2bbd208b992568261dc > SHA256 (games.txz) = > b9bedddeea549640b4f41a577f4c5f09aa29d0c3d0d4c105bc4fe7d327bf9fcd > SHA256 (kernel.txz) = > 661df36b4a2e87d2aa88ce998b50d48f2a91892fc288452a0282e3c092739046 > SHA256 (ports.txz) = > 315cbfac6f252de5209a3513a846d14650b98e2dcf99c12779ffd1d32acaa287 > SHA256 (src.txz) = > 6b3a4a9536b1ca2618949bb7bb44478266db551ac9f09ccfc92b5469a715f3cf > > This also prevents an installation of 9.0-RELEASE/sparc64 > via bsdinstall from CDROM (bsdinistall says that the data sets > are corrupted). I was only able to get 9.0 on that SunBlade 1500 > by using a regular source upgrade from a running 8.2-RELEASE > system (using usr/freebsd-dist/src.txz from that very same CDROM > that checksummed correctly on 8.2-RELEASE). > > Just to make it clear: the CDROM media is correct and checksums > correctly on 8.2-RELEASE. It doesn't checksum correctly on 9.0-RELEASE > because reading from CDROM media is now (partially) broken. > > Just to make sure the 9.0-RELEASE sha256 program isn't at fault, > I've mounted FreeBSD-9.0-RELEASE-sparc64-disc1.iso via mdconfig > and run sha256 on the *.txz files again: same results as in MANIFEST. > So sha256 on 9.0 itself is okay, it's only the reading from physical > media that corrupts data (and prevents installation from CDROM -- funny > that this passed release engineering and testing...). One more thing: With a 9.0-RELEASE world installed, if I boot the old 8.2-RELEASE kernel (/boot/kernel.old/kernel), mount /dev/acd0 and checksum the files with sha256, everything is okay. If I boot again the new 9.0-RELEASE kernel (/boot/kernel/kernel), mount /dev/cd0 and checksum the files with sha256, I get the wrong results above. Since there's no /dev/acd0 on 9.0-RELEASE, I can't test mounting that on 9 and compare the results with /dev/cd0. But obviously, whatever /dev/cd0 returns to cd9660 seems to be silently corrupted on 9.0; at least on sparc64. -cpghost. -- Cordula's Web. http://www.cordula.ws/