From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jean-Dens Girard <jd.girard@sysnux.pf>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel Panic after updating Kernel
Date: Fri, 19 Jun 2020 01:38:02 -0600 [thread overview]
Message-ID: <CAHmME9qy4j2XpsTu1syABo1g6BZyS4w3OYghmT4T2kj7WjTyyQ@mail.gmail.com> (raw)
In-Reply-To: <975a5f77-5c7e-dcfe-6bbe-d4b6e2c5e379@sysnux.pf>
On Fri, Jun 19, 2020 at 12:58 AM Jean-Dens Girard <jd.girard@sysnux.pf> wrote:
>
> Le 18/06/2020 à 10:11, Jason A. Donenfeld a écrit :
> > On Thu, Jun 18, 2020 at 2:10 PM Jean-Denis Girard <jd.girard@sysnux.pf> wrote:
> >> I cannot reboot now, I will let you know how it goes later.
>
> Reboot with newer kernel and latest wireguard still hangs.
>
> > Oh, in your case, you appear to be using the dkms package instead of
> > the elrepo package.
>
> Is that a problem?
Remove all wireguard packages. Update to the latest kernel. Run `find
/lib/modules -name '*wireguard*' -print -delete`. Then install
kmod-wireguard.
For further help, you're probably best off asking on IRC. From
debugging this with the original reporter there, this turned out to be
a mixing and matching of versions issue due to weird yum things.
next prev parent reply other threads:[~2020-06-19 7:38 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
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 [this message]
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=CAHmME9qy4j2XpsTu1syABo1g6BZyS4w3OYghmT4T2kj7WjTyyQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=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).