From owner-freebsd-stable@FreeBSD.ORG Thu Jul 24 10:55:30 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 8FCA1106567F for ; Thu, 24 Jul 2008 10:55:30 +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 380DC8FC27 for ; Thu, 24 Jul 2008 10:55:30 +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 4873CA95002FD576; Thu, 24 Jul 2008 12:55:23 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message Date: Thu, 24 Jul 2008 12:55:22 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A61A1985@royal64.emp.zapto.org> In-Reply-To: <021501c8ed35$0053a330$47a8a8c0@iij.ad.jp> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MCP55 SATA data corruption in FreeBSD 7 Thread-Index: AcjtOgf2Td+BcpruSMynSNt9Kp+QKQAQIN5g References: <021501c8ed35$0053a330$47a8a8c0@iij.ad.jp> From: "Daniel Eriksson" To: Cc: Munenori Ohuchi 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: Thu, 24 Jul 2008 10:55:30 -0000 Munenori Ohuchi wrote: > Could you try the following patch? > ... > If you have a device like 'ad4' which is detected as=20 > 'udma=3DUDMA100', this patch will work. The drive in question looked like this in the verbose boot-log: ata2-master: pio=3DPIO4 wdma=3DWDMA2 udma=3DUDMA133 cable=3D40 wire ad4: 715404MB at ata2-master SATA300 ad4: 1465149168 sectors [1453521C/16H/63S] 16 sectors/interrupt 1 depth queue I tried the patch even though it probably isn't applicable to my problem, and unsurprisingly it didn't help. :-) Thanks for trying to help though! ___ Daniel Eriksson (http://www.toomuchdata.com/)