From: Henry Snow <henry.snow@nielsen.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-dkms and CentOS 7.5
Date: Thu, 10 May 2018 21:41:47 +0000 [thread overview]
Message-ID: <CAFuSFDHaFoF1SkbbdqDA87SKzOuwfV1GWWnZapDkOWTa7yYObA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qhmPiDEE81h6rmA+iWdV4KpbqV7vCcw-6Nr+PZcQfnYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4206 bytes --]
Hmm...yeah, I've followed these steps:
Fresh CentOS 7.5 install
yum install git libmnl-devel elfutils-libelf-devel kernel-devel
@development-tools
git clone https://git.zx2c4.com/WireGuard
cd WireGuard/src
make
make install
deploy /etc/wireguard/wg0.conf
systemctl start wg-quick@wg0
kernel panic.
Any additional debugging steps I can provide? This trace looks a little
different, so also including it:
[ 1571.621740] ------------[ cut here ]------------
[ 1571.627195] WARNING: CPU: 1 PID: 264 at arch/x86/kernel/smp.c:127
native_smp_send_reschedule+0x65/0x70
[ 1571.637324] Modules linked in: wireguard(OE) ip6_udp_tunnel udp_tunnel
bonding skx_edac intel_powerclamp coretempd
[ 1571.715278] CPU: 1 PID: 264 Comm: kworker/1:2 Tainted: G D OE
------------ 3.10.0-862.2.3.el7.x86_64 #1
[ 1571.726478] Hardware name: Dell Inc. PowerEdge R640/0W23H8, BIOS 1.3.7
02/08/2018
[ 1571.734820] Workqueue: wg-crypt-wg0 packet_rx_worker [wireguard]
[ 1571.741700] Call Trace:
[ 1571.744990] <IRQ> [<ffffffffa7d0d78e>] dump_stack+0x19/0x1b
[ 1571.751604] [<ffffffffa76916d8>] __warn+0xd8/0x100
[ 1571.757319] [<ffffffffa769181d>] warn_slowpath_null+0x1d/0x20
[ 1571.763975] [<ffffffffa7654245>] native_smp_send_reschedule+0x65/0x70
[ 1571.771325] [<ffffffffa76dd791>] trigger_load_balance+0x191/0x280
[ 1571.778320] [<ffffffffa76d1f75>] ? sched_clock_cpu+0x85/0xc0
[ 1571.784883] [<ffffffffa76cd41a>] scheduler_tick+0x10a/0x150
[ 1571.791355] [<ffffffffa7701420>] ? tick_sched_do_timer+0x50/0x50
[ 1571.798254] [<ffffffffa76a4825>] update_process_times+0x65/0x80
[ 1571.805063] [<ffffffffa7701220>] tick_sched_handle+0x30/0x70
[ 1571.811608] [<ffffffffa7701459>] tick_sched_timer+0x39/0x80
[ 1571.818060] [<ffffffffa76beff6>] __hrtimer_run_queues+0xd6/0x260
[ 1571.824937] [<ffffffffa76bf58f>] hrtimer_interrupt+0xaf/0x1d0
[ 1571.831549] [<ffffffffa76577fb>] local_apic_timer_interrupt+0x3b/0x60
[ 1571.838863] [<ffffffffa7d24063>] smp_apic_timer_interrupt+0x43/0x60
[ 1571.846003] [<ffffffffa7d207b2>] apic_timer_interrupt+0x162/0x170
[ 1571.852973] <EOI> [<ffffffffa7d07b80>] ? panic+0x1d8/0x21f
[ 1571.859455] [<ffffffffa7d17763>] oops_end+0xd3/0xe0
[ 1571.865223] [<ffffffffa762e96b>] die+0x4b/0x70
[ 1571.870555] [<ffffffffa7d16eb0>] do_trap+0x60/0x170
[ 1571.876314] [<ffffffffa762b284>] do_invalid_op+0xb4/0x130
[ 1571.882591] [<ffffffffa77f6bbc>] ? kfree+0x13c/0x140
[ 1571.888435] [<ffffffffa76d3838>] ? __enqueue_entity+0x78/0x80
[ 1571.895059] [<ffffffffa76da2fc>] ? enqueue_entity+0x26c/0xb60
[ 1571.901676] [<ffffffffa795bb78>] ? prandom_u32+0x18/0x20
[ 1571.907858] [<ffffffffa7bd60c5>] ? skb_release_data+0xf5/0x140
[ 1571.914561] [<ffffffffa7d22aee>] invalid_op+0x1e/0x30
[ 1571.920479] [<ffffffffa7bd60c5>] ? skb_release_data+0xf5/0x140
[ 1571.927164] [<ffffffffa77f6bbc>] ? kfree+0x13c/0x140
[ 1571.932962] [<ffffffffa7bd60c5>] skb_release_data+0xf5/0x140
[ 1571.939446] [<ffffffffa7bd6134>] skb_release_all+0x24/0x30
[ 1571.945743] [<ffffffffa7bd659c>] consume_skb+0x2c/0x90
[ 1571.951700] [<ffffffffc08eff35>] packet_rx_worker+0x2d5/0x7f0
[wireguard]
[ 1571.959302] [<ffffffffa76b2dff>] process_one_work+0x17f/0x440
[ 1571.965847] [<ffffffffa76b3ac6>] worker_thread+0x126/0x3c0
[ 1571.972117] [<ffffffffa76b39a0>] ? manage_workers.isra.24+0x2a0/0x2a0
[ 1571.979327] [<ffffffffa76bae31>] kthread+0xd1/0xe0
[ 1571.984873] [<ffffffffa76bad60>] ? insert_kthread_work+0x40/0x40
[ 1571.991611] [<ffffffffa7d1f5dd>] ret_from_fork_nospec_begin+0x7/0x21
[ 1571.998687] [<ffffffffa76bad60>] ? insert_kthread_work+0x40/0x40
[ 1572.005389] ---[ end trace 5ef54fbe37d13ebd ]---
On Thu, May 10, 2018 at 4:25 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Hi Henry,
>
> Here's a transcript of things working fine with the latest master
> branch: https://א.cc/GEDdGn4N <https://xn--4db.cc/GEDdGn4N>
>
> I'm still playing to see if I can reproduce your crash.
>
> Jason
>
--
Henry Snow | Director, Site Reliability Engineering
eXelate, a Nielsen company <http://exelate.com/>
E: henry.snow@nielsen.com | M: 347.366.2700
675 6th Ave, 3rd Floor, New York, NY 10010
[-- Attachment #2: Type: text/html, Size: 6162 bytes --]
next prev parent reply other threads:[~2018-05-10 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 13:59 Henry Snow
2018-05-10 15:34 ` Jason A. Donenfeld
2018-05-10 16:14 ` Jason A. Donenfeld
2018-05-10 16:31 ` Henry Snow
2018-05-10 17:24 ` Henry Snow
2018-05-10 17:25 ` Jason A. Donenfeld
2018-05-10 17:35 ` Henry Snow
2018-05-10 17:36 ` Jason A. Donenfeld
2018-05-10 17:49 ` Jason A. Donenfeld
2018-05-10 18:26 ` Germano Massullo
2018-05-10 20:25 ` Jason A. Donenfeld
2018-05-10 21:41 ` Henry Snow [this message]
2018-05-10 21:47 ` Jason A. Donenfeld
2018-05-11 16:07 ` Joe Doss
2018-05-11 16:15 ` Henry Snow
2018-05-13 16:56 ` Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2018-05-10 13:50 Henry Snow
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=CAFuSFDHaFoF1SkbbdqDA87SKzOuwfV1GWWnZapDkOWTa7yYObA@mail.gmail.com \
--to=henry.snow@nielsen.com \
--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).