and we have errata:
https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/016_fpuinit.patch.sig
I confirm AMI now works as expected
Thank you for great work!
_
Zbyszek Żółkiewski
> Wiadomość napisana przez Zbyszek Żółkiewski w dniu
> 06.08.2018, o godz. 11:54:
>
>> On Thu, 2 Aug 2018,Mike E
On Wed, 1 Aug 2018, Philip Guenther wrote:
>> This smells like some compatibility issue with the eager-FPU change. One
>> thought is whether the Xen presents the guest with a correctly reset FPU
>> state on all CPUs, or if there's some odd state that we're not clearing.
>>
>> I made a later commit
On Wed, 1 Aug 2018, Philip Guenther wrote:
> This smells like some compatibility issue with the eager-FPU change. One
> thought is whether the Xen presents the guest with a correctly reset FPU
> state on all CPUs, or if there's some odd state that we're not clearing.
>
> I made a later commit in t
i have just created AMI from 6.3-current (snapshot from 1 Aug) - and it boots
correctly.
For eager-FPU - i have rolled-back syspatch(8) using -r up to first patch - and
it was broken before eager-FPU which was introduced in errata 010 - so i am not
sure this is it.
I will try to investigate tha
On Wed, 1 Aug 2018, Zbyszek Żółkiewski wrote:
> OpenBSD 6.3 GENERIC.MP running on XEN (AWS m4.large) - dmesg at the end
> of this mail. Image build from https://github.com/kolargol/openbsd-aws
> which is fork from https://github.com/ajacoutot/aws-openbsd - my fork
> have some minor modifications
Hi guys,
OpenBSD 6.3 GENERIC.MP running on XEN (AWS m4.large) - dmesg at the end of this
mail. Image build from https://github.com/kolargol/openbsd-aws which is fork
from https://github.com/ajacoutot/aws-openbsd - my fork have some minor
modifications.
Recently i run into problems after using
