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.

Sign up for GitHub

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

Jump to bottom

USBVM Blocks S3 sleep #1419

Closed
maxzinkus opened this issue Nov 13, 2015 · 32 comments
Closed

USBVM Blocks S3 sleep #1419

maxzinkus opened this issue Nov 13, 2015 · 32 comments
Labels
C: core C: kernel P: minor Priority: minor. The lowest priority, below "default." r3.0-fc20-stable r3.0-fc21-stable r3.0-fc22-stable r3.0-fc23-stable r3.0-jessie-stable r3.0-wheezy-stable r3.1-fc21-stable r3.1-fc22-stable r3.1-fc23-stable r3.1-jessie-stable r3.1-stretch-cur-test r3.1-wheezy-stable T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Milestone
Release 3.1

Comments

@maxzinkus
Copy link

When I have the USB controllers under dom0 (no USBVM) dropping to S3 sleep takes just under a second.

However, when a USBVM has been assigned PCI devices (The two USB2.0 controllers, in my case), dropping to S3 sleep takes upward of 15 seconds.

I'm not entirely sure the nature of the bug - it may have something to do with the fact that detaching block devices from VMs with qvm-block has reported LibVirt errors ("failed to detach").

I'm sorry this is unspecific, let me know what output (dom0 / usbvm dmesg?) will help in diagnostics.

Thanks!
@marmarek
Copy link
Member

Do you have block devices (qvm-block) attached when going to sleep? This
might be a problem.
Anyway check logs in dom0 and USB VM (journalctl) to see what takes that
much time.

Also some USB 3.0 controllers makes problems with S3 sleep. If you
happen to have some of them, simply add xhci_pci module to
/rw/config/suspend-module-blacklist

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@maxzinkus
Copy link
Author

No devices attached on sleep, I haven't tried sleeping with devices
attached although I assume that will go similarly or worse.

I was having pci reset issues with my usbvm so I disabled USB3 in the BIOS
a while ago.

I'll let you know what the logs look like, thanks as always.

Max
On Nov 13, 2015 12:58 PM, "Marek Marczykowski-Górecki" <
[email protected]> wrote:

Do you have block devices (qvm-block) attached when going to sleep? This
might be a problem.
Anyway check logs in dom0 and USB VM (journalctl) to see what takes that
much time.

Also some USB 3.0 controllers makes problems with S3 sleep. If you
happen to have some of them, simply add xhci_pci module to
/rw/config/suspend-module-blacklist

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

—
Reply to this email directly or view it on GitHub
#1419 (comment)
.

@maxzinkus
Copy link
Author

The only journalctl entries that seems to stand out:

