From owner-freebsd-bugs@freebsd.org  Mon Jul 24 23:19:29 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 1E358DAAFBE
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 24 Jul 2017 23:19:29 +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 0C51D808C1
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Jul 2017 23:19:29 +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 v6ONJRZk004565
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Jul 2017 23:19:28 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 23:19:27 +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-t0uSup5hWq@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 23:19:29 -0000

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

--- Comment #113 from Don Lewis <truckman@FreeBSD.org> ---
(In reply to Nils Beyer from comment #112)
Hmn ... what I though of a bug may not have been a bug after all ...

I missed the fact that that main initially set the lock, so the first insta=
nce
of threadx() should have properly initialized things afterall.  With the in=
it
code removed, that instance of threadx() just spins on the lock instead of
doing the init stuff and then unlocking things and letting the other threads
run.

In this code in main():
         atomic_store(&flg, 1);
         atomic_store(&locked, 1);
change the second line so that locked is initialized to zero.

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