> Xen is difficult to debug without a classic onboard serial port for
> console output. Has to be some bug in that function.
Could Xen print messages to a screen? If yes, then it is possible to
find this function and insert the bunch of printf("1/2/3/etc") //
sleep(1) ( sleep is necessary to ensur
For the patching, I modified the xen.spec(.in) file adding the patch to the
already existing set of patches (eg. as Patch628). This way the patch is
applied even after make clean, when the xen sources are gunzipped again.
I also compiled xen-4.12.0 with the patch, and there were no compilation
Mike Banon:
Excellent discovery, awokd and qubes123!
qubes123 gets 100% of the credit, I merely confirmed it.
Please try to somehow upstream your solution to Xen.
Idea: find a way to detect a CPU type before executing this
"recheck_cpu_features(0)"
function, and if it is AMD CPU - maybe just
Excellent discovery, awokd and qubes123!
Please try to somehow upstream your solution to Xen.
Idea: find a way to detect a CPU type before executing this
"recheck_cpu_features(0)"
function, and if it is AMD CPU - maybe just skip this check :
> -if ( !recheck_cpu_features(0) )
> +/*if ( cpu
awokd wrote on 4/10/19 8:50 PM:
Got my build environment going, but I think I am missing a step. I edit
/home/user/qubes-builder/chroot-dom0-fc25/home/user/rpmbuild/BUILD/xen-4.8.5/xen/arch/x86/acpi/power.c
with the above patch. Then I run "make vmm-xen". Then I see it has
overwritten my chang
awokd wrote on 4/8/19 6:43 PM:
qubes123 wrote on 4/8/19 6:08 PM:
...distribution kernels (fedora, debian) with xen 4.11.1 still have
issues with suspend & g505s...
Understood, thank you! That will save a lot of testing time. I'm still
getting my build environment stood up, but will update onc
qubes123 wrote on 4/8/19 6:08 PM:
...distribution kernels (fedora, debian) with xen 4.11.1 still have issues with
suspend & g505s...
Understood, thank you! That will save a lot of testing time. I'm still
getting my build environment stood up, but will update once I can
confirm the workaround.
...distribution kernels (fedora, debian) with xen 4.11.1 still have issues with
suspend & g505s...
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+un
I'm not aware of that. I think for CB'd fam15h we need a xen patch, that will
not check the CPU features after resume, as microcode update never happens...
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
2019. április 6., szombat 12:34:31 UTC időpontban awokd a következőt írta:
> dm1.libe...@gmail.com wrote on 4/6/19 7:14 AM:
>
> > This issue is due to a xen patch ("Fix resume, when using microcode
> > upgrade"), that has been included when releases changed from xen-4.8.3-4 to
> > xen-4.8.3-5. T
dm1.libe...@gmail.com wrote on 4/6/19 7:14 AM:
This issue is due to a xen patch ("Fix resume, when using microcode upgrade"),
that has been included when releases changed from xen-4.8.3-4 to xen-4.8.3-5. This patch
checks the availability of previous CPU features (..Spectre) during resume, and
11 matches
Mail list logo
