From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Hancock Subject: Re: via 8237 sata errors Date: Sun, 30 May 2010 12:40:04 -0600 Message-ID: <4C02B104.4010900@gmail.com> References: <201005292046.06344.tfjellstrom@strangesoft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-gy0-f174.google.com ([209.85.160.174]:57654 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752206Ab0E3SqW (ORCPT ); Sun, 30 May 2010 14:46:22 -0400 In-Reply-To: <201005292046.06344.tfjellstrom@strangesoft.net> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Thomas Fjellstrom Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org On 05/29/2010 08:46 PM, Thomas Fjellstrom wrote: > I'm getting a rather nasty set of messages from dmesg when trying to use > a couple SATA II WD 2TB Green drives with an older system (via 8237 based). > They seem to work fine on a newer p35 based system. .. > [ 283.308963] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 > [ 283.309007] ata2.00: BMDMA stat 0x4 > [ 283.309045] ata2.00: failed command: READ DMA > [ 283.309089] ata2.00: cmd c8/00:08:08:08:30/00:00:00:00:00/e0 tag 0 dma 4096 in > [ 283.309091] res 41/04:00:08:08:30/00:00:00:00:00/e0 Emask 0x1 (device error) > [ 283.309171] ata2.00: status: { DRDY ERR } > [ 283.309207] ata2.00: error: { ABRT } > [ 283.324886] ata2.00: configured for UDMA/133 > [ 283.324904] ata2: EH complete It's not really clear why the drive is returning command aborted on a read, there's no other error bits to indicate an uncorrectable error or a CRC error. Is it only the one drive that's giving the errors?