From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Egbert Verhage <egbert@eggiecode.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Seeking Ubuntu PPA Maintainer
Date: Wed, 16 Nov 2016 02:31:13 +0100 [thread overview]
Message-ID: <CAHmME9rUEA7ZXjZj5Th45X-tHEZfTQB134M+ym0sqyK3a4a4og@mail.gmail.com> (raw)
In-Reply-To: <82c49c47-1779-2c6c-8797-9f02f138fb6e@eggiecode.org>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
Hey Egbert,
On Wed, Nov 16, 2016 at 1:34 AM, Egbert Verhage <egbert@eggiecode.org> 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
[-- Attachment #2: avx2disabler.tar.xz --]
[-- Type: application/x-xz, Size: 700 bytes --]
next prev parent reply other threads:[~2016-11-16 1:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 20:44 Jason A. Donenfeld
2016-11-15 23:41 ` Egbert Verhage
[not found] ` <454ad249-3313-9423-c2d4-7602d56849fc@eggiecode.org>
2016-11-16 0:12 ` Jason A. Donenfeld
2016-11-16 0:34 ` Egbert Verhage
2016-11-16 1:31 ` Jason A. Donenfeld [this message]
2016-11-16 6:20 ` Dan Luedtke
2016-11-16 11:18 ` Egbert Verhage
2016-11-16 11:34 ` Dan Lüdtke
2016-11-16 14:04 ` Jason A. Donenfeld
2016-11-16 10:03 ` Egbert Verhage
2016-11-16 14:09 ` Jason A. Donenfeld
2016-11-16 14:22 ` Egbert Verhage
2016-11-16 14:25 ` Jason A. Donenfeld
2016-11-16 6:45 ` Daniel Kahn Gillmor
2016-11-16 11:10 ` Egbert Verhage
2016-11-16 14:24 ` Jason A. Donenfeld
2016-11-16 22:17 ` Daniel Kahn Gillmor
2016-11-16 22:52 ` Jason A. Donenfeld
2016-11-16 14:11 ` Jason A. Donenfeld
2016-11-16 14:37 Anonymous Anonymous
2016-11-16 15:00 ` Jason A. Donenfeld
2016-11-16 15:08 ` Egbert Verhage
2016-11-16 14:47 Anonymous Anonymous
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHmME9rUEA7ZXjZj5Th45X-tHEZfTQB134M+ym0sqyK3a4a4og@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=egbert@eggiecode.org \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).