Date: Thu, 20 Jul 2017 08:21:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen... Message-ID: <bug-219399-8-ilG9XL6b2m@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219399-8@https.bugs.freebsd.org/bugzilla/> References: <bug-219399-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=3D219399 --- Comment #74 from Nils Beyer <nbe@renzel.net> --- (In reply to Don Lewis from comment #70) Don, many thanks for your extensive report. Regarding building "java/openjdk7": that never did trigger a hard-lock or a reboot on my system here, unfortunately. The Java compilations of different ports don't care about processor limitations; they always use all available cores - at least here during my poudriere runs. So this could help stressing your system until crash. Regarding "DragonflyBSD patch": okay, makes sense that this patch is not needed/incompatible on FreeBSD. Thanks for the clarification. Regarding building "lang/ghc": yes, that build always generates a "bus erro= r" on my Ryzen system. On my Intel system, that build is always successful. Ma= ybe expected behaviour due to wrongly optimized bootstrap. Regarding i386 builds: interesting that there seems to be no problems in 32= bit environments. But I don't want to go back to 32bit. ;-) Regarding serial console: thanks for trying that out - I fear that you won't get any debug messages during the crashes/lock-ups though. But let's hope t= he best. --=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-219399-8-ilG9XL6b2m>