From owner-freebsd-current@FreeBSD.ORG Thu Oct 19 12:51:27 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 5710B16A403; Thu, 19 Oct 2006 12:51:27 +0000 (UTC) (envelope-from if@hetzner.co.za) Received: from hetzner.co.za (office.cpt2.host-h.net [196.7.147.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9756943D94; Thu, 19 Oct 2006 12:51:18 +0000 (GMT) (envelope-from if@hetzner.co.za) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GaXMe-000Muq-Ft; Thu, 19 Oct 2006 14:51:12 +0200 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= From: Ian FREISLICH In-Reply-To: Message from =?ISO-8859-1?Q?S=F8ren_Schmidt?= of "Thu, 19 Oct 2006 13:23:09 +0200." <4537601D.3090107@deepcore.dk> X-Attribution: BOFH Date: Thu, 19 Oct 2006 14:51:12 +0200 Message-Id: Cc: freebsd-current@FreeBSD.ORG, Ruslan Ermilov , 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 12:51:27 -0000 =?ISO-8859-1?Q?S=F8ren_Schmidt?= wrote: > Ruslan Ermilov wrote: > > On Wed, Oct 18, 2006 at 09:18:58PM +0200, S?ren Schmidt wrote: > > =20 > >> Ruslan Ermilov wrote: > >> =20 > >>> 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= > =20 > >>> 0xfc900000-0xfc9fffff irq 20 at device 1.0 on pci2 > >>> # dd if=3D/dev/ad16 bs=3D128k count=3D1024 | md5 > >>> 1024+0 records in > >>> 1024+0 records out > >>> 134217728 bytes transferred in 2.091913 secs (64160282 bytes/sec) > >>> 669aa0b8c706f06d3d41aae95d4a3cf1 > >>> # dd if=3D/dev/ad16 bs=3D128k count=3D1024 | md5 > >>> 1024+0 records in > >>> 1024+0 records out > >>> 134217728 bytes transferred in 2.092598 secs (64139273 bytes/sec) > >>> 5b92918e4beaadf5a7ff74829b9ab9ce > >>> # dd if=3D/dev/ad16 bs=3D128k count=3D1024 | md5 > >>> 1024+0 records in > >>> 1024+0 records out > >>> 134217728 bytes transferred in 2.096472 secs (64020758 bytes/sec) > >>> d56fbdee36d70c8d6fcae6ea7b7550a7 > >>> #=20 > >>> > >>> I'm currently looking into adding errata quirks found in the Linux > >>> driver to see if that helps. JFYI. > >>> =20 > >>> =20 > >> Right, there are a few mentioned in the docs, however I've not been ab= > le=20 > >> to reproduce any of them, but please let me know what you find out!! > >> > >> =20 > > 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? > > =20 > Hmm, I've seen bad behavior with PCI-X riser cards, I guess its because=20 > 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=20 > the PCI-X bus speed. Out of interest, are these "active" or "passive" risers? I have several systems each with 6 slots on 2 risers. 3 on a passive backplane and 3 on the active backplane. I've only ever used the active backplane and I've never noticed any issues. Ian -- Ian Freislich