Date: Sun, 21 Jan 2018 12:17:44 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: Mark Millard <marklmi26-fbsd@yahoo.com> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Ryzen issues on FreeBSD ? Message-ID: <tkrat.bffc09f63ec0b5e0@FreeBSD.org> In-Reply-To: <EF6F255D-141D-4929-A3BE-0DDDBAAB9171@yahoo.com> References: <EF6F255D-141D-4929-A3BE-0DDDBAAB9171@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.bffc09f63ec0b5e0>