From: Mark Lord <lkml@rtr.ca>
To: Greg KH <gregkh@suse.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Oliver Neukum <oneukum@suse.de>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Markus <lists4me@web.de>, Jeff Chua <jeff.chua.linux@gmail.com>,
"Antonino A. Daplas" <adaplas@gmail.com>,
linux-alpha@vger.kernel.org,
Stefan Becker <Stefan.Becker@nokia.com>, Andi Kleen <ak@suse.de>,
Dave Jones <davej@redhat.com>, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>, Thomas Gleixner <tglx@linutronix.de>,
Jakub Jelinek <jakub@redhat.com>,
Jeff Dike <jdike@linux.intel.com>,
user-mode-linux-devel@lists.sourceforge.net,
Adrian Bunk <bunk@kernel.org>
Subject: Re: [1/4] 2.6.23-rc6: known regressions
Date: Thu, 13 Sep 2007 09:21:35 -0400 [thread overview]
Message-ID: <46E9395F.2090300@rtr.ca> (raw)
In-Reply-To: <20070913093651.GA5077@suse.de>
Greg KH wrote:
> On Wed, Sep 12, 2007 at 10:50:26PM -0400, Mark Lord wrote:
>> Michal Piotrowski wrote:
>>> Hi all,
>>> Here is a list of some known regressions in 2.6.23-rc6.
>> ...
>>
>> Missing from the list:
>>
>> USB "autosuspend" feature (new in 2.6.23) breaks *lots* of devices.
>> Many have since been blacklisted in one-at-a-time discovery patches,
>> but that's really just the tip of the iceberg.
>>
>> This "feature" breaks a TON of user-visible things,
>> mostly USB storage devices (USB drives/pens, digicams, etc..).
>>
>> The functionality is broken for just too much stuff,
>> and needs to either be reverted or defaulted to "off" rather than "on".
>
> Ok, after conferring with Oliver this morning, I think the best solution
> here is to both revert the usb-storage suspend patch as it has some
> basic problems that can cause data loss, _and_ add the change to the
> kernel that by default disables autosuspend on all USB devices except
> hubs.
Sounds like a sane approach.
Hopefully the kinks can be worked out in time for a reattempt in 2.6.24.
I understand how important this stuff is for battery powered devices,
but it just doesn't appear to be ready yet.
Cheers
prev parent reply other threads:[~2007-09-13 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 16:58 [1/4] 2.6.23-rc6: known regressions Michal Piotrowski
2007-09-12 17:15 ` Linus Torvalds
2007-09-12 17:19 ` Thomas Gleixner
2007-09-12 17:38 ` Michal Piotrowski
2007-09-13 2:50 ` Mark Lord
2007-09-13 9:36 ` Greg KH
2007-09-13 13:21 ` 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=46E9395F.2090300@rtr.ca \
--to=lkml@rtr.ca \
--cc=Stefan.Becker@nokia.com \
--cc=adaplas@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=jakub@redhat.com \
--cc=jdike@linux.intel.com \
--cc=jeff.chua.linux@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists4me@web.de \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=oneukum@suse.de \
--cc=pavel@ucw.cz \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).