From owner-freebsd-stable@FreeBSD.ORG Wed Jul 2 07:34:49 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 AA13E10656B0; Wed, 2 Jul 2008 07:34:49 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp7.yandex.ru (smtp7.yandex.ru [213.180.200.45]) by mx1.freebsd.org (Postfix) with ESMTP id 7FE928FC20; Wed, 2 Jul 2008 07:34:48 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:10231 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S737367AbYGBHem (ORCPT + 2 others); Wed, 2 Jul 2008 11:34:42 +0400 X-Yandex-Spam: 1 X-Yandex-Front: smtp7 X-Yandex-TimeMark: 1214984082 X-MsgDayCount: 9 X-Comment: RFC 2476 MSA function at smtp7.yandex.ru logged sender identity as: bu7cher Message-ID: <486B2F8F.70801@yandex.ru> Date: Wed, 02 Jul 2008 11:34:39 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Jeremy Chadwick References: <4F9C9299A10AE74E89EA580D14AA10A61A196C@royal64.emp.zapto.org> <486AFB78.5030905@yandex.ru> <4F9C9299A10AE74E89EA580D14AA10A61A196F@royal64.emp.zapto.org> <486B2B9C.2080007@yandex.ru> <20080702072826.GB45396@eos.sc1.parodius.com> In-Reply-To: <20080702072826.GB45396@eos.sc1.parodius.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Daniel Eriksson , =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= 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, 02 Jul 2008 07:34:49 -0000 Jeremy Chadwick wrote: > Which makes me wonder if there's multiple revisions of the MCP55, or, if > Samsung drives simply don't behave properly with that chipset (this has > my vote). Daniel has the same revision (as I can see from pciconf). -- WBR, Andrey V. Elsukov