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 > > On Thu, 2 Aug 2018,Mike Erdely wrote: >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.
can it be backported to -stable, so i can test ? No idea if that’s right for reliability errata patch, but looks like it’s now impossible to create working image on AWS _ Zbyszek Żółkiewski > Wiadomość napisana przez Zbyszek Żółkiewski <[email protected]> w dniu > 02.08.2018, o godz. 11:22: > > 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 that oddness bit more... > > _ > Zbyszek Żółkiewski > >> Wiadomość napisana przez Philip Guenther <[email protected]> w dniu >> 01.08.2018, o godz. 23:41: >> >> 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. >
