linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Chaitanya Huilgol <chaitanya@tidaldata.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ATA Bus Error with ICH7R and WDC WD7500AAKS-0
Date: Sun, 13 Apr 2008 11:29:12 +0900	[thread overview]
Message-ID: <48016FF8.2050908@gmail.com> (raw)
In-Reply-To: <20080402145628.c1eab7cb.akpm@linux-foundation.org>

Andrew Morton wrote:
> (cc linux-ide)
> 
> On Wed, 02 Apr 2008 18:51:05 +0530
> Chaitanya Huilgol <chaitanya@tidaldata.com> wrote:
> 
>> Hi,
>>
>> I am getting frequent 'ATA bus error' with ICH7R & WD7500AAKS-0.
>> I have tried the following combinations of NCQ and Write Cache disabled,
>> Write I/O is done with dd:
>> dd if=/dev/zero of=/dev/sdc bs=1048576
>>
>> (1) With Write Cache is Disabled and NCQ is enabled then the
>> errors are seen immediately on starting I/O
>> (2) With Write Cache enabled and NCQ enabled the errors are less frequent
>> (3) With NCQ disabled using "echo 1 >/sys/block/sdc/device/queue_depth"
>> the errors are rare but do occur.
>>
>> I have tried with different SATA Cables & Sata port combinations to
>> rule out cable/bad port issues.
>>
>> I am wondering if the WDC WD7500AAKS-0 is another candidate for NCQ blacklist?

PHY RDY changed is likely to indicate hardware problems.  Especially so 
on ICH ahci's which is one of the best supported and tested.  Can you 
please re-seat cable and move the harddrive to different power connector?

-- 
tejun

      reply	other threads:[~2008-04-13  2:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47F38841.9080300@tidaldata.com>
2008-04-02 21:56 ` ATA Bus Error with ICH7R and WDC WD7500AAKS-0 Andrew Morton
2008-04-13  2:29   ` Tejun Heo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48016FF8.2050908@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chaitanya@tidaldata.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).