linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Hotplug borked after suspend/resume in Linux-3.3 ?
Date: Tue, 17 Apr 2012 17:02:11 -0400	[thread overview]
Message-ID: <4F8DDA53.206@teksavvy.com> (raw)
In-Reply-To: <4F8DD834.5070000@teksavvy.com>

On 12-04-17 04:53 PM, Mark Lord wrote:
> On 12-04-17 04:48 PM, Mark Lord wrote:
>> On 12-04-17 04:38 PM, Mark Lord wrote:
>>> Okay, so why isn't SATA hotplug working in linux-3.3.2 ?
>>> I don't know when it stopped working, but it's a blooming pain in the sysadmin.
>>>
>>> I need to hotplug a SATA drive into an AHCI port,
>>> preferably without having to reboot first.
>>>
>>> Is there a patch available already for this regression?
>>
>>
>> Answering my own question, this patch appears to address the issue.
>> I'll test and report back again shortly:
>>
>>     http://patchwork.ozlabs.org/patch/146326/
>>
>> Odd that it's been sitting in various people's inboxes since 3.3-rc1
>> and hasn't been pushed out yet.
> 
> Ahh.. perhaps because it doesn't fix the problem I'm seeing here.
> 
> Oh well, anyone else got a fix for this regression yet?
> Even doing a rescan-scsi-bus doesn't work on the closed down ports.
> 
> Basically, any unoccupied AHCI port is dead to the world
> after a simple suspend/resume (RAM) cycle.  On one of my machines
> I can hot unplug/replug the ExpressCard adapter to recover,
> but that doesn't work so well for built-in SATA/eSATA ports.


Mmm.. on my little Atom ZBOX systems, the patch linked above
"Patchwork [v2] libata: disable runtime pm for hotpluggable port"
_does_ appear to fix the issue.

Maybe my notebook is suffering from the ExpressCard not being resumed properly,
which would be a PCI issue most likely.

Anyway, one issue at a time:  The "disable runtime pm" patch seems to
be the regression fix I'm looking for here so that I can use SATA hotplug
after a suspend/resume.

Why isn't this upstream as a regression fix yet?

Thanks

  reply	other threads:[~2012-04-17 21:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 20:38 Hotplug borked after suspend/resume in Linux-3.3 ? Mark Lord
2012-04-17 20:48 ` Mark Lord
2012-04-17 20:51   ` Tejun Heo
2012-04-17 20:53   ` Mark Lord
2012-04-17 21:02     ` Mark Lord [this message]
2012-04-17 21:05       ` cwillu
2012-04-18 17:10         ` Martin Mokrejs
2012-04-18 17:29           ` Jeff Garzik
2012-04-18 17:44             ` Martin Mokrejs
2012-04-18 18:23               ` Martin Mokrejs
2012-04-18 18:32               ` Martin Mokrejs
2012-04-19  1:31                 ` Lin Ming
     [not found]                 ` <CAF1ivSYqzjv10F+sdYkR_jdTZvzKP1=_ZwgNDj2njnmb6uaenA@mail.gmail.com>
2012-04-19  8:16                   ` Lin Ming
2012-04-19 17:28                     ` Martin Mokrejs
2012-04-19 18:22                     ` Martin Mokrejs
2012-04-20  1:46                       ` Lin Ming
2012-04-20  2:37                     ` Grant Grundler
2012-04-26  9:29                       ` Gwendal Grignou
2012-04-26 13:06                         ` Lin Ming
2012-04-26 16:50                           ` Gwendal Grignou
2012-05-03  1:26                         ` Lin Ming
2012-05-19 23:58             ` [PATCH 3.3.y] libata: forbid port runtime pm by default, fixing regression Jonathan Nieder
2012-05-24 17:30               ` Greg KH
2012-04-17 21:04     ` Hotplug borked after suspend/resume in Linux-3.3 ? Jeff Garzik
2012-04-17 20:57   ` Jeff Garzik
2012-04-17 21:05     ` Mark Lord
2012-04-17 21:10       ` Jeff Garzik
2012-04-17 21:16         ` Mark Lord
     [not found]           ` <CAF1ivSbEWJ18vV1ZqTnzWuZ5AXKwj+0pPPzCWUmnT_JKwKKQ2w@mail.gmail.com>
2012-04-18  1:29             ` Lin Ming
2012-04-18  1:37               ` Mark Lord
2012-04-18  1:46                 ` Mark Lord
2012-04-18  6:18                   ` Jeff Garzik
2012-04-18  1:52         ` Lin Ming
2012-04-18  2:28           ` Jeff Garzik
2012-04-17 20:50 ` Jeff Garzik
2012-04-17 21:07   ` Mark Lord
2012-04-17 21:14   ` 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=4F8DDA53.206@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.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).