From: Paul Hedderly <paul@mjr.org>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Kernel lockup with (debian) 4.16.0-2-rt-amd64
Date: Tue, 12 Jun 2018 21:00:31 +0100 [thread overview]
Message-ID: <46bd903565f6b1114b1d9f6bafa7db77bf3b5090.camel@mjr.org> (raw)
Loving wireguard but I'm getting failures running the Debian realtime
kernel. I first noticed that the wg link was freezing for 20-30 seconds
at a time, and then the machine would freeze.
For example now, before the innevitable freeze:
http://dpaste.com/1WFGS46
from 3820.516865 seconds in
[ 3820.516865] BUG: scheduling while atomic:
kworker/1:2/17295/0x00000002
[ 3820.516865] Modules linked ...
[ 3820.516926] Preemption disabled at:
[ 3820.516932] [<ffffffffbda3366f>] kernel_fpu_begin+0xf/0x20
[ 3820.516934] CPU: 1 PID: 17295 Comm: kworker/1:2 Tainted:
G U O 4.16.0-2-rt-amd64 #1 Debian 4.16.12-1
[ 3820.516935] Hardware name: Dell Inc. PowerEdge T20/0VD5HY, BIOS A06
01/27/2015
[ 3820.516940] Workqueue: wg-crypt-wg0 packet_encrypt_worker
[wireguard]
[ 3820.516940] Call Trace:
[ 3820.516946] dump_stack+0x5c/0x85
[ 3820.516948] ? kernel_fpu_begin+0xf/0x20
[ 3820.516950] __schedule_bug+0x73/0xc0
[ 3820.516953] __schedule+0x5a1/0x6e0
<etc - see paste>
Is there any more info needed? I think I'm going to drop the rt kernel
for now because I've had 4 lockups in 24hrs (since moving to the rt
kernel)
Is this a known problem? I'm guessing that wg hasnt been tested much
with the rt patchset.
With a previous freeze it was preceeded by thousands of :
Jun 12 18:11:40 brix /usr/lib/gdm3/gdm-x-session[9135]: ERROR
block_reap:328: [bandwidth] bad exit code 1
Jun 12 18:11:45 brix /usr/lib/gdm3/gdm-x-session[9135]: ERROR
block_reap:328: [bandwidth] bad exit code 1
Jun 12 18:11:50 brix /usr/lib/gdm3/gdm-x-session[9135]: ERROR
block_reap:328: [bandwidth] bad exit code 1
Jun 12 18:11:55 brix /usr/lib/gdm3/gdm-x-session[9135]: ERROR
block_reap:328: [bandwidth] bad exit code 1
Jun 12 18:12:00 brix /usr/lib/gdm3/gdm-x-session[9135]: ERROR
block_reap:328: [bandwidth] bad exit code 1
Jun 12 18:12:05 brix /usr/lib/gdm3/gdm-x-session[9135]: ERROR
block_reap:328: [bandwidth] bad exit code 1
Jun 12 18:12:10 brix /usr/lib/gdm3/gdm-x-session[9135]: ERROR
block_reap:328: [bandwidth] bad exit code 1
Jun 12 18:12:15 brix /usr/lib/gdm3/gdm-x-session[9135]: ERROR
block_reap:328: [bandwidth] bad exit code 1
then:
Jun 12 18:16:01 brix kernel: [16507.893206] CPU: 2 PID: 18331 Comm:
kworker/2:2 Tainted: G U O 4.16.0-2-rt-amd64 #1 Debian
4.16.12-1
Jun 12 18:16:01 brix kernel: [16507.893206] Hardware name: Dell Inc.
PowerEdge T20/0VD5HY, BIOS A06 01/27/2015
Jun 12 18:16:01 brix kernel: [16507.893211] Workqueue: wg-crypt-wg0
packet_encrypt_worker [wireguard]
Jun 12 18:16:01 brix kernel: [16507.893212] Call Trace:
Jun 12 18:16:01 brix kernel: [16507.893218] dump_stack+0x5c/0x85
Jun 12 18:16:01 brix kernel: [16507.893220] ?
kernel_fpu_begin+0xf/0x20
Jun 12 18:16:01 brix kernel: [16507.893222] __schedule_bug+0x73/0xc0
Jun 12 18:16:01 brix kernel: [16507.893224] __schedule+0x5a1/0x6e0
And this was all interspersed with the network going up and down. A log
of the previous failure:
https://pastebin.com/eFPHXaYk
Many thanks.
next reply other threads:[~2018-06-12 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 20:00 Paul Hedderly [this message]
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
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=46bd903565f6b1114b1d9f6bafa7db77bf3b5090.camel@mjr.org \
--to=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).