Date: Thu, 19 Oct 2006 14:41:39 +0400 From: Ruslan Ermilov <ru@freebsd.org> To: S?ren Schmidt <sos@deepcore.dk> Cc: freebsd-current@freebsd.org, Soren Schmidt <sos@freebsd.org> Subject: Re: support for marvell sata chips? Message-ID: <20061019104139.GA11216@rambler-co.ru> In-Reply-To: <45367E22.80207@deepcore.dk> References: <E27072CC-3CC7-4C40-A139-8674D44FA140@maubi.net> <4535E88B.9070108@freebsd.org> <20061018134019.GB21654@rambler-co.ru> <45367E22.80207@deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
--IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 <HDS725050KLA360 K2AOAB0A> at ata8-master SATA150 > ># dmesg | grep ^ata8 > >ata8: <ATA channel 6> on atapci0 > ># dmesg | grep ^atapci0 > >atapci0: <Marvell 88SX6081 SATA300 controller> 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 > Right, there are a few mentioned in the docs, however I've not been able= =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? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFN1ZjqRfpzJluFF4RAiDIAKCVUEMsWaxrLITnbh46dWf82SBMEwCdEiGv ZZ0ZyUAKwM3RPm7t7rV4jvo= =+rIY -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061019104139.GA11216>