From owner-freebsd-current@FreeBSD.ORG Thu Oct 19 11:23:03 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6753616A403; Thu, 19 Oct 2006 11:23:03 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A61EA43D62; Thu, 19 Oct 2006 11:23:02 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.130] (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.13.6/8.13.4) with ESMTP id k9JBN164052245; Thu, 19 Oct 2006 13:23:02 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <4537601D.3090107@deepcore.dk> Date: Thu, 19 Oct 2006 13:23:09 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 1.5.0.2 (X11/20060531) MIME-Version: 1.0 To: Ruslan Ermilov References: <4535E88B.9070108@freebsd.org> <20061018134019.GB21654@rambler-co.ru> <45367E22.80207@deepcore.dk> <20061019104139.GA11216@rambler-co.ru> In-Reply-To: <20061019104139.GA11216@rambler-co.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v2.0beta Cc: freebsd-current@FreeBSD.ORG, Soren Schmidt Subject: Re: support for marvell sata chips? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2006 11:23:03 -0000 Ruslan Ermilov wrote: > On Wed, Oct 18, 2006 at 09:18:58PM +0200, S?ren Schmidt wrote: > >> Ruslan Ermilov wrote: >> >>> BTW, we're having data corruption issues when using Marvell 88SX6081: >>> >>> # dmesg |grep ^ad16 >>> ad16: 476940MB at ata8-master SATA150 >>> # dmesg | grep ^ata8 >>> ata8: on atapci0 >>> # dmesg | grep ^atapci0 >>> atapci0: port 0x9800-0x98ff mem >>> 0xfc900000-0xfc9fffff irq 20 at device 1.0 on pci2 >>> # dd if=/dev/ad16 bs=128k count=1024 | md5 >>> 1024+0 records in >>> 1024+0 records out >>> 134217728 bytes transferred in 2.091913 secs (64160282 bytes/sec) >>> 669aa0b8c706f06d3d41aae95d4a3cf1 >>> # dd if=/dev/ad16 bs=128k count=1024 | md5 >>> 1024+0 records in >>> 1024+0 records out >>> 134217728 bytes transferred in 2.092598 secs (64139273 bytes/sec) >>> 5b92918e4beaadf5a7ff74829b9ab9ce >>> # dd if=/dev/ad16 bs=128k count=1024 | md5 >>> 1024+0 records in >>> 1024+0 records out >>> 134217728 bytes transferred in 2.096472 secs (64020758 bytes/sec) >>> d56fbdee36d70c8d6fcae6ea7b7550a7 >>> # >>> >>> I'm currently looking into adding errata quirks found in the Linux >>> driver to see if that helps. JFYI. >>> >>> >> Right, there are a few mentioned in the docs, however I've not been able >> to reproduce any of them, but please let me know what you find out!! >> >> > By removing the riser card I can no longer easily reproduce > the corruption but colleagues said it's still reproduceable > even without the riser card. I'm doing more testing now, > but so far I couldn't reproduce it. I tried several riser > cards, two different models, the issue is still the same; > reading 10 sectors gives one bit error (MSB bit) at one > byte. Do you have experience why using riser cards may be > a bad idea? > Hmm, I've seen bad behavior with PCI-X riser cards, I guess its because of poor design and the high speeds that the problems occur. Not much to do about it other than finding one that works or lowering the PCI-X bus speed. -Søren