From: Tejun Heo <tj@kernel.org>
To: linux-ide@vger.kernel.org
Subject: Re: SiI3811 PATA->SATA bridge not working on OpenRD-Base
Date: Tue, 01 Dec 2009 15:08:08 +0900 [thread overview]
Message-ID: <4B14B2C8.6080002@kernel.org> (raw)
In-Reply-To: <20091113212332.GD1965@twin.sascha.silbe.org>
Hello,
On 11/14/2009 06:23 AM, Sascha Silbe wrote:
> Nov 13 21:05:02 flatty kernel: ata2: hard resetting link
> Nov 13 21:05:03 flatty kernel: ata2: SATA link up 1.5 Gbps (SStatus 113
> SControl F300)
Hmmm... that's HSM violation.
> Is there a way to figure out what component is to blame? I.e. whether
> its the SATA host adapter driver (sata_mv) or something more generic?
In libata-sff.c there are several places which set AC_ERR_HSM. They
store the reason why they're setting it using ata_eh_push_desc() but
for EH commands those messages aren't printed out (we probably need to
fix that). Anyways, can you please conver those to printk's and see
which one is setting HSM error?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-12-01 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 21:23 SiI3811 PATA->SATA bridge not working on OpenRD-Base Sascha Silbe
2009-12-01 6:08 ` Tejun Heo [this message]
2009-12-14 19:59 ` Sascha Silbe
2009-12-14 23:07 ` Tejun Heo
2009-12-15 0:51 ` Mark Lord
2009-12-15 1:02 ` Mark Lord
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=4B14B2C8.6080002@kernel.org \
--to=tj@kernel.org \
--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).