Hey Jason, The kernel module worked for my. ([1020751.674357] AVX2 disabler loaded: 1 -> 0) Going to update the PPA to remove my disable of AVX2.
The problem is that the hosting company hides the cpuuid, but from the call with the sysadmin it is a XEON E5-2??? v3. Greetz, Egbert On 2016-11-16 02:31, Jason A. Donenfeld wrote: > Hey Egbert, > > On Wed, Nov 16, 2016 at 1:34 AM, Egbert Verhage <[email protected]> wrote: >> I mailed/called with one of the sys admins and discussed with him about the >> problem in the AVX2 extention. >> I think I'm going to mail/call the hosting company again. > It seems like the crux of the issue is that if they disable AVX2 > instructions, they need to make this known in the CPUID. Otherwise the > operating system will assume it's there when it isn't. > >> Can give you a vps if you want to. Just 3 euro the month. > See the attached tarball. Compile the kernel module in there and load > it BEFORE WireGuard. You might have to manually unload wireguard for > this to work: "rmmod wireguard && insmod ./avx2disabler.ko && modprobe > wireguard", for example. It should disable avx2 inside the kernel, > solving the issue. > > Jason _______________________________________________ WireGuard mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/wireguard
