From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: paul@mjr.org
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel lockup with (debian) 4.16.0-2-rt-amd64
Date: Wed, 13 Jun 2018 14:13:15 +0200 [thread overview]
Message-ID: <CAHmME9qU1OWW72PJ1q1=7pf+EYiPe8vdQX1V2f96Vi6WRmi9Ow@mail.gmail.com> (raw)
In-Reply-To: <ae8cd01fb2f30682efbae8b2f8b9cd98aaaa9353.camel@mjr.org>
Hi Paul,
> But although the machine froze I dont see the BUG's in the kernel log.
Alright, so this means I've determined the root cause of the BUGs you
were seeing before, and both the patch you applied and hopefully the
one I committed should take care of that. However, this lockup...
> Last night I recompiled with your first patch and left the machine
> running - this morning it was frozen again :(
> So honestly I'm wondering if that freezing is just a coincidence with
> the bug you found since I didnt see a BUG... However I could run the
> non-rt kernel for 13 days without freeze but cant run the -rt- kernel
> without freezing for more than a few hours. Do you think think the bug
> could cause that?
Does the freeze happen _without_ WireGuard? Or does it only happen
when using WireGuard?
Jason
next prev parent reply other threads:[~2018-06-13 12:09 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 [this message]
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
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='CAHmME9qU1OWW72PJ1q1=7pf+EYiPe8vdQX1V2f96Vi6WRmi9Ow@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).