From owner-freebsd-bugs@freebsd.org  Tue Jul  4 09:51:14 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 9BE5DD8C495
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  4 Jul 2017 09:51:14 +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 8993F7543D
 for <freebsd-bugs@FreeBSD.org>; Tue,  4 Jul 2017 09:51:14 +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 v649pEAS000291
 for <freebsd-bugs@FreeBSD.org>; Tue, 4 Jul 2017 09:51:14 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: Tue, 04 Jul 2017 09:51:14 +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: <bug-219399-8-nqFtBWEuxn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219399-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-219399-8@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jul 2017 09:51:14 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399

--- Comment #41 from Nils Beyer <nbe@renzel.net> ---
I think you mean this post here:

    https://community.amd.com/message/2802591#comment-2802591

Well, maybe the hysteresis temperature of Ryzen is not 75=C2=B0C but rather=
 50=C2=B0C,
meaning as soon as the CPU reaches (IMHO rather low) 50=C2=B0C it starts be=
coming
susceptible to data corruption. That would explain the behaviour here on my
system.

One guy here "tosilva" suspects that there is a signal integrity issue:

    https://community.amd.com/message/2808194#comment-2808194

that could possibly be fixed by raising voltages; what voltages excactly he
doesn't tell - so I assume every voltage. And by what amount - no idea.

That's what I'm trying right now, raising every voltage by 100mV:

    CPU Voltage: 1.18750 -> 1.28750
    VPPM: 2.550 -> 2.650
    2.50V Voltage: 2.520 -> 2.620
    DRAM Voltage: 1.210 -> 1.310
    +1.8 Voltage: 1.820 -> 1.920
    VDDP: 0.950 -> 1.050
    1.05V Voltage: 1.072 -> 1.072 (can only be raised several mV, so I left=
 it
AUTO)

--=20
You are receiving this mail because:
You are the assignee for the bug.=