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 that area (sys/arch/amd64/amd64/cpu.c rev 1.124) > so it would be interesting to know if -current shows the same issue or if > the symptoms have improved (or changed at all) there.
I applied this diff to my system running on a t2.medium running GENERIC.MP and it fixed the problem I was having post 010_intelfpu errata. Would be great to see this as an Errata. -ME