-
-
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
Resume from suspending is broken after update to Xen 4.14 #6066
Resume from suspending is broken after update to Xen 4.14 #6066
Comments
Was suspend ever working on this model in Qubes? I thought I remember hearing a long time ago that it wasn't working. P.S. -- Please use the issue template. This is borderline unsuitable for qubes-issues. |
Yes, It works with Xen 4.13 till upgrading to 4.14. P.S. -- ok |
The same happens in openQA: #6049 |
Bisected to xen-project/xen@633ecc4a7cb |
In my case patch gives me reboot while resume action... |
I do have a system where the resume is still broken, but looks like a proper panic instead of instant reboot now (5s timeout before reboot, instead of instant). Sadly I don't have serial console there, so I don't know what really happened. |
Looks like I have similar timeout and have no serial port at laptop too |
Discussion on xen-devel: https://lists.xenproject.org/archives/html/xen-devel/2020-09/msg02074.html |
Seeing the same on System76 Galago Pro 4. Suspend worked on Xen 4.13. On 4.14 fans and screen wake up, the Fn-1 fan control works, but the laptop doesn't respond to anything else, and there is nothing on the logs after suspending. |
@jevank I tried it just now, but there's no change, also with all the VMs stopped. I should also mention that on this laptop reboot doesn't work, so it's possible that Xen was trying to reboot and froze the computer. |
I've run yet another bisection and here are the findings: https://lists.xenproject.org/archives/html/xen-devel/2020-10/msg00002.html |
Few bisection runs later... I've updated issue description with the summary. |
@pwmarcz I've force-pushed QubesOS/qubes-vmm-xen#88 with fixes collected so far. Can you test it? |
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
|
The service is called to allow VM to prepare for suspend, but it's just a notification - if the call fails, suspend anyway. This especially is important for HVM with PCI devices - if the service fails, userspace might be not prepared for the suspend, but later suspend by the kernel in many cases is enough for the VM to recover. If VM isn't suspended (but paused by Xen instead), it almost never survive resume. While at it, improve logging of both service failure and actual suspend failure. QubesOS/qubes-issues#6066
The service is called to allow VM to prepare for suspend, but it's just a notification - if the call fails, suspend anyway. This especially is important for HVM with PCI devices - if the service fails, userspace might be not prepared for the suspend, but later suspend by the kernel in many cases is enough for the VM to recover. If VM isn't suspended (but paused by Xen instead), it almost never survive resume. While at it, improve logging of both service failure and actual suspend failure. QubesOS/qubes-issues#6066
The service is called to allow VM to prepare for suspend, but it's just a notification - if the call fails, suspend anyway. This especially is important for HVM with PCI devices - if the service fails, userspace might be not prepared for the suspend, but later suspend by the kernel in many cases is enough for the VM to recover. If VM isn't suspended (but paused by Xen instead), it almost never survive resume. While at it, improve logging of both service failure and actual suspend failure. QubesOS/qubes-issues#6066
Automated announcement from builder-github The component
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Qubes R4.1
I`ve tested with X1 Thinkpad gen6. Hyperthreading is disabled in UEFI, kernel 5.4.51 and 5.4.61. With Xen 4.13 all works fine.
Tried with and without VMs running. Looks like suspend successful (thinkpad's led smooth blinked), but it doesn't resume.
Is problem specific to me?
There are multiple bugs causing this, summary below.
S3 related bugs in Xen 4.14 summary:
Assertion 'c2rqd(sched_unit_master(unit)) == svc->rqd' failed at credit2.c:2273
- no solution yet, a change in Xen 4.14 makes it more likely to happenThe text was updated successfully, but these errors were encountered: