From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 12:32:04 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 A190B1065679; Wed, 23 Jul 2008 12:32:04 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout2-sn2.hy.skanova.net (pne-smtpout2-sn2.hy.skanova.net [81.228.8.164]) by mx1.freebsd.org (Postfix) with ESMTP id 6F01C8FC2A; Wed, 23 Jul 2008 12:32:04 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.168) by pne-smtpout2-sn2.hy.skanova.net (7.3.129) id 4873CA95002CE1F3; Wed, 23 Jul 2008 14:32:02 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message Date: Wed, 23 Jul 2008 14:32:01 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A61A1981@royal64.emp.zapto.org> In-Reply-To: <4F9C9299A10AE74E89EA580D14AA10A61A1968@royal64.emp.zapto.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MCP55 SATA data corruption in FreeBSD 7 Thread-Index: AcjbWSPaqAfW4rtJQwiRClpfJFg2GARZZjQg References: <4F9C9299A10AE74E89EA580D14AA10A61A1968@royal64.emp.zapto.org> From: "Daniel Eriksson" To: Cc: sos@FreeBSD.org 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: Wed, 23 Jul 2008 12:32:04 -0000 I wrote: > I am having problems with silent data corruption on (some) drives > connected to an MCP55 SATA controller. The original problem showed up when talking to (brand new) Samsung 1TB drives in SATA-300 mode hooked up to the onboard controller. I have now tested with a 750GB Seagate drive in both SATA-300 and SATA-150 mode. Unfortunately the problem was not Samsung-related or SATA-300 specific. This points to a driver problem with the chipset/controller combination, or possibly some sort of strange interaction with other hardware (interrupts?). I have no idea how to troubleshoot this any further. ___ Daniel Eriksson (http://www.toomuchdata.com/)