-
-
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
Computer does not recover from suspend #3738
Comments
I downgraded all relevant xen packages to 4.8.3-3 and previous functionality has been restored. |
@HW42 xen-4.8.3-4 breaks suspend. |
Is 4.8.3-4 the Spectre mitigation update? @unman Lenovo recently released BIOS updates with Spectre mitigation support for Ivy Bridge Thinkpads like the x230. Have you updated? |
Hi, I also had suspend/resume broken and booting an older kernel (4.14.13-2) works fine. |
According to QSB 37, it's |
Hi, I can confirm I had the same issue with X1 5th gen carbon. I believe it was after microcode_ctl update, rather than xen update, but am not sure. Wakeup only worked when I shut down every VM, (even sys-usb and sys-net). Latest bios upgrade by lenovo fixed the issue. Seems to reliably work again. |
I was also experiencing this issue on my Dell XPS 15 but flashing the latest Bios update fixed it for me. |
I'm having the same problem with Asus Z10PE-D16 WS motherboard. |
@x4lldux Have you tried updating your system's Bios firmware by flashing the latest version from the manufacturer? This fixed the issue for me. |
@Simon-Davies should have mentioned ealier, already have the latest version and that doesn't change the above results. |
QubesOS/qubes-vmm-xen#35 should fix this in practice. But is strictly not complete: Jan Beulich:
Edit: Fixed link to PR. |
In what cases those could happen? |
TBH I don't know. AFAIU one case would be hardware faults (RAM or bus errors). Not sure if Xen is using any breakpoint tricks ore something similar for profiling and if this can be active during early resume. FWIW: I never observed any such problems during testing. Based on https://lists.xenproject.org/archives/html/xen-devel/2018-04/msg00836.html I assume that Jan or Andrew will come up with a follow-up patch to disable IBRS/IBPB during suspend. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
@marmarek I'm pretty confused
I checked it but I don't have this package installed in dom0. Is this normal? Has it relation with this bug? I'm running an old kernel due this bug and I would like to run the latest version. |
Yes. Notification script is confused about multiple packages from a single source and just pick the first one. What is important is a package version (xen*-4.8.3-5.fc26) |
The updates fixed my resume issues. :) |
This fixed also for me great :) |
Automated announcement from builder-github The package
|
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
Or update dom0 via Qubes Manager. |
Qubes OS version:
R4.0 rc5
Affected component(s):
Resume after suspend
Steps to reproduce the behavior:
Suspend by shutting lid
Expected behavior:
Resume after suspend should work
Actual behavior:
Computer does not recover.
Screen stays black and no response to keyboard ot trackpad use.
Fans do not spin up.
Sometimes computer will not restart.
General notes:
I do not think this is the same issue as #3705 since symptoms are slightly different.
This is an old x230, with RAM at only 8GB.
It worked flawlessly under rc5 until I applied updates from current-testing.
On previous packages from current, suspend/restore worked every time.
Since the update it fails every time.
I see nothing relevant in the logs.
Obviously i suspect the update to xen-4.8.3-4.
I'll revert the update and downgrade back to 8.3-3 to see what effect that has.
Related issues:
#3705 - but I think this is not the same.
The text was updated successfully, but these errors were encountered: