Date: Thu, 20 Jul 2017 11:10: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-NGW29hXOaP@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 #85 from Nils Beyer <nbe@renzel.net> --- (In reply to Andriy Gapon from comment #83) makes sense to me; if there are undetected errors in the instruction cache = like corrupted memory addresses that would explain these corrupted stack traces, too. I got these messages on an other Ryzen system, too; different core, but sti= ll "MCA: CPU 10 COR ICACHE L1 IRD error". No system lock-ups or reboots there = yet, but this system is not poudriering due to lack of RAM (only 16GB). The only thing I did there was buildworlds in a RAM disk; and failed serveral times because of the "unable to rename temporary"-TMPFS-phenonema. The CPU is the same model (1700) but bought three months after my CPU, so I don't think it= 's the same batch. For me, the hints lead more and more to a design flaw within the CPU; and hopefully, that could be fixed with a microcode update... --=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-NGW29hXOaP>