Date: Mon, 07 Aug 2017 22:22:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld Message-ID: <bug-221029-8-7GbUvPhgxC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221029-8@https.bugs.freebsd.org/bugzilla/> References: <bug-221029-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #63 from Don Lewis <truckman@FreeBSD.org> --- (In reply to Nils Beyer from comment #61) Hard to say ... If it is something triggered by context switches and is well understood, it might be possible to add some synchronization code in that path as a workaround. It might be a slow path through some logic that was missed by AMD's test procedures. My testing does seem to indicate that there could be a sensiti= vity to the core clock speed, but it doesn't seem to be a sharp edge, and it also doesn't seem to be temperature sensitive. Doing a better job of testing sh= ould catch the bad chips, at the possible expense of throwing out a lot of them.= It might be possible to work around that in microcode by allowing more time for the signals propagate. It could also be some sort of other signal integrity problem, which should = also be possible to catch in test, but would be more difficult to work around. In either of these cases, the best long term fix is a new stepping. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221029-8-7GbUvPhgxC>