All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: Hotplug borked after suspend/resume in Linux-3.3 ?
Date: Tue, 17 Apr 2012 17:16:48 -0400	[thread overview]
Message-ID: <4F8DDDC0.2010609@teksavvy.com> (raw)
In-Reply-To: <4F8DDC4F.8060103@pobox.com>

On 12-04-17 05:10 PM, Jeff Garzik wrote:
> On 04/17/2012 05:05 PM, Mark Lord wrote:
>> On 12-04-17 04:57 PM, Jeff Garzik wrote:
>>> On 04/17/2012 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.
>>>
>>> The vast majority of "hotpluggable" ports are not necessarily covered by this patch.
>>
>>
>> And what majority of ports are currently broken by linux-3.3 ?
>> Any idea of what the offending commit may have been,
>> so I can test against that and perhaps get it reverted then?
>>
>> So far, my sample of three systems are all broken with this kernel.
>> That's definitely "regression" territory.  :)
> 
> Right -- rather than breaking a bunch and fixing a few, we might just need to revert the runtime pm
> stuff altogether.
> 
> Commits to look at include
> 
>     966f1212e1ac5fe3ddf04479d21488ddb36a2608
>     33574d68ae41ccbc6686cfabd965c685285c58a0
>     e90b1e5a6e04c8892007ff8db20ef6d4fbdb5402
>     9ee4f3933930abf5cc34f8e9d69fe0e08c18f602
>     5ef41082912bdfcb33fa53b8dba2ad17dea2ef90
>     9a6d6a2ddabbd32c07f6a38b659e5f3db319fa5a
> 

Or perhaps there's a simpler solution/patch, maybe a one-liner
to change the boot-up default to "no runtime PM until enabled" or something.

Probably less risky if the changes are as pervasive as you suggest.


  reply	other threads:[~2012-04-17 21:16 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 [this message]
     [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=4F8DDDC0.2010609@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.