From owner-freebsd-bugs@freebsd.org Sun Oct 8 10:44:44 2017 Return-Path: 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 7B0DFE30DB9 for ; Sun, 8 Oct 2017 10:44:44 +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 3941A6414B for ; Sun, 8 Oct 2017 10:44:44 +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 v98Aigtu020521 for ; Sun, 8 Oct 2017 10:44:44 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: Sun, 08 Oct 2017 10:44:42 +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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 10:44:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #255 from Mark Millard --- (In reply to SF from comment #254) Just reporting a distinct example. . . The Ryzen 1800X system that I had access to for a time had water-based cooling that kept it under 47 degC even during hot summer days with no air conditioning but doing builds. (Clearly not true of any days getting near that temperature in the first place. But it gives a clue as to effectiveness.) The power supply was also good. There was only a basic, low power video card present. That did not stop the SIGSEGV's, missing temporary files, having lang/ghc almost always fail to build, etc. Although, in general, I seemed to get them somewhat less often than some folks seemed to be reporting --other than lang/ghc nearly always failing fairly rapidly. [Side question: Have you tested your ability to repeatedly rebuild lang/ghc from scratch? It was by far the most reliable failure that I found (that was a normal activity).] But I never observed the panics in normal operation, not even before the page-avoidance change was made. However, I was using 64-bit FreeBSD via Hyper-V with Windows 10 Pro as the boot OS. That might have caused automatic avoidance of the problematical page. (I also did a little VirtualBox activity instead of Hyper-V activity.) I tended to assign FreeBSD access to 14 hw-threads in Hyper-V, leaving 2 avoided for Windows 10 Pro availability. For the vast majority of things I'd left the BIOS at defaults. For example, no voltage changes of any kind --nor CPU frequency changes. AMD Cool' n' Quiet disabled, SVM Mode Enabled, Core C6 state disabled. 2nd memory profile used as-is. 2133 MT/s resulted. (It was not overclocking-style RAM.) And that is about it for adjustments. I no longer have access to that system. So that has limited what I managed to explore. It will probably be a month or so before I've access to a Ryzen system of some kind again. (A BIOS update failure also cut into the time I had on the Ryzen system: motherboard replacement.) --=20 You are receiving this mail because: You are the assignee for the bug.=