From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 12:46:19 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 CD290106564A; Wed, 23 Jul 2008 12:46:19 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id CD4D88FC1F; Wed, 23 Jul 2008 12:46:19 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 7F4C91CC09E; Wed, 23 Jul 2008 05:46:19 -0700 (PDT) Date: Wed, 23 Jul 2008 05:46:19 -0700 From: Jeremy Chadwick To: Daniel Eriksson Message-ID: <20080723124619.GA65224@eos.sc1.parodius.com> References: <4F9C9299A10AE74E89EA580D14AA10A61A1968@royal64.emp.zapto.org> <4F9C9299A10AE74E89EA580D14AA10A61A1981@royal64.emp.zapto.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F9C9299A10AE74E89EA580D14AA10A61A1981@royal64.emp.zapto.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org, 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:46:19 -0000 On Wed, Jul 23, 2008 at 02:32:01PM +0200, Daniel Eriksson 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. Or it could just be a bad motherboard. (I'd need to go re-read the thread to remember if you were seeing this on more than one board.) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |