From: David Brownell <david-b@pacbell.net>
To: Len Brown <lenb@kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
gregkh@suse.de, linux-acpi@vger.kernel.org,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: USB D3 vs system S3
Date: Tue, 8 Jan 2008 13:55:30 -0800 [thread overview]
Message-ID: <200801081355.31154.david-b@pacbell.net> (raw)
In-Reply-To: <200801081547.00473.lenb@kernel.org>
On Tuesday 08 January 2008, Len Brown wrote:
> FYI,
> I think we may have an issue here where the entire Linux suspend order
> is being proposed to change, when in fact the underlying issue
> may really be that USB is in D3 on S3 for this box when it is
> not supposed to be deeper below D1.
>
> http://bugzilla.kernel.org/show_bug.cgi?id=9528
>
I still run my system with those patches to hook up PCI and USB
wakeup mechanisms to the ACPI tables. ISTR that they got pulled
at some point because they caused some system to wake up immediately
instead of suspending ... sound familiar?
If that immediate-wake problem is now otherwise resolved, maybe it's
time to revisit the merge of those patches. (From *LAST* January
I think, in at least one otherwise-mergeable incarnation ...)
In the absense of those patches, nothing is hooking up USB to
the relevant ACPI tables.
Want I should repost my latest version of those patches? They
apply cleanly against RC7.
- Dave
next prev parent reply other threads:[~2008-01-08 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 20:47 USB D3 vs system S3 Len Brown
2008-01-08 21:09 ` Rafael J. Wysocki
2008-01-08 21:55 ` David Brownell [this message]
2008-01-09 0:09 ` Carlos Corbacho
2008-01-09 12:51 ` Carlos Corbacho
2008-01-09 16:07 ` Alan Stern
2008-01-09 16:38 ` Carlos Corbacho
2008-01-09 17:16 ` Alan Stern
2008-01-09 21:03 ` David Brownell
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=200801081355.31154.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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