From: Erik Jerde <erik@jerde.org>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard causes system to hang
Date: Sun, 25 Aug 2019 14:17:28 -0500 [thread overview]
Message-ID: <4B05D371-79C3-40A2-9A30-F1FE0989E604@jerde.org> (raw)
In-Reply-To: <CAHmME9oqFzDF1YRuXiOybYFuG8mRZy7Wvy6dCQr+et5qqXfCJg@mail.gmail.com>
HI Jason, thanks for the info, I’ve been troubleshooting this same problem on my WireGuard VM which has made it a bit trickier. The info you posted cleared things up right quick for me. Do you happen to know what microcode version fixes this issue? I’m on 0x1000065 per /proc/cpuinfo but I can’t find any info on if that’s the “fixed” version or not. I’m running latest FW for my motherboard which is dated 8/7/19 (ASRock Rack X470D4U).
Thanks!
> On Aug 25, 2019, at 10:50 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> WireGuard uses get_random_u32 which uses rdrand. AMD shipped with a
> broken rdrand. Update your CPU's microcode or your motherboard's BIOS
> and all should be good.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-25 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 0:43 Wireguard causes system to hang Nicolas Chan
2019-08-25 15:50 ` Jason A. Donenfeld
2019-08-25 19:17 ` Erik Jerde [this message]
2019-08-25 19:25 ` Nicolas Chan
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=4B05D371-79C3-40A2-9A30-F1FE0989E604@jerde.org \
--to=erik@jerde.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).