From: Mark Lord <lkml@rtr.ca>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
linux-usb-devel@lists.sourceforge.net, Greg KH <greg@kroah.com>
Subject: Re: 2.6.14-rc4-mm1: USB suspend regression
Date: Wed, 19 Oct 2005 10:53:03 -0400 [thread overview]
Message-ID: <43565DCF.5020404@rtr.ca> (raw)
In-Reply-To: <200510191514.00186.rjw@sisk.pl>
None of the recent kernels can resume-from-ram reliably for me
if I use CONFIG_USB_SUSPEND (set). But with that option UNset,
suspend/resume to/from RAM works very well.
BUT.. new in 2.6.14-rc*, is that the ehci_hcd USB hispeed driver
no longer survives resume from ram. I have to unload/reload the
module to get hispeed USB after resume.
-ml
next prev parent reply other threads:[~2005-10-19 14:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 10:01 2.6.14-rc1-mm1: usb breaks suspend Pavel Machek
2005-10-17 10:01 ` Pavel Machek
2005-10-17 18:54 ` [linux-pm] " Alan Stern
2005-10-17 18:54 ` Alan Stern
2005-10-17 21:11 ` Rafael J. Wysocki
2005-10-18 1:01 ` Alan Stern
2005-10-18 1:01 ` [linux-pm] " Alan Stern
2005-10-19 13:13 ` 2.6.14-rc4-mm1: USB suspend regression (was: Re: 2.6.14-rc1-mm1: usb breaks suspend) Rafael J. Wysocki
2005-10-19 13:13 ` Rafael J. Wysocki
2005-10-19 14:53 ` Mark Lord [this message]
2005-10-19 16:03 ` 2.6.14-rc4-mm1: USB suspend regression Alan Stern
2005-10-20 3:21 ` Mark Lord
2005-10-19 16:18 ` 2.6.14-rc4-mm1: USB suspend regression (was: Re: 2.6.14-rc1-mm1: usb breaks suspend) Alan Stern
2005-10-19 20:18 ` Rafael J. Wysocki
2005-10-19 20:46 ` Alan Stern
2005-10-19 22:16 ` Rafael J. Wysocki
2005-10-20 15:30 ` Alan Stern
2005-10-18 0:13 ` [linux-pm] 2.6.14-rc1-mm1: usb breaks suspend Pavel Machek
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=43565DCF.5020404@rtr.ca \
--to=lkml@rtr.ca \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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.