From owner-freebsd-bugs@freebsd.org Sat Oct 7 19:27:10 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 0E33FE40601 for ; Sat, 7 Oct 2017 19:27:10 +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 5BE96334C for ; Sat, 7 Oct 2017 19:27:09 +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 v97JR8St051719 for ; Sat, 7 Oct 2017 19:27:09 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: Sat, 07 Oct 2017 19:27:08 +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: truckman@FreeBSD.org 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: Sat, 07 Oct 2017 19:27:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #252 from Don Lewis --- (In reply to SF from comment #250) This mega-thread https://community.amd.com/thread/215773?start=3D0&tstart= =3D0 on AMD Community Forum is full of Linux users who are experiencing random segfaults when doing parallel compiles. Lots of experiments with different voltage settings, RAM timing settings, and tweaking of other BIOS knobs. AMD eventually admitted that there is a "performance marginality" issue and= has been doing warranty replacements for customers who run into this problem.=20 Sometimes they request that the customer perform some experiments with vari= ous voltage and other settings before approving the replacement, but I don't re= call seeing any success stories from that. AMD was apparently manually screening some of the replacement CPUs before shipping them, as evidenced by one of the seals on the replacement CPU being cut and traces of thermal compound on the CPU. At least in some cases AMD performed testing with hardware identical to the the customer's. The system crashes and hangs that I and many other FreeBSD users was caused= by the behavior of the instruction prefetch hardware near the maximum possible user address 0x7fffffffffff. This problem affected both FreeBSD and DragonflyBSD. I don't know about the other BSDs. We implemented an accept= able workaround in r321899. --=20 You are receiving this mail because: You are the assignee for the bug.=