From owner-freebsd-bugs@freebsd.org  Mon Oct  9 16:57: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 2E930E36378
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon,  9 Oct 2017 16:57: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 8FA9F6D93B
 for <freebsd-bugs@FreeBSD.org>; Mon,  9 Oct 2017 16:57:57 +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 v99GvtoZ057096
 for <freebsd-bugs@FreeBSD.org>; Mon, 9 Oct 2017 16:57:57 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: Mon, 09 Oct 2017 16:57:56 +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.1-RELEASE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: markmi@dsl-only.net
X-Bugzilla-Status: Open
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-ITCWKI58qD@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: Mon, 09 Oct 2017 16:57:58 -0000

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

--- Comment #268 from Mark Millard <markmi@dsl-only.net> ---
Just an FYI example about the hangups:

I'm aware of one example of someone with a
Ryzen 7 that was not having any of the hangup
problems until a BIOS update problem caused
a motherboard replacement (with the same
type of motherboard).

Same CPU, same low end video card, same memory,
same power supply, same pair of M.2 NVMe SSDs,
nothing else added or removed: just the
motherboard change.

And the result was a fairly rare example of the
hangup problem: screen goes blank, lights on
usb keyboard and mouse go off, ethernet
communication stops. But the motherboard
lights keep on updating like normal. Examples
include it happening while the system is
basically idle from a user point of view.

The context was a Windows 10 Pro installation,
not FreeBSD.

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