public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm <linux-pm@lists.osdl.org>,
	USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: ehci_hcd causes box to resume immediately after suspend to RAM
Date: Sat, 9 Jun 2007 23:10:15 +0200	[thread overview]
Message-ID: <200706092310.16264.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0706031120560.23975-100000@netrider.rowland.org>

On Sunday, 3 June 2007 17:31, Alan Stern wrote:
> On Sun, 3 Jun 2007, Rafael J. Wysocki wrote:
> 
> > Hi,
> > 
> > One of my test boxes suspends to RAM just fine except that if ehci_hcd is
> > loaded before the suspend, the box resumes immediately after going to sleep.
> 
> Evidently the hardware thinks a wakeup event has occurred.  It is 
> possible to disable remote wakeup via sysfs, but it would be more 
> interesting to find out the real reason for the wakeup.
> 
> I don't know how to go about doing that, however.  It might be some 
> interaction at the ACPI level, and it might involve the PCI PME# 
> signal.
> 
> Do you have any USB devices attached when you suspend?
> 
> You can try using the patch below to see what happens when you manually
> suspend the controller.  It enables PCI devices to respond to the
> legacy power/state attribute.  You should look at what "lspci -vv" says
> about the controller's power management signals, both before and after
> suspending the PCI device entry.

It works as expected, AFAICS.  That is, after I echo '2' to the 'state' file,
it shows that the controller is in D3.

I've tried to suspend with the controller in that state, but it's resumed
immediately, as before.

> Maybe also see what ACPI reports.

How can I see that?

Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

  parent reply	other threads:[~2007-06-09 21:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 10:20 ehci_hcd causes box to resume immediately after suspend to RAM Rafael J. Wysocki
2007-06-03 15:31 ` Alan Stern
2007-06-03 22:35   ` Rafael J. Wysocki
2007-06-09 21:10   ` Rafael J. Wysocki [this message]
2007-06-09 21:26     ` [linux-usb-devel] " Alan Stern
2007-06-11 19:15       ` Rafael J. Wysocki
2007-06-11 20:10         ` Alan Stern
2007-06-13 22:01           ` Rafael J. Wysocki
2007-06-14 22:26             ` Alan Stern
2007-09-25  5:01               ` [linux-pm] " Benjamin Herrenschmidt
2007-09-25 14:39                 ` Alan Stern
2007-06-12  1:50         ` Zhang Rui
2007-06-12 11:59           ` Rafael J. Wysocki
2007-06-12 12: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=200706092310.16264.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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