also suffer from this issue,
we found out that none of those systems will go to S3 sleep state but
instantly wake up again (which pretty much looks like a similar problem).
Questions:
--
- What could be the root cause for this?
- How can we find out, what further commits have made the
d and mouse and I shutdown the system (even
from the menu) its shuts down and keeps off. So now it seems to behave
like the "good" kernel.
So at least we would have a workaround, but I would really prefer that I
can blacklist those modules because then our partner could build his own
kernel fo
system in the usual way and a "workaround"
>> could be disabling the ehci stuff from loading.
>
> Another possibility is to unbind ehci-pci just before shutting down,
> for example as part of a shutdown script.
>
>> Makes me really wonder if something is wrong with
ommunicate to our partner that is building the thin client
Linux distribution for those machines. So even if we didn't find the
root cause for this problem we have an easy workaround now that solves
the issue for the customers that are affected by this.
> Let me know what you find out.
