linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Matheus Izvekov <mizvekov@gmail.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	"Eric D. Mudama" <edmudama@gmail.com>,
	linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: AHCI + ST3160023AS + NCQ problems
Date: Mon, 12 Nov 2007 12:04:32 +0900	[thread overview]
Message-ID: <4737C2C0.10905@gmail.com> (raw)
In-Reply-To: <305c16960711062221u69e8eb37p1367b18343d0e2a5@mail.gmail.com>

Matheus Izvekov wrote:
>> Indeed removing the jumper of sdb made it be recognised as SATA2. But
>> sdc, what the problem is really about, is neither SATA2, not has any
>> jumper whatsoever. but both the manufacturer and libata claim it
>> supports NCQ.
>>
> 
> Anything i could do to help debug this? or perhaps it makes more sense
> to just blacklist NCQ for this particular drive?

Timeouts on modern SATA disks usually indicate hardware problem.

* unstable power supply (this is quite common)
* faulty cable or poorly seated connectors
* faulty drive or controller (seems rare)

Please apply common hardware debugging method - isolate problem by
changing configuration piece-by-piece and finding out to which component
the error actually belongs to.

-- 
tejun

  reply	other threads:[~2007-11-12  3:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30  0:13 AHCI + ST3160023AS + NCQ problems Matheus Izvekov
2007-10-30 10:52 ` Michael Tokarev
2007-10-30 13:15   ` Eric D. Mudama
2007-10-30 19:41     ` Michael Tokarev
2007-10-31  0:28       ` Matheus Izvekov
2007-11-07  6:21         ` Matheus Izvekov
2007-11-12  3:04           ` Tejun Heo [this message]
2007-12-07 20:54             ` Matheus Izvekov
2007-12-07 23:51               ` Tejun Heo
2007-12-08  0:39                 ` Matheus Izvekov
2007-12-09 10:39                   ` Tejun Heo

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=4737C2C0.10905@gmail.com \
    --to=htejun@gmail.com \
    --cc=edmudama@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mizvekov@gmail.com \
    --cc=mjt@tls.msk.ru \
    /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).