From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Ornati Subject: Re: [re] libata: blacklist NCQ on Seagate Barracuda ST380817AS Date: Tue, 3 Mar 2009 20:50:34 +0100 Message-ID: <20090303205034.6fa9a5d5@fastwebnet.it> References: <49AAB796.1010709@fisher-privat.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49AAB796.1010709-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Alexey Fisher Cc: Kernel Testers List , Tejun Heo , Jeff Garzik On Sun, 01 Mar 2009 17:28:06 +0100 Alexey Fisher wrote: > Commit da6f0ec2d54acf545e784363aa5bad0dafc5ffa8 > libata: blacklist NCQ on Seagate Barracuda ST380817AS > > I tested Seagate Barracuda ST380817AS on my system without the blacklist > entry on system with ext4 fs and it seems to work. Two days with > normal load, tar, kvm, torrent... i can't reproduce the error described > in this commit. > > I use board with ICH10R south bridge, AHCI mode. In my case it was happening _only_ with barriers enabled (like ext3 mounted with "barrier=1") or with XFS (that enables barriers by default). Does it survives an untar with barriers? -- Paolo Ornati Linux 2.6.29-rc6-00216-g778ef1e on x86_64