From owner-freebsd-stable@freebsd.org  Thu Jul  5 10:13:15 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06901103D8F7
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Thu,  5 Jul 2018 10:13:15 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 54FA373997;
 Thu,  5 Jul 2018 10:13:14 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk)
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>)
 id 1fb1GA-000PmI-8i; Thu, 05 Jul 2018 10:13:10 +0000
Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91
 (FreeBSD)) (envelope-from <petefrench@ingresso.co.uk>)
 id 1fb1GA-0000s2-Cy; Thu, 05 Jul 2018 11:13:10 +0100
To: kostikbel@gmail.com, petefrench@ingresso.co.uk
Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround)
Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org,
 freebsd@hda3.com, truckman@FreeBSD.org
In-Reply-To: <343bb693-850b-92b0-9749-5c722b90f817@ingresso.co.uk>
Message-Id: <E1fb1GA-0000s2-Cy@dilbert.ingresso.co.uk>
From: Pete French <petefrench@ingresso.co.uk>
Date: Thu, 05 Jul 2018 11:13:10 +0100
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2018 10:13:15 -0000

So, I got my first lockup in weeks, testing with the latest stable
and the patch which sets the kernel bits. But I cant say it its
Ryzen related or not.

Meanwhile I also got access to an Epyc server in Azure. Am also
runing the latest STABLE on that tp see how it goes. Interesting
thing there is that there appears to be no access to the MSR's.
They all appear as zerousing cpucontrol. I am not entirely surprised
by this as the are very low level, but I di think they were saved
and restored during context switches between virtual machines so I
was hoping to be able to set them. Is this normal ?

-pete.