Date: Tue, 30 May 2017 08:58:52 +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-746sY1UjJK@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 #9 from Andriy Gapon <avg@FreeBSD.org> --- Nils, I am not aware of any "mini test" that would be as good as a poudriere buil= d or a highly parallel buildworld. I am not sure that the nvidia is really a culprit here, the stack frames be= yond the trap frame look rather messed up. Maybe it's not that surprising given that the original trap type is 0xc, #SS, Stack-Segment Fault. Perhaps there was a stack overflow. If in kgdb you do 'list *0xffffffff831e410b', does it also point to _nv0002= 24rm ? The inability of kgdb to deal with the memory dump suggests a possibility of critical page table structures being corrupt or a significant binary mismat= ch between the userland (libkvm, etc) and the kernel. FWIW, I found a bug report with somewhat similar backtrace, but it does not have any enlightening details: bug #193622. Perhaps a mismatch between the module and the kernel... --=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-746sY1UjJK>