From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@osdl.org, Jiri Slaby <jirislaby@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: swsusp regression [Was: 2.6.17-mm1]
Date: Thu, 22 Jun 2006 14:11:57 -0700 [thread overview]
Message-ID: <20060622211157.GA15669@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0606221706450.5772-100000@iolanthe.rowland.org>
On Thu, Jun 22, 2006 at 05:09:43PM -0400, Alan Stern wrote:
> On Thu, 22 Jun 2006, Jiri Slaby wrote:
>
> > > ages. The "bogus requests" are attempts by the user to suspend a USB
> > > device (by writing to /sys/devices/.../power/state) without first
> > > suspending all its children and interfaces.
> > >
> > > (This can't happen when doing a global suspend because the PM core
> > > iterates through the entire device tree. It matters only for "runtime" or
> > > "selective" suspend.)
> >
> > But everything I did is:
> > echo reboot > /sys/power/disk
> > echo disk > /sys/power/state
> >
> > No writing anywhere else.
>
> You misunderstood. I meant that attempts to suspend a USB device without
> first suspending all its children and interfaces can't happen when doing a
> global suspend. That's still true.
>
> Your problem occurred because even though the PM core did _attempt_ to
> suspend the new children added by Greg's patch, it didn't _succeed_
> because the patch did not provide suspend or resume methods.
Which because they are virtual "devices" they do not need a suspend or
resume method, so not having any is just fine. If we abort because of
something like this, the core logic is quite broken...
thanks,
greg k-h
next prev parent reply other threads:[~2006-06-22 21:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060621034857.35cfe36f.akpm@osdl.org>
2006-06-21 21:48 ` swsusp regression [Was: 2.6.17-mm1] Jiri Slaby
2006-06-21 22:14 ` Mattia Dongili
2006-06-21 22:18 ` Mattia Dongili
2006-06-22 6:19 ` Greg KH
2006-06-22 7:46 ` [linux-pm] " Andrew Morton
2006-06-22 8:25 ` Jeremy Fitzhardinge
2006-06-22 15:51 ` Alan Stern
2006-06-22 17:17 ` Jeremy Fitzhardinge
2006-06-22 18:46 ` Greg KH
2006-06-22 19:07 ` [linux-pm] " Greg KH
2006-06-22 19:57 ` Alan Stern
2006-06-22 20:22 ` Greg KH
2006-06-22 20:38 ` Jiri Slaby
2006-06-22 21:09 ` Alan Stern
2006-06-22 21:11 ` Greg KH [this message]
2006-06-22 16:04 ` [linux-pm] " Frederik Deweerdt
2006-06-22 16:25 ` Andrew Morton
2006-06-22 19:07 ` [linux-pm] " Frederik Deweerdt
2006-06-23 9:02 ` Frederik Deweerdt
2006-06-23 9:10 ` [linux-pm] " Pavel Machek
2006-06-23 9:31 ` Andrew Morton
2006-06-23 12:12 ` Frederik Deweerdt
2006-06-23 12:57 ` Pavel Machek
2006-06-23 13:47 ` Frederik Deweerdt
2006-06-23 19:57 ` Andrew Morton
2006-06-26 9:00 ` [linux-pm] " Frederik Deweerdt
2006-06-23 19:41 ` Russell King
2006-06-23 20:22 ` Dave Jones
2006-06-23 21:10 ` Rafael J. Wysocki
2006-06-23 22:11 ` Pavel Machek
2006-06-23 23:53 ` [linux-pm] " Frederik Deweerdt
2006-06-24 17:16 ` Rafael J. Wysocki
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=20060622211157.GA15669@kroah.com \
--to=greg@kroah.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--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