From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.linux-foundation.org
Cc: Zhang Rui <rui.zhang@intel.com>,
linux-pm <linux-pm@lists.osdl.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-pm] Re: ehci_hcd causes box to resume immediately after suspend to RAM
Date: Tue, 12 Jun 2007 14:16:15 +0200 [thread overview]
Message-ID: <200706121416.15800.rjw@sisk.pl> (raw)
In-Reply-To: <200706121359.28888.rjw@sisk.pl>
On Tuesday, 12 June 2007 13:59, Rafael J. Wysocki wrote:
> On Tuesday, 12 June 2007 03:50, Zhang Rui wrote:
> > > > > 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?
> > > >
> > > > I wish I knew. Maybe you can try asking on the ACPI mailing list.
> > > >
> > > > The simplest workaround should be to disable remote wakeup for that
> > > > controller:
> > > >
> > > > echo disable >/sys/bus/pci/devices/.../power/wakeup
> > >
> > > I tried that but it didn't help. Namely, the box resumed right after
> > > suspending as it had done before.
> > >
> > > The only way to prevent it from resuming immediately after the suspend is to
> > > 'rmmod ehci_hcd' before the suspend.
> > >
> > > Interestingly enough, I have no such problems with EHCI on the other test box
> > > that is able to suspend to RAM and resume.
> > >
> > What's the kernel version you are using?
> > Is it the same problem shown here?
> > http://lkml.org/lkml/2007/5/18/55
> > 2.6.22-rc1-mm1 may have this problem.
>
> Yes, I remeber this thread.
s/remeber/remember/
> The kernel is 2.6.22-rc4 with the patches from
> http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc4/patches/
> applied.
>
> Greetings,
> 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
prev parent reply other threads:[~2007-06-12 12:16 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
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 [this message]
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=200706121416.15800.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-pm@lists.osdl.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rui.zhang@intel.com \
/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