wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: trulyliu <trulyliu@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Ryzen 3000 CPU soft lockup
Date: Tue, 27 Aug 2019 13:41:27 +0800	[thread overview]
Message-ID: <CANNc_DQL+xMLT+2-W5UGUCq41hpCZHSCnuKU49s0E3WP3EQ9BQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rGNPRtoAhi2Y94sMk8B-Q9f++v0S8rprTpwakV+a1Jig@mail.gmail.com>


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

ASUS  does not follow AMD microcode release in time, the latest motherboard
bios are using two month ago AMD
microcode.
Tried CPU's microcode with kernel, didn't work either.
fortunately, found a solution from arch linux comunity.  Appending nordrand
kernel parameter in grub resolved the issue.
Hope this can be documented some where to help others.


Jason A. Donenfeld <Jason@zx2c4.com> 于 2019年8月25日周日 23:51写道:

> 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.
>

[-- Attachment #1.2: Type: text/html, Size: 1040 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-08-27  5:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  5:09 Ryzen 3000 CPU soft lockup trulyliu
2019-08-25 15:51 ` Jason A. Donenfeld
2019-08-27  5:41   ` trulyliu [this message]

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=CANNc_DQL+xMLT+2-W5UGUCq41hpCZHSCnuKU49s0E3WP3EQ9BQ@mail.gmail.com \
    --to=trulyliu@gmail.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).