Am 28.12.2012 01:10, schrieb Alan Stern: > On Wed, 26 Dec 2012, Octavio Alvarez wrote: > >>>> It can't hurt to try the test. Does the patch below make any >>>> difference? >>> Thank you for the patch, but it makes no difference. :( > Too bad. > >> I looked for more instances of "linux immediate wakeup" and found >> interesting links. They are regarding EHCI, but I wonder if >> something similar could affect OHCI as well. >> >> >> First, two threads in linux-pm from 2010: >> >> http://lists.linux-foundation.org/pipermail/linux-pm/2010-April/025063.html >> [PATCH] ehci: Disable wake on overcurrent (WKOC_E) >> >> http://lists.linux-foundation.org/pipermail/linux-pm/2010-April/025064.html >> [PATCH v2] [RFC] ehci: Disable wake on overcurrent (WKOC_E) and disconnect >> (WKDISC_E) >> >> Do you think this may affect OHCI too in some similar way? > No, I don't think so. The mechanisms used by EHCI and OHCI for > controlling the wakeup setting (and in particular, wake on overcurrent) > are totally different. > >> --------------- >> >> Then, three links, apparently regarding EHCI about the usage of +5VSB >> instead of the +5V line for powering the USB controller. >> >> Could the experiment with switching the +5V and +5VSB lines be relevant as >> well for OCHI? > In fact, this message _is_ about OHCI. > >> http://www.gossamer-threads.com/lists/mythtv/users/316830 >> ASUS M2NPV-VM > It's certainly worth trying this out. > >>> I figured out that you have to enable the +5VSB jumper on all the >>> USB hubs that have devices connected to them, even if you're not going >>> to use them to wake up the box! In other words, turn them ALL on, not >>> just the one where the wake-up device is connected. Don't worry about >>> joysticks waking up your machine randomly, because they won't; >>> apparently only devices with power buttons can do so. >> --------------- >> >> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/128315 >> >>> Suspend started working after changing the USB from +5V to +5VSB. I do >>> get a message about half the times that 1 application refused to freeze: >>> Plasma. After the suspend attempt, I have to kill plasma and restart it. >>> If I try suspending again it works most of the time. But this seems like >>> an unrelated bug. >> --------------- >> >> http://www.gossamer-threads.com/lists/mythtv/users/309798 >> >>> Additionally, you need to have the motherboard jumper for USB host >>> controller set so that it gets power during S3. > If hardware jumpers on the motherboard are in the wrong position, it > definitely could cause the sort of problem you've been experiencing. > > Alan Stern > Ok, I tried switching the ports to +5VSB. That makes S3 work (no immediate wakeups). The problem is, that with this setting, the USB ports are powered ALWAYS (even when the computer is switched off completely). Great, especially when you have a USB device connected with lots of LEDs (or just an ordinary optical mouse)... :( Is there way to determine if the port is powered permanently ? I assume not, so there seems to be no sane way to fix/work around this. Seems like users have to disable wakeups for OHCI manually... Regards, Frank -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
