From: Paul Hedderly <paul@mjr.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel lockup with (debian) 4.16.0-2-rt-amd64
Date: Tue, 12 Jun 2018 22:42:47 +0100 [thread overview]
Message-ID: <32c8cc0d0059f0ae680c7c892919c309f621e9fd.camel@mjr.org> (raw)
In-Reply-To: <CAHmME9rtHVwfSdy4DDFYmgw06zVerbN8oP88ZZ5ahoJB3PPTFw@mail.gmail.com>
On Tue, 2018-06-12 at 23:35 +0200, Jason A. Donenfeld wrote:
> Hi Paul,
>
> Thanks for the useful bug report. I'll have a fix for it soon.
What a star :)
It's times like this I love being a invovled in OS and a linux
sysadmin. Forced to use a windows VD and o365 for work... and can't
imagine getting the frequent bugs I hit in both fixed so easily. Or
ever. Hit a windows explorer bug that's been a pain since at least
windows xp today!
> Thanks, also, for bringing Debian's rt kernel to my attention. Seems
> like this might be a good testing platform.
There are times the -rt- kernels are a bit behind, they are not always
built with every experimental/unstable/testing kernel, but for audio
work it is very nice to have them.
next prev parent reply other threads:[~2018-06-12 21:39 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 [this message]
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
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=32c8cc0d0059f0ae680c7c892919c309f621e9fd.camel@mjr.org \
--to=paul@mjr.org \
--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).