From: Jiri Slaby <jirislaby@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Rafael J. Wysocki" <rjw@suse.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
Date: Fri, 04 Feb 2011 20:38:31 +0100 [thread overview]
Message-ID: <4D4C55B7.4010005@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1102041426380.1877-100000@iolanthe.rowland.org>
On 02/04/2011 08:33 PM, Alan Stern wrote:
> On Fri, 4 Feb 2011, Jiri Slaby wrote:
>
>>>> It seems to suffice... No hangs still. Should I enable pm_async back
>>>> again to confirm the issue is still present?
>>>
>>> Yes, please, it would be good to know for sure.
>>
>> Ok, confirmed right now :).
>>
>> I disabled pm_async for USB again. What do you suggest next?
>
> What happens if you leave pm_async enabled but unplug all the USB
> devices before suspending?
Then I cannot suspend at all (ENOINPUTDEVICE)... And this would be
painful as the bug occurs once a week or so.
> If there are any USB devices you can't
> unplug, you can get an equivalent result by unconfiguring the root
> hubs:
>
> for a in /sys/bus/usb/devices/usb* ; do
> echo 0 >$a/bConfigurationValue
> done
Well, I can put this into suspend/resume scripts. What's the opposite
operation? 1 > $a/bConfigurationValue?
thanks,
--
js
next prev parent reply other threads:[~2011-02-04 19:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 0:34 mmotm 2010-12-02-16-34 uploaded akpm
2010-12-03 17:33 ` mmotm 2010-12-02-16-34 uploaded (acpi_video) Randy Dunlap
2010-12-03 17:37 ` mmotm 2010-12-02-16-34 uploaded (netfilter-related) Randy Dunlap
2010-12-03 21:43 ` mmotm 2010-12-02-16-34 uploaded Zimny Lech
2010-12-04 0:39 ` Stephen Rothwell
2010-12-06 17:11 ` Randy Dunlap
2010-12-05 8:25 ` Resume hangs [was: mmotm 2010-12-02-16-34 uploaded] Jiri Slaby
2010-12-05 13:08 ` Rafael J. Wysocki
2010-12-13 10:04 ` Jiri Slaby
2010-12-13 21:10 ` Rafael J. Wysocki
2010-12-14 22:08 ` Jiri Slaby
2010-12-14 22:22 ` Rafael J. Wysocki
2011-01-06 14:18 ` Jiri Slaby
2011-01-20 15:23 ` Jiri Slaby
2011-01-20 21:02 ` Rafael J. Wysocki
2011-01-21 9:16 ` Jiri Slaby
2011-01-31 21:37 ` Jiri Slaby
2011-01-31 21:40 ` Jiri Slaby
2011-01-31 22:00 ` Rafael J. Wysocki
2011-02-04 18:33 ` Jiri Slaby
2011-02-04 19:33 ` [linux-pm] " Alan Stern
2011-02-04 19:38 ` Jiri Slaby [this message]
2011-02-04 20:07 ` Alan Stern
2011-02-22 8:45 ` Jiri Slaby
2011-02-22 15:36 ` Alan Stern
2011-02-23 11:58 ` Jiri Slaby
2011-02-23 15:59 ` Alan Stern
2011-02-24 18:41 ` Jiri Slaby
2011-03-08 9:13 ` Jiri Slaby
2011-03-08 19:25 ` Rafael J. Wysocki
2011-03-08 20:31 ` Jiri Slaby
2011-03-08 22:12 ` Rafael J. Wysocki
2011-03-08 22:14 ` Jiri Slaby
2011-03-08 22:15 ` Rafael J. Wysocki
2011-03-08 22:16 ` Rafael J. Wysocki
2011-03-08 22:18 ` Jiri Slaby
2011-03-30 14:11 ` Jiri Slaby
2011-03-30 15:10 ` Alan Stern
2011-03-30 20:02 ` Rafael J. Wysocki
2011-03-30 21:19 ` Alan Stern
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=4D4C55B7.4010005@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@suse.com \
--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 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).