| 1 |
On Sun, Aug 27, 2017 at 7:03 AM, Alan Mackenzie <acm@×××.de> wrote: |
| 2 |
> |
| 3 |
> On Fri, Aug 25, 2017 at 15:46:31 +1000, Adam Carter wrote: |
| 4 |
>> FYI, you should be able to return your CPU for a fixed one now. |
| 5 |
> |
| 6 |
>> http://www.phoronix.com/scan.php?page=article&item=new-ryzen-fixed&num=1 |
| 7 |
> |
| 8 |
> Thanks for that. I wasn't actually aware anybody else was suffering |
| 9 |
> from this. |
| 10 |
> |
| 11 |
> I've had quite a few build failures with segmentation faults, always (as |
| 12 |
> far as I can tell) while building .lo files. Initially, I suspected the |
| 13 |
> RAM, but memtest presented a clean bill of health after several hours |
| 14 |
> testing. |
| 15 |
> |
| 16 |
> It's going to be a pain and a half taking my PC to bits to extract the |
| 17 |
> processor, but I suppose it's got to be done. ;-( |
| 18 |
> |
| 19 |
|
| 20 |
Does anybody know if AMD is doing advance returns of the defective |
| 21 |
CPUs (ie they send the replacement CPU before receiving the original |
| 22 |
back, typically with a hold on a credit card)? Mine also fails the |
| 23 |
gcc test, though I don't think I've encountered the issue yet in |
| 24 |
routine use (I suspect it is only a matter of time and it is only a |
| 25 |
week old). I really don't want to be without a CPU for weeks on end. |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Rich |
Archives