sys-usb dies on suspend/un-suspend

[lunarthegrey]

Qubes OS version:

Qubes OS 4.0

Affected component(s):

sys-usb VM

---

Steps to reproduce the behavior:

Close laptop to put into suspend, re-open later, un-suspend and sys-usb no longer works.

Expected behavior:

Suspend doesn't crash sys-usb and works fine like other VMs.

Actual behavior:

sys-usb stops working and you must kill it with qvm-kill sys-usb, qvm-shutdown does not work.

General notes:

My Qubes is fully patched with all of the latest stable updates (besides security testing). I am running kernel 4.14.41-1 and using the Fedora 28 template, although this also happened with the Fedora 26 template. I am unsure what logs I should be looking at to determine the cause. When the issue happens I have to force kill the VM and start it back up. I cannot get anything to run in sys-usb after a suspend/un-suspend.

---

Related issues:

Unknown.

[lunarthegrey]

It seems like if I suspend/un-suspend for a few minutes sys-usb works fine. But I just suspended for more than 8 hours, opened up my laptop and found that sys-usb is dead. I can confirm that when I suspend for a few minutes that logs are written but when I suspend for longer periods of time nothing is written to the log file /var/log/xen/console/guest-sys-usb.log

Not sure how I can go about debugging this one.

[lunarthegrey]

It seems like if I suspend/un-suspend for a few minutes sys-usb works fine. But I just suspended for more than 8 hours, opened up my laptop and found that sys-usb is dead. I can confirm that when I suspend for a few minutes that logs are written but when I suspend for longer periods of time nothing is written to the log file /var/log/xen/console/guest-sys-usb.log

Not sure how I can go about debugging this one.

[Kixunil]

I think I've just hit this issue too. Suspended my laptop during night and then failed to attach USB device to appvm.

Update: I attempted to relaunch it and it failed telling me to see the log file.

[Kixunil]

I think I've just hit this issue too. Suspended my laptop during night and then failed to attach USB device to appvm.

Update: I attempted to relaunch it and it failed telling me to see the log file.

[mig5]

This has affected me ever since upgrading from 3.2 to 4.

Because I use Yubikey auth for dom0 via the sys-usb, I have to shutdown my sys-usb before I suspend, and then let my Yubikey auth script auto-power up the machine to run its script. Otherwise, the script doesn't fire after resume and I can't login \o/

Like @lunarthegrey I found that if I quickly suspend then resume (like, a 30 second suspend), it sometimes works, but for longer periods of suspend (5 minutes or longer - even if plugged into AC power) sys-usb won't come back.

Some months back I recall seeing a lot of kernel module noise in the sys-usb log when it occurs, but didn't note it. Just tried to reproduce, but now my entire sys-usb AppVM seems to crash (the open gnome-terminal I had open isn't clickable, can't xl console to the VM from dom0, etc). The VM is still considered 'Running' from qvm-ls output, but do anything but qvm-kill it.

[mig5]

This has affected me ever since upgrading from 3.2 to 4.

Because I use Yubikey auth for dom0 via the sys-usb, I have to shutdown my sys-usb before I suspend, and then let my Yubikey auth script auto-power up the machine to run its script. Otherwise, the script doesn't fire after resume and I can't login \o/

Like @lunarthegrey I found that if I quickly suspend then resume (like, a 30 second suspend), it sometimes works, but for longer periods of suspend (5 minutes or longer - even if plugged into AC power) sys-usb won't come back.

Some months back I recall seeing a lot of kernel module noise in the sys-usb log when it occurs, but didn't note it. Just tried to reproduce, but now my entire sys-usb AppVM seems to crash (the open gnome-terminal I had open isn't clickable, can't xl console to the VM from dom0, etc). The VM is still considered 'Running' from qvm-ls output, but do anything but qvm-kill it.