linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Jacobo Pantoja <jacobopantoja@gmail.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [nForce4] - Repeatable issues with nForce 4
Date: Tue, 2 Dec 2014 10:17:10 -0500	[thread overview]
Message-ID: <20141202151710.GA6596@htj.dyndns.org> (raw)
In-Reply-To: <CADLC3L2nTrowBeBU=TRVELUjRahOnJxqkUTqxXSbjj9sQ+U2NQ@mail.gmail.com>

On Sun, Nov 30, 2014 at 11:52:40PM -0600, Robert Hancock wrote:
> Looks like it's doing a hardreset now (apparently successfully).
> However the reason it still does a softreset anyway is this at the end
> of nv_hardreset:
> 
>         /* device signature acquisition is unreliable */
>         return -EAGAIN;
> 
> Try changing that to:
> 
>         return 0;
> 
> and see if that changes the behavior. That should make it skip the
> soft-reset. Whether or not the device works or not after that, or if
> it still locks up at some later point, we'll see.

There have been some PMP devices which have trouble with SRST and
acquiring device signature, so there are link flags to deal with them
- ATA_LFLAG_NO_[SH]RST and ATA_LFLAG_ASSUME_*.  Not sure how useful
they'd be in this case tho.

Thanks.

-- 
tejun

      parent reply	other threads:[~2014-12-02 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAO18KQjN88PjQSh0bMo+YgqmSSE--eaxL3Lgo5QeUjg3vMu6iQ@mail.gmail.com>
2014-09-14  9:37 ` [nForce4] - Repeatable issues with nForce 4 Tejun Heo
2014-09-14 20:04   ` Robert Hancock
     [not found]   ` <CADLC3L397fmyWa1CpzZfkTkZavyKPG4M7JccdgbgTRTsUp8VVQ@mail.gmail.com>
2014-09-15 12:41     ` Jacobo Pantoja
2014-09-16  2:47       ` Robert Hancock
2014-11-30 11:03         ` Jacobo Pantoja
2014-12-01  0:01           ` Robert Hancock
2014-12-01  4:40             ` Jacobo Pantoja
2014-12-01  5:52               ` Robert Hancock
2014-12-01 22:37                 ` Jacobo Pantoja
2014-12-02  1:38                   ` Robert Hancock
2014-12-02 15:17                 ` 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=20141202151710.GA6596@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=hancockrwd@gmail.com \
    --cc=jacobopantoja@gmail.com \
    --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).