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 17:35:08 +0000 [thread overview]
Message-ID: <CAFuSFDEREZibd5Vb-J1GreLK9ZV+y2wGOc5MuaHvHx4XdbwDkw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pRTWCEzhuFAbDBtWPAxk0hB7AobZWa8bDHC3EuPbN95A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3213 bytes --]
Was able to pull a little more this time. This help?
datasource: [ 29.570013] ------------[ cut here ]------------
[ 29.575937] kernel BUG at mm/slub.c:3601!
[ 29.580741] invalid opcode: 0000 [#1] SMP
[ 29.585663] Modules linked in: wireguard(OE) veth vxlan ip6_udp_tunnel
udp_tunnel bridge sd
[ 29.689129] CPU: 1 PID: 223 Comm: kworker/1:1 Tainted: G OE
------------ 3.101
[ 29.700019] Hardware name: Dell Inc. PowerEdge R640/0W23H8, BIOS 1.3.7
02/08/2018
[ 29.708399] Workqueue: wg-crypt-wg0 packet_rx_worker [wireguard]
[ 29.715340] task: ffff920e8b608000 ti: ffff920e8b610000 task.ti:
ffff920e8b610000
[ 29.723722] RIP: 0010:[<ffffffff8b1f6c1c>] [<ffffffff8b1f6c1c>]
kfree+0x13c/0x140
[ 29.732222] RSP: 0018:ffff920e8b613ce8 EFLAGS: 00010246
[ 29.738429] RAX: 006fffff00000000 RBX: ffff920e76fbf000 RCX:
00000000fffbdd13
[ 29.746466] RDX: 006fffff00000000 RSI: 0000000000000206 RDI:
ffff920e76fbf000
[ 29.754489] RBP: ffff920e8b613d00 R08: 0000000000000001 R09:
b7c55a3205f72200
[ 29.762508] R10: 0000000000000000 R11: ffffeddddfdbefc0 R12:
ffff920e76fbf6c0
[ 29.770525] R13: ffffffff8b5d60c5 R14: ffff920e80220000 R15:
ffff920e7e7e2500
[ 29.778535] FS: 0000000000000000(0000) GS:ffff920e8be00000(0000)
knlGS:0000000000000000
[ 29.787497] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 29.794125] CR2: 00007ffe415adee0 CR3: 0000000c0e1ea000 CR4:
00000000007607e0
[ 29.802143] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 29.810161] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[ 29.818152] PKRU: 00000000
[ 29.821713] Call Trace:
[ 29.825002] [<ffffffff8b5d60c5>] skb_release_data+0xf5/0x140
[ 29.831595] [<ffffffff8b5d6134>] skb_release_all+0x24/0x30
[ 29.838008] [<ffffffff8b5d659c>] consume_skb+0x2c/0x90
[ 29.844073] [<ffffffffc088df35>] packet_rx_worker+0x2d5/0x7f0
[wireguard]
[ 29.851802] [<ffffffff8b71291c>] ? __schedule+0x41c/0xa20
[ 29.858139] [<ffffffff8b0b2dff>] process_one_work+0x17f/0x440
[ 29.864817] [<ffffffff8b0b3ac6>] worker_thread+0x126/0x3c0
[ 29.871238] [<ffffffff8b0b39a0>] ? manage_workers.isra.24+0x2a0/0x2a0
[ 29.878612] [<ffffffff8b0bae31>] kthread+0xd1/0xe0
[ 29.884338] [<ffffffff8b0bad60>] ? insert_kthread_work+0x40/0x40
[ 29.891284] [<ffffffff8b71f61d>] ret_from_fork_nospec_begin+0x7/0x21
[ 29.898578] [<ffffffff8b0bad60>] ? insert_kthread_work+0x40/0x40
[ 29.905513] Code: 49 8b 03 31 f6 f6 c4 40 74 04 41 8b 73 68 4c 89 df e8
89 63 fa ff eb 84
[ 29.927746] RIP [<ffffffff8b1f6c1c>] kfree+0x13c/0x140
[ 29.933888] RSP <ffff920e8b613ce8>
[ 29.938300] ---[ end trace 66811942e35f2cba ]---
#
[ 29.948435] Kernel panic - not syncing: Fatal exception in interrupt
On Thu, May 10, 2018 at 1:26 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Yikes. I guess I need to examine my compat backport closely. Do you
> have any more logging than that? Usually there's a backtrace.
>
--
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: 4842 bytes --]
next prev parent reply other threads:[~2018-05-10 17:32 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 [this message]
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
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=CAFuSFDEREZibd5Vb-J1GreLK9ZV+y2wGOc5MuaHvHx4XdbwDkw@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).