Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 05 Feb 2018 16:50:41 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 225584] Various compile process hang on Ryzen, but not on Intel
Message-ID:  <bug-225584-8-AUrSKp2ccS@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-225584-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-225584-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225584

--- Comment #11 from Eugene Grosbein <eugen@freebsd.org> ---
(In reply to mike from comment #9)

These threads locked in "umtxn" state remind me of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 that revealed
long-standing bugs in our libc
being not cancel-safe for multi-threaded code (fixed now). The problem was a
race and could be reproduced in very specific load pattern leading mutex lo=
ck
leak and following live-lock.

I suspect we may be facing similar problem here that is not hardware-specif=
ic
but is more probably to hit with specific hardware due to different timings.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225584-8-AUrSKp2ccS>