[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DF28360.1090206@teksavvy.com>
Date: Fri, 10 Jun 2011 16:49:36 -0400
From: Mark Lord <kernel@...savvy.com>
To: Jeff Garzik <jgarzik@...ox.com>
CC: Tejun Heo <htejun@...il.com>,
Bruce Stenning <b.stenning@...igovision.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>
Subject: Re: sata_mv port lockup on hotplug (kernel 2.6.38.2)
On 11-06-10 01:39 PM, Jeff Garzik wrote:
> On 06/10/2011 01:32 PM, Mark Lord wrote:
>> On 11-06-10 10:01 AM, Tejun Heo wrote:
>>> Hello,
>>>
>>> (cc'ing Jeff)
>>>
>>> On Fri, Jun 10, 2011 at 08:28:51AM -0400, Mark Lord wrote:
>>>> Tejun, did this ever go upstream and to -stable ??
>>>> I'm asking because I see the same issue with other SATA controllers,
>>>> in particular with sata_sil boards. Hot plug generally works _once_
>>>> per port, and then stops working.
>>>
>>> The patch is still pending,
>>>
>>> http://article.gmane.org/gmane.linux.ide/49613
>>>
>>> I don't think it would be wise to include the patch for -stable tho.
>>> It's not a regression fix and has some possibility of introducing
>>> regressions, so....
>>
>> Not a regression fix? Excuse me?
>> SATA hotplug always used to work fine,
>> and is more or less essential to reboot-free operations.
>
> I can move it from #upstream (linux-next) to #upstream-fixes, if we feel it is
> sufficient urgent. It seemed like it needed more testing, but maybe the best
> way to do that is #upstream-fixes?
>
> Was mainly a -rc question, to me.
Well, it's not getting any testing sitting outside of the kernel right now.
Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists