Date: Thu, 03 Aug 2017 04:46:20 +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-bXmQrDxAhn@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 #202 from Don Lewis <truckman@FreeBSD.org> --- (In reply to Nils Beyer from comment #200) I believe so. It's pretty unlikely that the problem is caused by undefined opcodes, and we are not seeing any evidence (SIGILL) of valid instructions being trapped as invalid because they experience page faults mid-fetch. BTW, using either my origin workaround patch, or the committed version if t= he sv_maxuser adjustment is commented out, it is possible to use a user proces= s to mmap() the top page of user memory, load some code up there, and execute it= for testing purposes. I've done some experiments with that and it is possible = to quickly hang the machine or cause it to reboot. The interesting thing is t= hat I haven't observed any ill effects as long as no instructions are executed above 0x7fffffffff40. That's sort of in the area mentioned in the Dragonfly fix, but even they saw issues at addresses lower than that and a decreasing rate as the address was lowered. Our signal trampoline code was much close= r to the bottom of the page at 0x7ffffffff000, so at this point I don't know why= we were having problems. The only thing that I can think of is that the signal trampoline code uses some unusual instructions like syscall and hlt, which = are unlike the more vanilla instructions that I was using in my experiments. --=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-bXmQrDxAhn>