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

sys-usb freeze after suspend #3142

Closed
marmarek opened this Issue Oct 2, 2017 · 8 comments

Comments

Projects
None yet
3 participants
@marmarek
Member

marmarek commented Oct 2, 2017

Qubes OS version (e.g., R3.2): R4.0


Steps to reproduce the behavior:

Start the system. Suspend it. Wait few seconds. Wake it up.

Expected behavior:

Working sys-usb after system suspend.

Actual behavior:

[   77.992077] Freezing user space processes ... (elapsed 0.001 seconds) done.
[   77.993575] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[   77.997918] PM: freeze of devices complete after 3.027 msecs
[   77.998408] PM: late freeze of devices complete after 0.464 msecs
[   78.017709] PM: noirq freeze of devices complete after 19.275 msecs
[   78.018020] xen:events: Xen HVM callback vector for event delivery is enabled
[   78.018020] xen:grant_table: Grant tables using version 1 layout
[   78.018020] Suspended for 249.976 seconds
[   78.021274] PM: noirq thaw of devices complete after 3.450 msecs
[   78.021452] PM: early thaw of devices complete after 0.126 msecs
[   78.021606] rtc_cmos 00:02: System wakeup disabled by ACPI
[   78.067039] xhci_hcd 0000:00:05.0: port 8 resume PLC timeout
[   78.067039] xhci_hcd 0000:00:05.0: port 6 resume PLC timeout
[   78.067039] xhci_hcd 0000:00:05.0: port 5 resume PLC timeout

And at this point sys-usb console is not responsive (nor any other application there).

This happens regardless of virt_mode property (pv or hvm).

Related issues:

Branched from #2849

cc @HW42

@marmarek marmarek added this to the Release 4.0 milestone Oct 2, 2017

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 6, 2017

Member

Unloading xhci-pci before suspend "fixes" this.

Member

marmarek commented Oct 6, 2017

Unloading xhci-pci before suspend "fixes" this.

@HW42

This comment has been minimized.

Show comment
Hide comment
@HW42

HW42 Oct 6, 2017

Unloading xhci-pci before suspend "fixes" this.

So it works if you reload it after suspend?

HW42 commented Oct 6, 2017

Unloading xhci-pci before suspend "fixes" this.

So it works if you reload it after suspend?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 6, 2017

Member

Yes.

Member

marmarek commented Oct 6, 2017

Yes.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 7, 2017

Member

Looks like the xhci-pci is already on the blacklist to automatically unload before suspend. But the scripts is called by non-root, so it fails. Thanks @jpouellet for debugging as part of #3151

Member

marmarek commented Oct 7, 2017

Looks like the xhci-pci is already on the blacklist to automatically unload before suspend. But the scripts is called by non-root, so it fails. Thanks @jpouellet for debugging as part of #3151

@HW42

This comment has been minimized.

Show comment
Hide comment
@HW42

HW42 Oct 7, 2017

Do you know if this previously (R3.2) also led to a hanging VM? I.e. is this purely a regression because of the broken blacklist script or are there two problems (blacklist not working and hanging VM after suspend)?

HW42 commented Oct 7, 2017

Do you know if this previously (R3.2) also led to a hanging VM? I.e. is this purely a regression because of the broken blacklist script or are there two problems (blacklist not working and hanging VM after suspend)?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 7, 2017

Member

On 3.2 xhci-pci is blacklisted too and there the unloading script works (is properly called as root). I don't remember details, but I'd guess it caused hang there too. Ok, just tested - after disabling module unload, sys-usb with USB3 controller is unusable after suspend. First it is frozen, but few seconds later it panics on __pci_write_msi_msg. If you want, I can post a full message.

Member

marmarek commented Oct 7, 2017

On 3.2 xhci-pci is blacklisted too and there the unloading script works (is properly called as root). I don't remember details, but I'd guess it caused hang there too. Ok, just tested - after disabling module unload, sys-usb with USB3 controller is unusable after suspend. First it is frozen, but few seconds later it panics on __pci_write_msi_msg. If you want, I can post a full message.

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Oct 7, 2017

Automated announcement from builder-github

The package qubes-core-dom0-4.0.8-1.fc25 has been pushed to the r4.0 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

Automated announcement from builder-github

The package qubes-core-dom0-4.0.8-1.fc25 has been pushed to the r4.0 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 qubesos-bot referenced this issue in QubesOS/updates-status Oct 7, 2017

Closed

core-admin v4.0.8 (r4.0) #250

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Oct 30, 2017

Automated announcement from builder-github

The package qubes-core-dom0-4.0.11-1.fc25 has been pushed to the r4.0 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

Automated announcement from builder-github

The package qubes-core-dom0-4.0.11-1.fc25 has been pushed to the r4.0 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment