From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: zachm1996@gmail.com, Claudia <claudia1@disroot.org>
Subject: [Xen-devel] Xen fails to resume on AMD Fam15h (and Fam17h?) because of CPUID mismatch
Date: Mon, 10 Feb 2020 00:06:55 +0100 [thread overview]
Message-ID: <20200209230655.GA32524@mail-itl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]
Hi,
Multiple Qubes users have reported issues with resuming from S3 on AMD
systems (Ryzen 2500U, Ryzen Pro 3700U, maybe more). The error message
is:
(XEN) CPU0: cap[ 1] is 7ed8320b (expected f6d8320b)
If I read it right, this is:
- OSXSAVE: 0 -> 1
- HYPERVISOR: 1 -> 0
Commenting out the panic on a failed recheck_cpu_features() in power.c
makes the system work after resume, reportedly stable. But that doesn't
sounds like a good idea generally.
Is this difference a Xen fault (some missing MSR / other register
restore on resume)? Or BIOS vendor / AMD, that could be worked around in
Xen?
--
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?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2020-02-09 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 23:06 Marek Marczykowski-Górecki [this message]
2020-02-10 8:55 ` [Xen-devel] Xen fails to resume on AMD Fam15h (and Fam17h?) because of CPUID mismatch Jan Beulich
2020-02-10 11:17 ` Andrew Cooper
2020-02-10 12:14 ` Marek Marczykowski-Górecki
2020-02-10 12:46 ` Andrew Cooper
2020-02-11 12:59 ` Claudia
2020-02-11 21:08 ` Marek Marczykowski-Górecki
2020-02-12 4:20 ` Claudia
2020-05-02 21:12 ` Z M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200209230655.GA32524@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=claudia1@disroot.org \
--cc=xen-devel@lists.xenproject.org \
--cc=zachm1996@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).