Date: Mon, 24 Jul 2017 23:19:27 +0000 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... 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219399-8-t0uSup5hWq>