linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux@sun7.cn,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>, Peer Chen <pchen@nvidia.com>,
	Kuan Luo <kluo@nvidia.com>,
	stable@kernel.org
Subject: Re: [stable] [PATCH #upstream-fixes] sata_nv: disable hardreset for generic
Date: Thu, 2 Oct 2008 12:57:31 -0700	[thread overview]
Message-ID: <20081002195731.GA20902@kroah.com> (raw)
In-Reply-To: <48E41447.6000103@kernel.org>

On Thu, Oct 02, 2008 at 09:22:31AM +0900, Tejun Heo wrote:
> Greg KH wrote:
> > On Mon, Sep 08, 2008 at 09:17:30PM +0200, Tejun Heo wrote:
> >> Tejun Heo wrote:
> >>> From 2.6.26, libata is defaulting to hardreset for various reasons one
> >>> of them being unifying probing, hotplug and EH reset paths uniform.
> >>> Previously, broken hardreset could go unnoticed as it wasn't used
> >>> during probing but when something goes wrong or after hotplug the
> >>> problem will surface and bite hard.
> >>>
> >>> OSDL bug 11195 reports that sata_nv generic flavor falls into this
> >>> category.  Hardreset itself succeeds but PHY stays offline after
> >>> hardreset.  I tried longer debounce timing but the result was the
> >>> same.
> >>>
> >>>   http://bugzilla.kernel.org/show_bug.cgi?id=11195
> >>>
> >>> So, it seems we'll have to drop hardreset from the generic flavor.
> >>>
> >>> Signed-off-by: Tejun Heo <tj@kernel.org>
> >>> Cc: Peer Chen <pchen@nvidia.com>
> >> This one definitely should go into -stable too.  The original patch is...
> >>
> >> http://article.gmane.org/gmane.linux.ide/34077/raw
> > 
> > Now applied, thanks.
> 
> Greg, can you please hold a bit before releasing this?  This patch
> accidentally disables hardreset for all flavors of nv controllers which
> causes problems for ck804.  A later patch to only apply it to generic
> went in but it then broke nf2 flavor, so it seems generic and nf2
> require this workaround but ck804 doesn't like the workaround.  I've
> asked a reporter to test to apply the workaround only to generic and nf2
> and will forward the third patch as soon as it's confirmed.  So, please
> wait till the third one is ready.

Ok, I've dropped:
	sata_nv-disable-hardreset-for-generic.patch
from the 2.6.26-stable queue for now.

If you get it all working, please resend all of the patches that you
wish me to pick up for a -stable release (well send them to
stable@kernel.org, not me directly.)

thanks,

greg k-h

      reply	other threads:[~2008-10-02 20:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03  5:22 [RFC PATCH #upstream-fixes] sata_nv: disable hardreset for generic Tejun Heo
2008-08-04  9:20 ` Peer Chen
2008-08-13  6:51   ` Tejun Heo
2008-08-29 14:13 ` [PATCH " Tejun Heo
2008-09-08 16:16   ` Jeff Garzik
2008-09-08 19:17   ` Tejun Heo
2008-10-01 23:22     ` [stable] " Greg KH
2008-10-02  0:22       ` Tejun Heo
2008-10-02 19:57         ` Greg KH [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=20081002195731.GA20902@kroah.com \
    --to=greg@kroah.com \
    --cc=jeff@garzik.org \
    --cc=kluo@nvidia.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@sun7.cn \
    --cc=pchen@nvidia.com \
    --cc=stable@kernel.org \
    --cc=tj@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).