| 1 |
On Thu, May 24, 2018 at 7:21 PM john <jdm@××××××××××××.uk> wrote: |
| 2 |
> On Sun, 20 May 2018 23:20:36 +0100 |
| 3 |
> Mick <michaelkintzios@×××××.com> wrote: |
| 4 |
|
| 5 |
> > On Sunday, 20 May 2018 21:54:32 BST Alan Mackenzie wrote: |
| 6 |
> > > |
| 7 |
> > > My system is an AMD Ryzen processor on an Asus Prime X370-Pro |
| 8 |
> > > mainboard, and is just over a year old. |
| 9 |
> > > |
| 10 |
> Interesting post. |
| 11 |
> Just read this and have same issue. |
| 12 |
> AMD Ryzen |
| 13 |
> X370 Asus motherboard |
| 14 |
|
| 15 |
|
| 16 |
You guys don't have an early CPU with the segfault bug, do you? I don't |
| 17 |
know if they ever fully characterized the circumstances that can cause it, |
| 18 |
but if it can make a compiler segfault, I don't see why it couldn't make a |
| 19 |
kernel panic. At least not without knowing more about what actually |
| 20 |
triggers the bug... |
| 21 |
|
| 22 |
-- |
| 23 |
Rich |
Archives