From owner-freebsd-bugs@freebsd.org  Wed Jul 26 19:08:20 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 B43F4DAE093
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 26 Jul 2017 19:08:20 +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 9C773733B0
 for <freebsd-bugs@FreeBSD.org>; Wed, 26 Jul 2017 19:08:20 +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 v6QJ8JaB014178
 for <freebsd-bugs@FreeBSD.org>; Wed, 26 Jul 2017 19:08:20 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: Wed, 26 Jul 2017 19:08:20 +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: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: markmi@dsl-only.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-CP6UGOMas6@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: Wed, 26 Jul 2017 19:08:20 -0000

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

--- Comment #154 from Mark Millard <markmi@dsl-only.net> ---
(In reply to Don Lewis from comment #149)

It is my understanding that many Ryzen 7
boards allow ECC memory but do not use the ECC
functionality: either the board is not wired
or else the BIOS does not configure for it.

For example:

7A32v1.0(G52-7A321X1)(X370 GAMING PRO CARBON).pdf

says:

Supports ECC UDIMM memory (non-ECC mode)

(It does not say if the board is wired to allow
ECC or not so I've no clue if a BIOS update
might be able to enable support of ECC mode.)

So it appears that:

"Too bad you're not running ECC RAM, that would eliminate one potential sil=
ent
cause of strange behavior"

needs more context, such as "on a board that
uses ECC mode (when appropriately configured
if needed)".

It may be that most folks would not have ECC
ram put to use for their boards.

(The X370 GAMING PRO CARBON that I had access
to was turned into a brick by a BIOS update
attempt and I do not yet have access to another
Ryzen system.)

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