[Xen-devel] Xen fails to resume on AMD Fam15h (and Fam17h?) because of CPUID mismatch

[Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>]

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: signature.asc
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel