From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Paul Hedderly <paul@mjr.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel lockup with (debian) 4.16.0-2-rt-amd64
Date: Fri, 15 Jun 2018 19:04:52 +0200 [thread overview]
Message-ID: <CAHmME9pkqA7_4zaC_u14O0FX1_9pV25MhnB-SBgnWgsi+gr0uA@mail.gmail.com> (raw)
In-Reply-To: <9d824fde3e070d0d1264a09425a3c4b5cd455560.camel@mjr.org>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
Happy to hear it's working for you. I went asking for deeper answers, and
this thread might interest you:
https://marc.info/?l=linux-rt-users&m=152906766629953&w=2
https://marc.info/?l=linux-rt-users&m=152907896201090&w=2
On Thu, Jun 14, 2018, 21:50 Paul Hedderly <paul@mjr.org> wrote:
> On Wed, 2018-06-13 at 15:52 +0200, Jason A. Donenfeld wrote:
> > Hi Paul,
> >
> > I got an -rt kernel up and running, enabled a bunch of nice debugging
> > options, and found a handful of problems, all of which were fixed by:
> > https://git.zx2c4.com/WireGuard/commit/?id=0f05452d043d8d047cf5d7987f
> > c2732b97d676e6
>
> Well just some feedback - I ran overnight on the -rt- kernel with no
> wireguard... and it was clean and normal in the morning. Worked for a
> couple of hours with and then fired up wireguard compiled from the
> above commit - and its been running 10 hours now with no issues
> whatsoever. dmesg nice and empty!
>
> So many thanks - I think you nailed that one!
>
> > I realize the solution in that patch is a bit of a bummer, but at the
> > very least it keeps things from breaking now. I'll see if I can
> > improve it somewhere down the line.
>
> Its great to get a stable system again - brilliant work.
>
> I love wg - and having it on android (user-space only because its a new
> unrooted phone :( ) and Ubiquiti and LEDE... I'm sorted!
>
> The GSOC projects are also very exciting prospects...
>
[-- Attachment #2: Type: text/html, Size: 2296 bytes --]
next prev parent reply other threads:[~2018-06-15 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 20:00 Paul Hedderly
2018-06-12 21:35 ` Jason A. Donenfeld
2018-06-12 21:42 ` Paul Hedderly
2018-06-12 21:47 ` Jason A. Donenfeld
2018-06-13 1:58 ` Jason A. Donenfeld
2018-06-13 7:58 ` Paul Hedderly
2018-06-13 12:13 ` Jason A. Donenfeld
2018-06-13 13:52 ` Jason A. Donenfeld
2018-06-13 14:54 ` Paul Hedderly
2018-06-13 15:08 ` Greg KH
2018-06-13 16:07 ` Paul Hedderly
2018-06-13 21:12 ` Jason A. Donenfeld
2018-06-14 19:49 ` Paul Hedderly
2018-06-15 17:04 ` Jason A. Donenfeld [this message]
2018-06-13 14:49 ` Paul Hedderly
2018-06-12 21:38 ` Paul Hedderly
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=CAHmME9pkqA7_4zaC_u14O0FX1_9pV25MhnB-SBgnWgsi+gr0uA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=paul@mjr.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).