From owner-freebsd-bugs@freebsd.org Fri Jun 30 11:07:17 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 681BDD8E9A4 for ; Fri, 30 Jun 2017 11:07:17 +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 556EF64CAF for ; Fri, 30 Jun 2017 11:07:17 +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 v5UB7GvU027171 for ; Fri, 30 Jun 2017 11:07:17 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: Fri, 30 Jun 2017 11:07:17 +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: Fri, 30 Jun 2017 11:07:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #16 from Nils Beyer --- Sound loops are somewhat new to me - my music that is playing while using t= he computer just stops - no sound artifacts at all. Something else I've noticed are often messages in the poudriere logs like: error: unable to rename temporary '...' to output file '...': 'No such = file or directory' I'm using tmpfs for the work directories. So I've reconstructed that for a buildworld/buildkernel stress test: ---------------------------------------------------------------------------= ----------------- #!/bin/sh trap "exit 1" 1 2 3 cd /usr/src umount /usr/obj mount -t tmpfs tmpfs /usr/obj while [ 1 ]; do echo "`date` begin" BEG=3D"`date +%s`" make -j20 buildworld buildkernel >/usr/obj/${BEG}.log 2>&1 ERR=3D"$?" echo "`date` end - errorcode ${ERR}" [ "${ERR}" !=3D "0" ] && cp /usr/obj/${BEG}.log /usr/src/. rm /usr/obj/${BEG}.log done ---------------------------------------------------------------------------= ----------------- And yes, I get these "unable to rename..." messages as well: ---------------------------------------------------------------------------= ----------------- 1498777486.log:error: unable to rename temporary 'ofb_enc.pico-91eb399a' to output file 'ofb_enc.pico': 'No such file or directory' 1498797284.log:error: unable to rename temporary 'CodeGen/MachineModuleInfo.o-f77c51a1' to output file 'CodeGen/MachineModuleInfo.o': 'No such file or directory' 1498806242.log:error: unable to rename temporary 'dsl_deleg.o-68764d23' to output file 'dsl_deleg.o': 'No such file or directory' 1498807306.log:error: unable to rename temporary 'StaticAnalyzer/Frontend/ModelInjector.o-a246df8d' to output file 'StaticAnalyzer/Frontend/ModelInjector.o': 'No such file or directory' ---------------------------------------------------------------------------= ----------------- Maybe that is a good and quick indicator for something being wrong. Perhaps somebody can try that, too, please? As a side note, I've tried to set the RAM timings to something even, as I'm using a 2133 MHz RAM; the default timings are CL15, and in the AMD forum's thread here: https://community.amd.com/message/2805287 it is said that Ryzen has problems with odd timings. Unfortunately, no improvements raising CL to 16... --=20 You are receiving this mail because: You are the assignee for the bug.=