From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: USB APM suspend
Date: Sun, 21 Sep 2003 17:58:35 -0700 [thread overview]
Message-ID: <3F6E493B.7070901@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0309191755590.763-100000@ida.rowland.org>
Alan Stern wrote:
> Here's a piece from my system log, when I did "apm --suspend". The
> usb_device_suspend/resume messages are things I added for debugging.
That's progress ... last time I tried APM on 2.6 it failed horribly.
(This was after working fine until recently.)
> Why was this routine called twice? (Don't be fooled by the timestamps; I
> think the "suspend D4 --> D3" message was created during the suspend but
> not read by syslogd until after the resume.)
That's happened for as long as I remember (2.4 also).
Still seems buglike to me, maybe 2.6 will finally squish it...
> Why doesn't usb_hcd_pci_resume() log a similar message when it is called?
> A simple oversight?
You mean, why didn't it announce its first resume? Basically, yes.
> Why was the host controller suspended _before_ its child USB devices?
Seems buglike to me, with the first call being wrong (before the
children were suspended) and the second being right (after).
> And why was it woken up twice?
The converse of the "suspended-twice" problem: first call right,
second call (after children) wrong.
- Dave
next prev parent reply other threads:[~2003-09-22 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 22:14 USB APM suspend Alan Stern
2003-09-19 22:24 ` Greg KH
2003-09-22 0:58 ` David Brownell [this message]
2003-09-22 15:09 ` PATCH (as112) " Alan Stern
2003-09-22 16:04 ` David Brownell
2003-09-24 0:17 ` Greg KH
[not found] <Pine.LNX.4.44L0.0309221606230.677-100000@ida.rowland.org>
2003-10-10 3:19 ` 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=3F6E493B.7070901@pacbell.net \
--to=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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