On Thu, 24 May 2018 18:31:35 -0400 Rich Freeman <ri...@gentoo.org> wrote:
> On Thu, May 24, 2018 at 7:21 PM john <j...@jdm.myzen.co.uk> wrote: > > On Sun, 20 May 2018 23:20:36 +0100 > > Mick <michaelkintz...@gmail.com> wrote: > > > > On Sunday, 20 May 2018 21:54:32 BST Alan Mackenzie wrote: > > > > > > > > My system is an AMD Ryzen processor on an Asus Prime X370-Pro > > > > mainboard, and is just over a year old. > > > > > > Interesting post. > > Just read this and have same issue. > > AMD Ryzen > > X370 Asus motherboard > > > You guys don't have an early CPU with the segfault bug, do you? I > don't know if they ever fully characterized the circumstances that > can cause it, but if it can make a compiler segfault, I don't see why > it couldn't make a kernel panic. At least not without knowing more > about what actually triggers the bug... > Could be. I bought CPU only a month or so after release. Initially thought it was an enlightenment desktop issue but have reproduced on KDE and xfce. It happens usually when doing something quite simple like clicking on a Window to minimise or just in a terminal. Nothing stressful like an emerge gcc. Never found anything in logs but not sure if there is a better way to capture problem. Its a Ryzen 1700X John
