From owner-freebsd-bugs@freebsd.org  Wed Jul 26 20:30:58 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 F29C3DAFB36
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 26 Jul 2017 20:30:58 +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 E095C75CC0
 for <freebsd-bugs@FreeBSD.org>; Wed, 26 Jul 2017 20:30:58 +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 v6QKUvw4032623
 for <freebsd-bugs@FreeBSD.org>; Wed, 26 Jul 2017 20:30:58 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 20:30:58 +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-cYKrN57y1P@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 20:30:59 -0000

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

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

Note: I can not claim to know for

In:

Physical Memory Array
. . .
        Error Correction Type: Multi-bit ECC

I wonder if it says that even with non-ECC RAM in
one or more (or all) DIMMs. That section is not
DIMM specific at all from what I can tell. But
may be some of it is a summary over all DIMMs?
(My guess is: no.)

In:

Memory Device
. . .
        Error Information Handle: 0x002D
        Total Width: 128 bits
        Data Width: 64 bits

vs. the older, narrower context's

Memory Device
. . .
        Error Information Handle: Not Provided
        Total Width: 72 bits
        Data Width: 64 bits

The 128 bits instead of 128+8 or 128+2*8 bits
suggests lack of ECC use at the DIMM in
question.

But I'm unable to test a Ryzen context for now
so take my notes in this area as speculation
(or as a suggestion for contrasting tests that
I might have performed if the Ryzen system still
worked, presuming some non-ECC RAM is available
to substitute temporarily).

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