From owner-freebsd-bugs@freebsd.org Fri Jun 30 17:01:31 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 0E134D961DE for ; Fri, 30 Jun 2017 17:01:31 +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 EF86175764 for ; Fri, 30 Jun 2017 17:01:30 +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 v5UH1UOD049125 for ; Fri, 30 Jun 2017 17:01:30 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 17:01:30 +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: shitman71@hotmail.com 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 17:01:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #19 from SF --- To me it is the complete opposite, my system runs too hot. Up to 70=C2=B0C = or higher under full load. Changing Voltages to lower values and power-settings to what i described improved it to me, my system stays far longer running before crashing. With= far longer i mean it runs several hours under heavy load while with default-settings it only runs less then a hour before crashing. We are using different Mainboards which means they have different solutions delivering p= ower to the cpu but in general i did read this from several people having improv= ed their crashing-problems by changing power-settings. You can try setting your ram manually to what is inside xmp but this didnt = made any difference and i tryed all kinds of settings, even custom. All you can and need to do is changing the values tCL, tRCD, tRP, tRAS. The= se are four, not five. Only setting these values will make a difference to my experiences. Put command-rate to 2T, 1T is always causing crashes to me. 2T= in generals i known to be much more stable then 1T with minor performance-impa= cts. (2-3%) You might also check your ramvoltage, if you did forgot this. Increasing he= lps for higher performance, decreasing gets you more stable. Don't place more then 2 rams into your system, ensure they are seperated fr= om each other. This will increase stability and performance. Single-ranked ram= is also more stable to higher frequencys and has more performance then dual-ra= nked but dual-ranked is more efficient at costs. Dual-rank will outperform single-ranked ram if they are on equal frequencys. https://www.amd.com/system/files/2017-06/am4-motherboard-memory-support-lis= t-en.pdf You can use higher rams at your own risk, i know some people did reach 3600= Mhz with my ram already. I can only achieve 3333Mhz. --=20 You are receiving this mail because: You are the assignee for the bug.=