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: Wed, 13 Jun 2018 08:58:24 +0100 [thread overview]
Message-ID: <ae8cd01fb2f30682efbae8b2f8b9cd98aaaa9353.camel@mjr.org> (raw)
In-Reply-To: <CAHmME9qW8udKYrcdwgFK6qcabAJ8vDqijek0UcRmFTGTcUdznw@mail.gmail.com>
On Wed, 2018-06-13 at 03:58 +0200, Jason A. Donenfeld wrote:
> Hi Paul,
>
> The current patch I'm now considering is here:
> https://git.zx2c4.com/WireGuard/patch/?id=17fb4ff6064e10bb91bf2ccf653
> 4bfdf767a9b90
Ahh!
Last night I recompiled with your first patch and left the machine
running - this morning it was frozen again :(
prh@brix:~$ sudo modinfo /lib/modules/4.16.0-2-rt-
amd64/updates/dkms/wireguard.ko
filename: /lib/modules/4.16.0-2-rt-
amd64/updates/dkms/wireguard.ko
alias: net-pf-16-proto-16-family-wireguard
alias: rtnl-link-wireguard
version: 0.0.20180531-1
author: Jason A. Donenfeld <Jason@zx2c4.com>
description: Fast, secure, and modern VPN tunnel
license: GPL v2
srcversion: 6BC9480277BB8058D75035C
depends: udp_tunnel,ip6_udp_tunnel
retpoline: Y
name: wireguard
vermagic: 4.16.0-2-rt-amd64 SMP preempt mod_unload modversions
But although the machine froze I dont see the BUG's in the kernel log.
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?
I need to run the non-rt today to get some work done and I'll run the
-rt- with the new patch this evening if thats ok.
The other "weird" errors are there, but I've just rebooted to the non-
rt kernel and I'm getting those "ERROR block_reap:328: [bandwidth] bad
exit code 1" a lot still... but searching specifically on those is
pointing to i3blocks... indeed killing i3blocks does stop them, so
something in my i3blocks config is screwy. Woops! I was confused
because the logs show them being trapped by gdm3.
Many thanks for your help and brilliant code.
next prev parent reply other threads:[~2018-06-13 7:54 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 [this message]
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=ae8cd01fb2f30682efbae8b2f8b9cd98aaaa9353.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).