Skip to content
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

Closed
marmarek opened this issue Dec 25, 2018 · 8 comments · Fixed by QubesOS/qubes-app-linux-usb-proxy#28
Closed
Assignees
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: core P: minor Priority: minor. The lowest priority, below "default." r4.1-bookworm-stable r4.1-bullseye-stable r4.1-buster-stable r4.1-centos-stream8-stable r4.1-dom0-stable r4.1-fc35-stable r4.1-fc36-stable r4.1-fc37-cur-test T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@marmarek
Copy link
Member

Qubes OS version:

R4.0

Affected component(s):

usb-proxy


Steps to reproduce the behavior:

  1. Use qvm-usb to assign device from sys-usb to sys-net (like 3G modem).
  2. Try to suspend the system

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.

@marmarek marmarek added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. P: minor Priority: minor. The lowest priority, below "default." labels Dec 25, 2018
@marmarek marmarek added this to the Release 3.2 updates milestone Dec 25, 2018
@andrewdavidwong
Copy link
Member

A long timeout (~60sec) after which system seemingly suspend. But after resume, sys-usb is not working and in some cases sys-net neither.

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.

and in some cases sys-net neither.

Branched to #4658.

@marmarek marmarek changed the title USB device connected with qvm-usb breaks suspend USB device connected with qvm-usb cause problems on suspend Dec 25, 2018
@marmarek
Copy link
Member Author

If the machine actually does suspend, then this seems very similar to #4042.

Indeed it looks similar, but I think it's still different. This is specifically caused by qvm-usb, #4042 looks to be independent of qvm-usb.

@qubesos-bot
Copy link

Automated announcement from builder-github

The package app-linux-usb-proxy has been pushed to the r4.1 testing repository for the CentOS centos-stream8 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r4.1-current-testing

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The component app-linux-usb-proxy (including package qubes-usb-proxy-dom0-1.1.2-1.fc32) has been pushed to the r4.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-usb-proxy_1.1.2 has been pushed to the r4.1 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing buster-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The package app-linux-usb-proxy has been pushed to the r4.1 stable repository for the CentOS centos-stream8 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-usb-proxy_1.1.2+deb10u1 has been pushed to the r4.1 stable repository for the Debian template.
To install this update, please use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The component app-linux-usb-proxy (including package qubes-usb-proxy-dom0-1.1.2-1.fc32) has been pushed to the r4.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@andrewdavidwong andrewdavidwong added the affects-4.1 This issue affects Qubes OS 4.1. label Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: core P: minor Priority: minor. The lowest priority, below "default." r4.1-bookworm-stable r4.1-bullseye-stable r4.1-buster-stable r4.1-centos-stream8-stable r4.1-dom0-stable r4.1-fc35-stable r4.1-fc36-stable r4.1-fc37-cur-test T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants