From owner-freebsd-bugs@freebsd.org Mon Jul 3 14:16:23 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 221319E7A6A for ; Mon, 3 Jul 2017 14:16:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBABB7204F for ; Mon, 3 Jul 2017 14:16:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v63EGMo5096807 for ; Mon, 3 Jul 2017 14:16:22 GMT (envelope-from bugzilla-noreply@freebsd.org) 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... Date: Mon, 03 Jul 2017 14:16:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: nbe@renzel.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2017 14:16:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #29 from Nils Beyer --- Hmm, are you probably a victim of the AMD Ryzen 20=C2=B0C temperature offse= t: =20=20=20 https://www.reddit.com/r/Amd/comments/607xg2/why_do_the_x_ryzen_cpus_have_a= _temperature_offset/ ? So your real temperatures were aroung 5X=C2=B0C? BTW: how do you measure = the CPU temperature under FreeBSD? Regarding my script - you are correct; it's an endless buildworld and buildkernel loop. Unfortunately, to catch the AMD Ryzen "bug", you need a T= MPFS mount. You can allow a user to mount TMPFS by executing following as root o= nce: sysctl vfs.usermount=3D1 source: https://www.freebsd.org/doc/handbook/usb-disks.html Here's the modified script that is able to run as user: --------------------------------------------- SNIP --------------------------------------------------- #!/bin/sh OBJDIR=3D"/tmp/ryzen_stress_test" trap "exit 1" 1 2 3 cd /usr/src umount ${OBJDIR} mkdir ${OBJDIR} mount -t tmpfs tmpfs ${OBJDIR} || exit 1 while [ 1 ]; do echo "`date` begin" BEG=3D"`date +%s`" make -j20 buildworld buildkernel MAKEOBJDIRPREFIX=3D${OBJDIR} >${OBJDIR}/${BEG}.log 2>&1 ERR=3D"$?" echo "`date` end - errorcode ${ERR}" [ "${ERR}" !=3D "0" ] && cp ${OBJDIR}/${BEG}.log ~/. rm ${OBJDIR}/${BEG}.log done --------------------------------------------- SNIP --------------------------------------------------- In this version the suspicious log files will be saved to your home dir. Ju= st save everything between the "SNIP"-lines to "ryzen_stress_test.sh" in your = home dir and then execute as user: /usr/bin/nohup sh ~/ryzen_stress_test.sh & This spawns the stress test in the background; to kill it, execute as user: pkill -f ryzen_stress_test then the remaining buildworld, buildkernel processes should die afterwards.= As user, execute: umount /tmp/ryzen_stress_test in order to unmount and erase the TMPFS buildowlrd/buildkernel temporary folder... --=20 You are receiving this mail because: You are the assignee for the bug.=