Dom0

  • the suspension of the netvm (although this doesn't affect time when sys-usb has been deleted)
  • clock syncing (I don't have a clockVM set..?) although the time elapsed is a fraction of a second
  • libvirtd[867] EOF while reading data I/O error

sys-usb (usbvm)

  • nothing out of the ordinary

EDIT: Setting a clockVM had no effect

@marmarek
Copy link
Member

You can still try with blacklisting module - in case of USB 2.0, it would be ehci_pci. Write it to /rw/config/suspend-module-blacklist

@maxzinkus
Copy link
Author

I couldn't seem the glean a full answer from some cursory googling, what
does the blacklisting actually do?

Thanks!
On Nov 28, 2015 3:30 PM, "Marek Marczykowski-Górecki" <
[email protected]> wrote:

You can still try with blacklisting module - in case of USB 2.0, it would
be ehci_pci. Write it to /rw/config/suspend-module-blacklist

—
Reply to this email directly or view it on GitHub
#1419 (comment)
.

@marmarek
Copy link
Member

I couldn't seem the glean a full answer from some cursory googling, what does the blacklisting actually do?

It will unload the module before suspend and load it back after resume (if was loaded at suspend time). Described here: https://www.qubes-os.org/doc/config-files/

@marmarek marmarek added C: core C: kernel P: minor Priority: minor. The lowest priority, below "default." labels Dec 26, 2015
@marmarek marmarek added this to the Release 3.1 milestone Dec 26, 2015
@maxzinkus
Copy link
Author

Duly noted, thanks as always.

That said, it doesn't seem to have solved the issue. From lsusb.py I
noticed the device referred to as ehci_hcd, but trying that in the
blacklist didn't work either. Is there a way to list those IDs of hub
devices to tell what exactly to put in the blacklist?

Thanks!

I couldn't seem the glean a full answer from some cursory googling, what
does the blacklisting actually do?

It will unload the module before suspend and load it back after resume (if
was loaded at suspend time). Described here:
https://www.qubes-os.org/doc/config-files/

—
Reply to this email directly or view it on GitHub
#1419 (comment)
.

@marmarek
Copy link
Member

In latest kernels, ehci_hcd was split into ehci_hcd and ehci_pci - the later one is actually bound to the device (and depends on ehci_hcd), so this is the one to blacklist.

Anyway, I have similar issue on one laptop, will look into that closer.

@maxzinkus
Copy link
Author

Thanks. I'll try some configurations as well and let you know if anything
comes of it.
On Dec 28, 2015 4:17 AM, "Marek Marczykowski-Górecki" <
[email protected]> wrote:

In latest kernels, ehci_hcd was split into ehci_hcd and ehci_pci - the
later one is actually bound to the device (and depends on ehci_hcd), so
this is the one to blacklist.

Anyway, I have similar issue on one laptop, will look into that closer.

—
Reply to this email directly or view it on GitHub
#1419 (comment)
.

@marmarek marmarek mentioned this issue Dec 29, 2015
Closed
@marmarek marmarek added the T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. label Jan 10, 2016
@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.1.12-1.fc21 has been pushed to the r3.1 testing repository for the Fedora fc21 template.
To test this update, please install it with the following command:

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

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.1.12-1.fc22 has been pushed to the r3.1 testing repository for the Fedora fc22 template.
To test this update, please install it with the following command:

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

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.1.12-1.fc23 has been pushed to the r3.1 testing repository for the Fedora fc23 template.
To test this update, please install it with the following command:

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

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.1.12-1.fc21 has been pushed to the r3.1 stable repository for the Fedora fc21 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.1.12-1.fc22 has been pushed to the r3.1 stable repository for the Fedora fc22 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.1.12-1.fc23 has been pushed to the r3.1 stable repository for the Fedora fc23 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.0.24-1.fc20 has been pushed to the r3.0 testing repository for the Fedora fc20 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r3.0-current-testing

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.0.24-1.fc21 has been pushed to the r3.0 testing repository for the Fedora fc21 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r3.0-current-testing

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.0.24-1.fc22 has been pushed to the r3.0 testing repository for the Fedora fc22 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r3.0-current-testing

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.0.24-1.fc23 has been pushed to the r3.0 testing repository for the Fedora fc23 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r3.0-current-testing

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package qubes-core-agent_3.0.24-1+deb8u1 has been pushed to the r3.0 testing repository for the Debian jessie template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing jessie-testing, then use the standard update command:

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

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package qubes-core-agent_3.0.24-1+deb7u1 has been pushed to the r3.0 testing repository for the Debian wheezy template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing wheezy-testing, then use the standard update command:

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

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.0.25-1.fc20 has been pushed to the r3.0 stable repository for the Fedora fc20 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.0.25-1.fc21 has been pushed to the r3.0 stable repository for the Fedora fc21 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.0.25-1.fc22 has been pushed to the r3.0 stable repository for the Fedora fc22 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package python2-dnf-plugins-qubes-hooks-3.0.25-1.fc23 has been pushed to the r3.0 stable repository for the Fedora fc23 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@marmarek
Copy link
Member

Automated announcement from builder-github

The package qubes-core-agent_3.0.25-1+deb8u1 has been pushed to the r3.0 stable repository for the Debian jessie 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

@marmarek
Copy link
Member

Automated announcement from builder-github

The package qubes-core-agent_3.0.25-1+deb7u1 has been pushed to the r3.0 stable repository for the Debian wheezy 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: core C: kernel P: minor Priority: minor. The lowest priority, below "default." r3.0-fc20-stable r3.0-fc21-stable r3.0-fc22-stable r3.0-fc23-stable r3.0-jessie-stable r3.0-wheezy-stable r3.1-fc21-stable r3.1-fc22-stable r3.1-fc23-stable r3.1-jessie-stable r3.1-stretch-cur-test r3.1-wheezy-stable T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Milestone
Release 3.1
Development

No branches or pull requests
2 participants
@marmarek @maxzinkus