Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Dec 2020 22:32:00 +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-QbB3qTwwl2@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/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251736

Greg V <greg@unrelenting.technology> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |Not A Bug

--- Comment #8 from Greg V <greg@unrelenting.technology> ---
Closing as there's no ERMS bug, but it seems that there is *some* bug causi=
ng
wild instability on these CPUs that was added in the last couple months.

Testing log:

- turned off all overclocking (even XMP, RAM is 2400MHz now) just to be sur=
e,
turned off ERMS, basically running stock firmware settings
- everything seems perfectly stable on a kernel from September
- rebuilt current kernel cleanly (erasing /usr/obj and ccache), unstable
- rebuilt it with llvm10, unstable
- rebuilt it without CPUTYPE, unstable
- rebuilt the exact git revision of the September kernel, fine!

--=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-251736-227-QbB3qTwwl2>