From: Mark Lord <kernel@teksavvy.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Lin Ming <ming.m.lin@intel.com>
Subject: Re: Hotplug borked after suspend/resume in Linux-3.3 ?
Date: Tue, 17 Apr 2012 17:14:47 -0400 [thread overview]
Message-ID: <4F8DDD47.8070809@teksavvy.com> (raw)
In-Reply-To: <4F8DD7AB.2050709@pobox.com>
On 12-04-17 04:50 PM, Jeff Garzik wrote:
> On 04/17/2012 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?
>
> hrm... smells like runtime PM stuff.
>
> Can you try "libata: disable runtime pm for hotpluggable port"?
>
> You probably have to edit ahci_port_pluggable() to make it unconditionally return true.
Okay tried the ahci_port_pluggable() hack, no difference.
The patch above fixes the issue on two systems here with motherboard SATA,
and has zero effect on the AHCI ExpressCard in my notebook.
The notebook issue is definitely PCIe hotplug b0rkage, not libata.
I fixed that once, a few years ago, but it seems to have crept back
into the kernel again when I wasn't paying close attention.
Dunno when, could have been there for ages now.
But the libata regression is new. And fixable here, at least.
I think whatever broke it should get reverted ASAP until you are
happy with a more permanent solution.
Otherwise the solution above is what I'm now patching into all of my systems here.
Cheers
prev parent reply other threads:[~2012-04-17 21:14 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
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 [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=4F8DDD47.8070809@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=ming.m.lin@intel.com \
/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).