Date: Sat, 02 Dec 2017 06:36:04 +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-Q0EHc7NDws@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 #104 from Mark Millard <markmi@dsl-only.net> --- (In reply to Don Lewis from comment #103) I'm experimenting with a Ryzen Threadripper 1950X on head -r326192 an /usr/ports/ -r454407 and its first go build got: . . . bytes strings hash/adler32 fatal error: attempt to execute C code on Go stack bufio runtime stack: runtime.throw(0x67f725) /usr/local/go14/src/runtime/panic.go:491 +0xad badc() /usr/local/go14/src/runtime/stack.c:891 +0x2a runtime.onM(0x68b110) /usr/local/go14/src/runtime/asm_amd64.s:257 +0x68 runtime.mstart() /usr/local/go14/src/runtime/proc.c:818 So about the same as you got on amd64 with 11.1 . The 2nd attempt built go fine. (The ghc build went fine but I guess that is now expected, though I do not know just what changed.) Most failing builds seem to be reliably failing when retried. At this point I've been focused on "fails initially then later retry works" So far none of these trace back to SIGSEGV or SIGBUS in the failures. FYI for the initial from-scratch bulk -a (i.e., with -C after smaller experiments): QUEUE BUILT FAIL SKIP IGNORE REMAIN TIME=20=20=20=20=20 27777 25049 364 2015 349 0 54:09:28 Context: Running in a Windows 10 Pro Hyper-V Virtual Machine, 29 logical processors assigned (of 2*16 in hardware), 110592 MBytes RAM assigned. Samsung 960 Pro 1 TByte nvme-ssd for the file system (not a .vhd* file under NTFS), 262144 MByte swap partition on a separate device (again, not inside NTFS). UFS, not ZFS USE_TMPFS=3Dyes no PARALLEL_JOBS assignment, so, 29 builders ALLOW_MAKE_JOBS=3Dyes (so possibly 29*29 active processes) no CCCACHE use I build with both optimizations and debug information. . . /usr/ports/Mk/bsd.port.mk has: STRIP_CMD=3D ${TRUE} .endif DEBUG_FLAGS?=3D -g +.if defined(ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG) +CFLAGS:=3D ${CFLAGS} ${DEBUG_FLAGS} +.else CFLAGS:=3D ${CFLAGS:N-O*:N-fno-strict*} ${DEBUG_FLAGS} +.endif .if defined(INSTALL_TARGET) INSTALL_TARGET:=3D ${INSTALL_TARGET:S/^install-strip$/install/g} .endif and /usr/local/etc/poudriere.d/make.conf has: WANT_QT_VERBOSE_CONFIGURE=3D1 # DEFAULT_VERSIONS+=3Dperl5=3D5.24 gcc=3D7 # # From a local /usr/ports/Mk/bsd.port.mk extension: ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG=3D # .if ${.CURDIR:M*/devel/llvm*} #WITH_DEBUG=3D .elif ${.CURDIR:M*/lang/cling*} #WITH_DEBUG=3D .elif ${.CURDIR:M*/www/*webkit*} #WITH_DEBUG=3D .else WITH_DEBUG=3D .endif MALLOC_PRODUCTION=3D (Note: lang/cling above was added after observing the -C -a build time-out the packaging of its 16GB+ build. Similarly www/qt5-webkit was generalized to www/*webkit* . Under WITH_DEBUG=3D these are massively huge and fail.) [My only attempt to boot -r326192 directly did boot but in-use soon ethernet and the USB keyboard and USB mouse where hung up. I've not pursued this any farther but may someday.] The board/BIOS supports ECC mode but the RAM in use is not ECC RAM at this point. lang/guile2 built fine the first time. So did math/scilab and www/chromium . --=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-Q0EHc7NDws>