From owner-freebsd-bugs@freebsd.org  Mon Jul 24 22:18:01 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 9663FDA9FD4
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 24 Jul 2017 22:18:01 +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 842787F05E
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Jul 2017 22:18:01 +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 v6OMI1CQ046568
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Jul 2017 22:18:01 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, 24 Jul 2017 22:18:01 +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 Only Me
X-Bugzilla-Who: truckman@FreeBSD.org
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-thqzoGy0nq@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, 24 Jul 2017 22:18:01 -0000

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

--- Comment #107 from Don Lewis <truckman@FreeBSD.org> ---
(In reply to SF from comment #104)
The temperature in my un-airconditioned office varies quite a bit and I've
never been able to correlate the observed instability with temperature.  I
first assembled the system before the heat of summer and it crashed.  These
days it will crash during he cool night hours with the office window open a=
nd
the cool outside air blowing on it.  It will crash in the late afternoon wh=
en
the sun has been coming in through west-facing glass door and making the ro=
om
uncomfortably hot.  It will crash under full load or with only two cores
enabled in the BIOS and SMT off.  It will crash with the system fans under
temperature control or turned on full blast.

With my patch, the I had no problems doing repeated openjdk builds during t=
he
cool overnight hours and no problems with a lengthy poudriere run on an
especially warm day in my office.

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