From owner-freebsd-bugs@freebsd.org Mon Jul 3 14:31:36 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 4D9F49E7DB1 for ; Mon, 3 Jul 2017 14:31:36 +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 2C5C1725FF for ; Mon, 3 Jul 2017 14:31:36 +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 v63EVZq6030689 for ; Mon, 3 Jul 2017 14:31:36 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:31:36 +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:31:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #32 from Nils Beyer --- Looks good; if you check via the command "top", you should see CPU usage. A= nd please check with the command "mount" whether the TMPFS is really mounted to "/tmp/ryzen_stress_test"; the output should look something like this: ------------------------------------------------------------------------ zroot on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs, local, multilabel) tmpfs on /tmp/buildworld (tmpfs, local, nosuid, mounted by nbe) ------------------------------------------------------------------------ Last line with "tmpfs" is important. If the bug is triggered, you will get ".log" files in your home dir. You can look in to "nohup.out" to check the errorcodes of each loop. Errorcode zero= (0) means all okay, Errorcode two (2) probably means Ryzen "bug", like here: ------------------------------------------------------------------------ umount: /tmp/ryzen_stress_test: not a file system root directory mkdir: /tmp/ryzen_stress_test: File exists Mon Jul 3 16:10:32 CEST 2017 begin Mon Jul 3 16:23:53 CEST 2017 end - errorcode 2 ------------------------------------------------------------------------ 5MB log file means that the buildworld/buildkernel is not finished yet. Let= it run; it can take several hours to trigger that error. After 48h, if all your loops end with zero errorcode, then your system really seems stable now... --=20 You are receiving this mail because: You are the assignee for the bug.=