From owner-freebsd-stable@FreeBSD.ORG Tue Jul 1 16:55:25 2008 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 C51B41065678 for ; Tue, 1 Jul 2008 16:55:25 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.freebsd.org (Postfix) with ESMTP id 815138FC1A for ; Tue, 1 Jul 2008 16:55:25 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.168) by pne-smtpout1-sn1.fre.skanova.net (7.3.129) id 47A9795002A39D05; Tue, 1 Jul 2008 18:55:24 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message Date: Tue, 1 Jul 2008 18:55:23 +0200 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A61A196C@royal64.emp.zapto.org> X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2 In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MCP55 SATA data corruption in FreeBSD 7 Thread-Index: Acjbk6ISq2/onaBrQLGJs8F6JcHyHwABxjWg References: From: "Daniel Eriksson" To: Cc: utisoft@gmail.com Subject: RE: MCP55 SATA data corruption in FreeBSD 7 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: Tue, 01 Jul 2008 16:55:25 -0000 Chris Rees wrote: > I have a 570 SLI too (Asus M2N-SLI Deluxe), I've been looking for an > excuse to put FreeBSD on here :) >=20 > I'll start installing it, anything I should do to make this=20 > error more obvious? No, if it is a common problem with this chipset and/or MCP55 controller revision (which I think) then you should run into problems pretty much as soon as you start reading from the drive (on initial boot after install for example). I'm not sure if the problem is amd64 specific or not, but it seems the people that have reported problems have all run amd64 (and not i386). This might be a coincident though. ___ Daniel Eriksson (http://www.toomuchdata.com/)