From owner-freebsd-stable@freebsd.org Mon Jan 22 01:02:52 2018 Return-Path: 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 8E513EC5B17 for ; Mon, 22 Jan 2018 01:02:52 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic309-15.consmr.mail.bf2.yahoo.com (sonic309-15.consmr.mail.bf2.yahoo.com [74.6.129.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56CE992F for ; Mon, 22 Jan 2018 01:02:51 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: IRa.incVM1mkkWD.5c47acRgc45oUCuKy.VOZXTwDY0QZb8CyOSeI_9qX_beN_Z 5YIh9FiKjRP1AVrjEiYksQgg3fXZ.KgofHd3n7T568sy.lB4pCNItcA87fOm4k6OXRqFQlbtUkhv 6ouxiS54WkiEE6ocMs6KTdGjD5aI4dMpiCkKO4og4rmjHYm6mCiakG7u5ycix1FFIyYI3qbxtvGO nocU42YskqCp2gtujUdDh2hbl5p2WHN_z1Tjsrad3X50z0FvCFeORoOVI0sGYIXPcovXESPhz2aZ vaUI1n1S9G6KSGqOG9yMbjoGVV.YDo4caBtG_Ye54R0gbTbvGJU4OuWHpYCvlaUsAafTjtC6akpK i5tCSwdmg.V8RAVVzsvBKbPw7JpO8RGOFSixqkP8jUvvPcTlZe6RtE3pMYjACfwb2hccAVri1NKL zVHTehgArGFaJPw6duqd0aWVZprqaAJU8J2nVaf.ccjO0bWMal0OhUbBvRmT8q6Tl9oPX Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Mon, 22 Jan 2018 01:02:44 +0000 Received: from smtpgate102.mail.bf1.yahoo.com (EHLO [192.168.1.25]) ([72.30.28.113]) by smtp416.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 5be0b94c2a6cd1b2e7b53d583f096639; Mon, 22 Jan 2018 01:02:43 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Ryzen issues on FreeBSD ? From: Mark Millard In-Reply-To: Date: Sun, 21 Jan 2018 17:02:41 -0800 Cc: FreeBSD-STABLE Mailing List Content-Transfer-Encoding: 7bit Message-Id: <7F3E20DB-9BAB-4FD7-A574-5F1635FB2B8D@yahoo.com> References: To: Don Lewis X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 01:02:52 -0000 On 2018-Jan-21, at 12:17 PM, Don Lewis wrote: > 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 ... Sounds like the overall information is then: Old CPU: frequent problem building ghc (nearly always fails as far as I know) New CPU: rare problem building ghc (possibly never for some softare version combinations?) (On a Ryzen Threadripper 1950X I've not seen a failure. For the above I'm including what I observed under Hyper-V for the 1800X and 1950X as contributing evidence: The 1800X was a early one and fit the "Old CPU" case above. AMD has stated that threadrippers never had the problems that other, early Ryzen CPUs did for heavy compiling use. So far, for me, that seems true.) So, it sounds like building ghc is still a good test. Back when I had access to the 1800X Ryzen system ghc was the most reliable failure-to-build of what I tried. It still may be useful for that sort of test activity to classify Ryzen CPUs for the one type of issue. === Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late)