From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: sata_mv port lockup on hotplug (kernel 2.6.38.2) Date: Fri, 10 Jun 2011 16:49:36 -0400 Message-ID: <4DF28360.1090206@teksavvy.com> References: <20110425162242.GB30828@mtj.dyndns.org> <20110426135027.GI878@htj.dyndns.org> <20110426155229.GM878@htj.dyndns.org> <20110430140109.GJ29280@htj.dyndns.org> <20110525094127.GF10146@htj.dyndns.org> <4DF20E03.9030502@teksavvy.com> <20110610140155.GJ15235@htj.dyndns.org> <4DF25526.9010800@teksavvy.com> <4DF256E1.4010703@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from ironport2-out.teksavvy.com ([206.248.154.181]:49604 "EHLO ironport2-out.pppoe.ca" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754736Ab1FJUtl (ORCPT ); Fri, 10 Jun 2011 16:49:41 -0400 In-Reply-To: <4DF256E1.4010703@pobox.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Jeff Garzik Cc: Tejun Heo , Bruce Stenning , "linux-kernel@vger.kernel.org" , "linux-ide@vger.kernel.org" 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