From owner-freebsd-stable@freebsd.org  Sun Jan 21 20:17:59 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:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B57A2EB86B2
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun, 21 Jan 2018 20:17:59 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "amnesiac", Issuer "amnesiac" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 938D97A5D1
 for <freebsd-stable@freebsd.org>; Sun, 21 Jan 2018 20:17:59 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org ([76.212.85.177])
 by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w0LKIMQm088878
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL);
 Sun, 21 Jan 2018 20:18:24 GMT (envelope-from truckman@FreeBSD.org)
Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w0LKHnFB040195
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Sun, 21 Jan 2018 12:17:51 -0800 (PST)
 (envelope-from truckman@FreeBSD.org)
Date: Sun, 21 Jan 2018 12:17:44 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: Ryzen issues on FreeBSD ?
To: Mark Millard <marklmi26-fbsd@yahoo.com>
cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
In-Reply-To: <EF6F255D-141D-4929-A3BE-0DDDBAAB9171@yahoo.com>
Message-ID: <tkrat.bffc09f63ec0b5e0@FreeBSD.org>
References: <EF6F255D-141D-4929-A3BE-0DDDBAAB9171@yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Content-Disposition: INLINE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.25
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: Sun, 21 Jan 2018 20:17:59 -0000

On 20 Jan, Mark Millard wrote:
> Don Lewis truckman at FreeBSD.org wrote on
> Sat Jan 20 02:35:40 UTC 2018 :
> 
>> The only real problem with the old CPUs is the random segfault problem
>> and some other random strangeness, like the lang/ghc build almost always
>> failing.
> 
> 
> At one time you had written
> ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029
> comment #103 on 2017-Oct-09):
> 
> QUOTE
> The ghc build failure seems to be gone after upgrading the a
> more recent 12.0-CURRENT.  I will try to bisect for the fix
> when I have a chance.
> END QUOTE
> 
> Did that not pan out? Did you conclude it was
> hardware-context specific?

I was never able to reproduce the problem.  It seems like it failed on
the first ports build run after I replaced the CPU.  When I upgraded the
OS and ports, the build succeeded.  I tried going back to much earlier
OS and ports versions, but I could never get the ghc build to fail
again.  I'm baffled by this ...