-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB device connected with qvm-usb cause problems on suspend #4657
USB device connected with qvm-usb cause problems on suspend #4657
Comments
I'm confused. The issue title and most of the description imply that the machine is prevented from suspending, but the phrase "after resume" implies that it actually did suspend, otherwise there would be nothing to "resume" from. If the machine actually does suspend, then this seems very similar to #4042.
Branched to #4658. |
Host controller drivers are detached on suspend, so all devices will be detached anyway. Do it before any domain is actually suspended to avoid deadlock. Fixes QubesOS/qubes-issues#4657
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
Or update dom0 via Qubes Manager. |
Qubes OS version:
R4.0
Affected component(s):
usb-proxy
Steps to reproduce the behavior:
Expected behavior:
System suspend successfully.
Actual behavior:
A long timeout (~60sec) after which system seemingly suspend. But after resume, sys-usb is not working and in some cases sys-net neither.
General notes:
I think it depends on suspend order - if one end of qvm-usb connection is suspended before the other, that other fails to suspend.
One solution would be to detach all such devices before suspend. It may be enough to force those USB devices suspend in appropriate order.
The text was updated successfully, but these errors were encountered: