Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Jun 2018 11:12:04 -0400
From:      Mike Tancsa <mike@sentex.net>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        Eric van Gyzen <eric@vangyzen.net>, current@freebsd.org
Subject:   Re: Ryzen public erratas
Message-ID:  <1f0bb657-f371-3f50-23d9-96655464de8b@sentex.net>
In-Reply-To: <20180614150354.GB2493@kib.kiev.ua>
References:  <20180613103535.GP2493@kib.kiev.ua> <231dda70-6383-9d5c-d6c3-98e1c784f505@vangyzen.net> <402ba93e-4930-4237-dd53-d20a24b317e3@sentex.net> <20180614150354.GB2493@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On 6/14/2018 11:03 AM, Konstantin Belousov wrote:
> I am not sure about only microcode update.  Depending on the BIOS
> vendor and current BIOS, you may need all three: BIOS update, microcode
> update using cpucontrol/devcpu-data, and running the script I posted.
> In the best case, some of this is just redundand.

Thanks, I will run the tests on the Epyc system over the next few days.
It took a little longer to crash the Epyc than the Ryzen.  The Ryzen is
still going now for 20hrs.  Previously 5-10 min were enough to trigger
the hard lockup.

	---Mike


-- 
-------------------
Mike Tancsa, tel +1 519 651 3400 x203
Sentex Communications, mike@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1f0bb657-f371-3f50-23d9-96655464de8b>