From: Alexandre Karlov <bassbeat@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel panic on ARM
Date: Tue, 30 May 2017 20:54:38 +0200 [thread overview]
Message-ID: <267E2F68-320A-4D1F-BDC7-7B5A240B75C8@gmail.com> (raw)
In-Reply-To: <CAHmME9rKAXC2AXKkLKK3k5Nw11n1nAF3gro1ynEGXnqMuaxEYg@mail.gmail.com>
Hey Jason,=20
I confirm, the hardware is now running for almost 4 hours without any =
issues, so let=E2=80=99s be optimistic and say the patch solved it.=20
I will continue to run the patched version on one device and try the =
latest master branch on another one. I=E2=80=99ll report there is =
something weird.=20
Thanks for your quick help and keep up the great work!
Cheers,
Alexandre=20
> On 30 May 2017, at 18:04 , Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>=20
> Hi Alexandre,
>=20
> As 2 hours have gone by, I assume things are working somewhat =
decently. Great!
>=20
> If that patch is stable for you, you might be interested in trying out
> the latest `master` branch in the git repo:
>=20
> $ git clone https://git.zx2c4.com/WireGuard
> $ cd WireGuard/src
> $ make debug -j$(nproc) && make install
>=20
> I'll probably make a new snapshot in a few days, but if you'd like to
> try things out in advance, that'd be welcome. The master branch
> contains some NEON accelerations for the hardware you're using, so if
> all goes well, you should see an increase in performance.
>=20
> Regards,
> Jason
prev parent reply other threads:[~2017-05-30 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 8:59 Alexandre Karlov
2017-05-30 11:48 ` Jason A. Donenfeld
2017-05-30 11:57 ` Alexandre Karlov
2017-05-30 12:00 ` Jason A. Donenfeld
2017-05-30 12:45 ` Jason A. Donenfeld
2017-05-30 13:29 ` Alexandre Karlov
2017-05-30 16:04 ` Jason A. Donenfeld
2017-05-30 18:54 ` Alexandre Karlov [this message]
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=267E2F68-320A-4D1F-BDC7-7B5A240B75C8@gmail.com \
--to=bassbeat@gmail.com \
--cc=Jason@zx2c4.com \
--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).