Date: Mon, 09 Oct 2017 07:17:06 +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-QFFfSSgzYq@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 #103 from Don Lewis <truckman@FreeBSD.org> --- For my next experiment, I built my usual set of packages using the same set= of jails that I use on my other build box: 10.4 i386 lang/go build failure (malloc corruption) 11.1 i386 lang/go build failure (malloc corruption) german/gimp-help multiple python SEGVs (memory corruption?) 11.1 amd64 lang/go build failure (fatal error: attempt to execute C code on Go sta= ck) lang/guile2 build failure (guile SEGV) math/scilab build failure (SEGV in Java Runtime Environment called from scilab when building docs) 12.0 amd64 lang/go build failure (crash during garbage collection) www/chromium configure failure (SIGTRAP in gn due to assertion failure) The go build failure seems to be specific to Ryzen and my replacement CPU d= id not fix it. 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. I've seen the guile failures on both my Ryzen machine and my AMD FX-8320E package build machine. The failures are somewhat sporadic. I've never seen the scilab or chromium failures before. The python SEGV failures look like a corrupted copy of the executable cache= d in RAM or in tmpfs). I do have ECC RAM and haven't seen any MCA errors of any kind since replacing my CPU. I also plan on bisecting userland to try to track down the sporadic build runaway errors that I've recently seen, both in earlier poudriere runs on my replacement CPU as well as on my FX-8320E. I suspect a userland problem si= nce I've only seen this when building using a 12.0-CURRENT jail and the problem appears to be recent. --=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-QFFfSSgzYq>