Hi!
> > In any case this isn't under our control.
> > Devices are resumed in the same order they were detected initially. I
> > think the only way to solve this problem is to find a workaround for EHCI
> > controllers that act weird when they resume.
>
> The problem could well be in UHCI instead, or BIOS.
> There are at least several dozen different configurations
> to test here, after all ... ;)
>
> Oliver, you're using some kind of BIOS suspend right?
> That is, /sys/power/disk says "platform" not "shutdown".
> Does swsusp behave correctly in the "shutdown" case?
> That's roughly the difference between an ACPI S4bios
> and an ACPI S4 suspend sequence. Both need testing.
"platform" is swsusp followed by S4 powerdown.
S4bios is "firmware".
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
