Rich Ercolani

Oh right, I thought I vaguely remembered one. And it's for Zen 2, isn't that fun. #14557 So maybe a newer microcode would be a good time for you. (You...

Did you try the `noxsaves` kernel parameter? That'd be my suggestion as most likely to help.

I'd let the first one finish and then run a second one, to be sure - since the problem there is "it screwed up a calculation sometimes", if it is...

It'll reset on reboot, but if changing that helped you, you have SIMD issues. I'd still suspect an interaction with that Zen 2 erratum, absent more data, since there's not...

Here, this patch will log something like: ``` [ 232.980881] SIMD debug: sse: 1 sse2: 1 sse3: 1 ssse3: 1 sse41: 1 sse42: 1 avx: 1 avx2: 1 bmi1: 1...

Cute, so it was already set to 0, I would guess because the kernel detected the same sort of concern that I mentioned. That makes this all the more fascinating,...

If I were guessing here, also, Intel had a bug relatively recently where SIMD state didn't get saved/restored properly across VMENTER/VMEXIT. So stopping all VMs on the system then running...

"Rounding error" almost certainly means the CPU, yes, and unless you changed the power from stock before, I would be surprised if tweaking the voltages reliably improved your outcomes. For...

The only thing I can think of that might match your description (since ZFS has, to my knowledge, never used the kernel's crypto primitives, and those posts don't appear to...

I've not tried it in the way you mean (whenever I've played with cross-compilation here, it's been with qemu-static and chroot), but I don't know of any secret sauce that...