Date: Fri, 11 Dec 2020 12:37:37 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 251736] [panic] memcpy_erms general protection fault on AMD Zen 3 (Ryzen 5000 series) Message-ID: <bug-251736-227-SIorzglPn4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251736-227@https.bugs.freebsd.org/bugzilla/> References: <bug-251736-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251736 --- Comment #12 from Greg V <greg@unrelenting.technology> --- Now testing upstream OpenZFS: - 2.0.0-rc1 + compat fixes (cherry-pick 01a65c58 f6bb7c029) = stable - 2.0.0-rc2 + INVARIANTS + compat fixes = FPU crash - 2.0.0-rc2 + INVARIANTS + compat fixes + FPU fix (e0716250bf) = unstable - 2.0.0-rc7 + INVARIANTS + FPU fix = stable - master + INVARIANTS = stable - master = stable (my stability test being running rm -rf /usr/obj/usr and buildkernel a few times while zpool scrub is going on) Conclusion: seems like that problem has been fixed upstream. Whatever it was. I'm not seeing anything obvious in the commit log o_0 -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251736-227-SIorzglPn4>