Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jean-Denis Girard <jd.girard@sysnux.pf>
To: wireguard@lists.zx2c4.com
Subject: Re: Kernel Panic after updating Kernel
Date: Thu, 18 Jun 2020 06:48:22 -1000	[thread overview]
Message-ID: <1e6ef75d-3657-888a-51dd-0bedf8783904@sysnux.pf> (raw)
In-Reply-To: <CAHmME9qyk41mAvSiEePmZDrmmsBwOVSejg8q+oXV7nb=Jo1SAQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2020 bytes --]

Hi list,

Le 17/06/2020 à 19:53, Jason A. Donenfeld a écrit :
> Hmm, still not able to reproduce.
> 
> Are you sure you're running the latest up to date module? Try
> uninstalling kmod-wireguard and reinstalling?
> 
> What driver is your ethernet NIC using?
> 

For what it's worth, I seem to have the same problem on a CentOS-7
virtual machine hosted on VMware with vmxnet3. It has been working fine
since installed in 2017, but does lock up after upgrading to
kernel-3.10.0-1127.8.2.el7.x86_64 or kernel-3.10.0-1127.10.1.el7.x86_64.
The VM is now running fine on kernel-3.10.0-1062.18.1.el7.x86_64.

[    4.751926] NET: Registered protocol family 40
[    5.008840] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 3
vectors allocated
[    5.009298] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[    9.148571] vmxnet3 0000:13:00.0 ens224: intr type 3, mode 0, 3
vectors allocated
[    9.149062] vmxnet3 0000:13:00.0 ens224: NIC Link is Up 10000 Mbps
[   13.318360] vmxnet3 0000:1b:00.0 ens256: intr type 3, mode 0, 3
vectors allocated
[   13.318908] vmxnet3 0000:1b:00.0 ens256: NIC Link is Up 10000 Mbps
[   17.704052] FS-Cache: Loaded
[   17.823986] FS-Cache: Netfs 'nfs' registered for caching
[   17.837062] Key type dns_resolver registered
[   17.867211] NFS: Registering the id_resolver key type
[   17.867218] Key type id_resolver registered
[   17.867220] Key type id_legacy registered
[   17.879846] wireguard: module verification failed: signature and/or
required key missing - tainting kernel
[   17.886512] wireguard: WireGuard 1.0.20200520 loaded. See
www.wireguard.com for information.
[   17.886514] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld
<Jason@zx2c4.com>. All Rights Reserved.
[  564.297446] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)


Thanks,
-- 
Jean-Denis Girard

SysNux                   Systèmes   Linux   en   Polynésie  française
https://www.sysnux.pf/   Tél: +689 40.50.10.40 / GSM: +689 87.797.527


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-06-18 16:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 19:30 dxiri
2020-06-17  8:32 ` Jason A. Donenfeld
2020-06-18  4:31   ` dxiri
2020-06-18  5:53     ` Jason A. Donenfeld
2020-06-18 16:48       ` Jean-Denis Girard [this message]
2020-06-18 19:27         ` Jason A. Donenfeld
2020-06-18 19:48         ` Jason A. Donenfeld
2020-06-18 20:10           ` Jean-Denis Girard
2020-06-18 20:11             ` Jason A. Donenfeld
2020-06-19  6:58               ` Jean-Dens Girard
2020-06-19  7:38                 ` Jason A. Donenfeld
2020-06-27  1:26                   ` Jean-Denis Girard
     [not found]               ` <975a5f77-5c7e-dcfe-6bbe-d4b6e2c5e379@53c70r.de>
2020-06-21 12:57                 ` Silvan Nagl
2020-06-18 11:02     ` Phil Perry

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=1e6ef75d-3657-888a-51dd-0bedf8783904@sysnux.pf \
    --to=jd.girard@sysnux.pf \
    --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).