From: Ondrej Zary <linux@rainbow-software.org>
To: linux-pm@lists.linux-foundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: ehci_hcd causes immediate wakeup from suspend to RAM or disk on Asus P4P800-VM
Date: Tue, 27 Apr 2010 15:23:46 +0200 [thread overview]
Message-ID: <201004271523.48647.linux@rainbow-software.org> (raw)
Hello,
machine with Asus P4P800-VM mainboard wakes up immediately after:
echo mem >/sys/power/state
or even
echo disk >/sys/power/state (only when /sys/power/disk is set to "platform",
which is the default)
The problem disappears when unloading ehci_hcd module. There are no USB
devices attached. The problem seems to be something like this:
http://www.mail-archive.com/linux-usb-devel%40lists.sourceforge.net/msg54499.html
/sys/devices/pci0000:00/0000:00:1d.7/power/wakeup is disabled by default
/sys/devices/pci0000:00/0000:00:1d.7/usb1/power/wakeup is enabled by default,
changing it to disabled fixes the problem
The board has 4 USBPWxx jumpers (USBPW12, USBPW34, USBPW56 and USBPW78) that
selects 5V or 5VSB as power to the corresponding USB connectors. When they're
all set to 5VSB, the immediate wakeup does not appear. When any of them is
set to 5V, it wakes up immediately after entering suspend. I guess that the
loss of power to any of the ports (5V power is turned off in suspend) is
detected as some event (overcurrent or device connect?)
"ignore_oc=1" parameter to ehci_hcd modules does not change anything.
--
Ondrej Zary
next reply other threads:[~2010-04-27 13:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 13:23 Ondrej Zary [this message]
2010-04-27 14:22 ` [PATCH] ehci: Disable wake on overcurrent (WKOC_E) Ondrej Zary
2010-04-27 16:25 ` [PATCH v2] [RFC] ehci: Disable wake on overcurrent (WKOC_E) and disconnect (WKDISC_E) Ondrej Zary
2010-04-27 19:21 ` Alan Stern
2010-04-27 20:46 ` Ondrej Zary
2010-04-27 21:33 ` Greg KH
2010-04-28 15:41 ` Alan Stern
2010-04-28 17:30 ` Ondrej Zary
2010-04-29 16:16 ` Alan Stern
2010-04-29 17:45 ` [linux-pm] " Alan Stern
2010-04-29 21:14 ` Ondrej Zary
2010-05-04 5:37 ` Du, Alek
2010-05-05 3:12 ` Du, Alek
2010-05-05 15:55 ` Alan Stern
2010-05-06 0:11 ` Du, Alek
2010-05-06 8:23 ` Du, Alek
2010-05-06 14:46 ` Alan Stern
2010-05-06 15:20 ` Du, Alek
2010-05-06 16:06 ` Alan Stern
2010-05-07 1:32 ` Du, Alek
2010-05-07 15:20 ` Alan Stern
2010-05-08 2:00 ` Du, Alek
[not found] ` <6C44CD31806DCD4BB88546DAB7AFC9A201EB5A39FA@shsmsx502.ccr.corp.intel.com>
2010-05-10 2:25 ` Du, Alek
2010-05-10 21:05 ` Alan Stern
2010-05-11 3:31 ` Du, Alek
2010-05-11 14:01 ` Alan Stern
2010-05-11 15:58 ` Alan Stern
2010-05-11 16:10 ` Du, Alek
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=201004271523.48647.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb@vger.kernel.org \
/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