Date: Tue, 01 Aug 2017 02:01:07 +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-HHc4uFE6NN@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 #193 from Don Lewis <truckman@FreeBSD.org> --- (In reply to rozhuk.im from comment #190) I don't see that change in the March 2017 AMD64 Architecture Programmer=E2= =80=99s Manual Volume 2: System Programming (revision 3.28), which I found here: http://support.amd.com/TechDocs/24593.pdf The only change to the #UD description is the addition of the UD0 and UD1 instructions as potential causes. I didn't find these in the AMD documentation, but apparently they are reserved opcodes that will generate = #UD. It looks to me like encountering this bug will kill the process with SIGILL, which we aren't seeing. Working around this looks like it would be ugly ... --=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-HHc4uFE6NN>