linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Kasimir Mueller <kjm@kasimir.mueller.de>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata , Silicon Image 3124
Date: Wed, 14 Nov 2007 11:10:57 +0900	[thread overview]
Message-ID: <473A5931.4040704@gmail.com> (raw)
In-Reply-To: <473A11B4.5030409@kasimir.mueller.de>

[linux-ide added back. please don't drop cc list]

Kasimir Mueller wrote:
> Tejun Heo schrieb:
>> Kasimir Müller wrote:
>>  
>>> Nov 12 19:28:42 linux kernel: ata6.02: cmd
>>> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
>>> Nov 12 19:28:42 linux kernel:          res
>>> 40/00:00:09:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
>>>     
>>
>> That's flush timing out, which isn't good.
>>
>> 1. Are the errors localized to ata6.02?
>>   
> I think it's ata6.01

The above message says 6.02 tho.  Anyways, if the errors are localized
to one drive, please swap that drive with another drive.  Do the errors
follow the drive or stay with the slot?

>> 2. Is FLUSH always involved (ie. is cmd always ea)?
>>   
> yes

Hmmm... okay.  That sounds like a dying drive to me.  What does
'smartctl -a /dev/sdX' say?

>> 3. If you disable NCQ, what do errors look like?
>>   
> I put all disk-drives in the blacklist , without a change

So, NCQ isn't the problem.

ATM, it sounds like a dying drive to me.  Please double check the errors
are localized to one drive, check smartctl log and try to verify as
written above.

Thanks.

-- 
tejun

      parent reply	other threads:[~2007-11-14  2:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 18:57 libata , Silicon Image 3124 Kasimir Müller
2007-11-13  1:22 ` Tejun Heo
     [not found]   ` <473A11B4.5030409@kasimir.mueller.de>
2007-11-14  2:10     ` 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=473A5931.4040704@gmail.com \
    --to=htejun@gmail.com \
    --cc=kjm@kasimir.mueller.de \
    --cc=linux-ide@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).