- To: Tejun Heo <tj@xxxxxxxxxx>
- Subject: Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- From: Mark Lord <kernel@xxxxxxxxxxxx>
- Date: Thu, 16 Feb 2012 09:20:22 -0500
- Cc: Jeff Garzik <jeff@xxxxxxxxxx>, Brian Norris <computersforpeace@xxxxxxxxx>, Lin Ming <ming.m.lin@xxxxxxxxx>, Norbert Preining <preining@xxxxxxxx>, "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, "stern@xxxxxxxxxxxxxxxxxxx >> Alan Stern" <stern@xxxxxxxxxxxxxxxxxxx>, linux-ide@xxxxxxxxxxxxxxx, Linux PM mailing list <linux-pm@xxxxxxxxxxxxxxx>, "Rafael J. Wysocki" <rjw@xxxxxxx>, Jian Peng <jipeng2005@xxxxxxxxx>, Kevin Cernekee <cernekee@xxxxxxxxx>, valdis.kletnieks@xxxxxx
- In-reply-to: <20120215183139.GC24986@google.com>
- List-id: <linux-ide.vger.kernel.org>
- User-agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
On 12-02-15 01:31 PM, Tejun Heo wrote:
> Hey, Jeff.
>
> On Wed, Feb 15, 2012 at 01:29:29PM -0500, Jeff Garzik wrote:
>> A module parameter is not necessarily the best/only option.
>> ahci_platform already has infrastructure set up to deal with
>> platform-specific quirks. An internal flag seems more appropriate
>> to enable automatic handling of this on the specific platforms where
>> it applies (plus the revert Tejun has already mentioned).
>
> The problem is that there's no way to identify the controller in
> question, so we can't do this automatically, so might just as well do
> it in the simplest way for now. :(
Well, a module parameter is no good,
because that method would affect all attached controllers
rather than just the one(s) with the issue.
Something in sysfs perhaps.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
- References:
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
[Linux Filesystems]
[Linux SCSI]
[Linux RAID]
[Git]
[Kernel Newbies]
[Linux Newbie]
[Share Photos]
[Security]
[Netfilter]
[Bugtraq]
[Photo]
[Yosemite]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Samba]
[Video 4 Linux]
[Device Mapper]
[Linux Resources]