From owner-freebsd-bugs@freebsd.org Sat Aug 5 01:21:06 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 2FF91DD395E for ; Sat, 5 Aug 2017 01:21:06 +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 1BDA2832E0 for ; Sat, 5 Aug 2017 01:21:06 +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 v751L5YC073768 for ; Sat, 5 Aug 2017 01:21:05 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, 05 Aug 2017 01:21:05 +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: nbe@renzel.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: 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, 05 Aug 2017 01:21:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #205 from Nils Beyer --- (In reply to Don Lewis from comment #204) absolutely wonderful test case you've created - despite your instructions I= 've run that program on a vanilla 11.1-RELEASE (no patches) on my second Ryzen system (the one with 16GB where I've never poudriered), and it freezes exac= tly there where you have experienced it (done it via SSH, so output is still visible): ---------------------------------------------------------------------------= ---- [...] executing at 0x7fffffffff30 .......... executing at 0x7fffffffff31 .......... executing at 0x7fffffffff32 .......... executing at 0x7fffffffff33 .......... executing at 0x7fffffffff34 .......... executing at 0x7fffffffff35 .......... executing at 0x7fffffffff36 .......... executing at 0x7fffffffff37 .......... executing at 0x7fffffffff38 .......... executing at 0x7fffffffff39 .......... executing at 0x7fffffffff3a .......... executing at 0x7fffffffff3b .......... executing at 0x7fffffffff3c .......... executing at 0x7fffffffff3d .......... executing at 0x7fffffffff3e .......... executing at 0x7fffffffff3f .......... executing at 0x7fffffffff40 ... ---------------------------------------------------------------------------= ---- tried that on my Intel Xeon E3-1220 v3 system, but had to use the second "WHERE"-define because it couldn't mmap at 0x7f(...) - ENOMEM. Anyways, the result is that it didn't freeze there... --=20 You are receiving this mail because: You are the assignee for the bug.=