1 |
Hello, Rich. |
2 |
|
3 |
On Sun, Aug 27, 2017 at 08:23:48 -0400, Rich Freeman wrote: |
4 |
> On Sun, Aug 27, 2017 at 7:03 AM, Alan Mackenzie <acm@×××.de> wrote: |
5 |
|
6 |
> > On Fri, Aug 25, 2017 at 15:46:31 +1000, Adam Carter wrote: |
7 |
> >> FYI, you should be able to return your CPU for a fixed one now. |
8 |
|
9 |
> >> http://www.phoronix.com/scan.php?page=article&item=new-ryzen-fixed&num=1 |
10 |
|
11 |
> > Thanks for that. I wasn't actually aware anybody else was suffering |
12 |
> > from this. |
13 |
|
14 |
> > I've had quite a few build failures with segmentation faults, always (as |
15 |
> > far as I can tell) while building .lo files. Initially, I suspected the |
16 |
> > RAM, but memtest presented a clean bill of health after several hours |
17 |
> > testing. |
18 |
|
19 |
> > It's going to be a pain and a half taking my PC to bits to extract the |
20 |
> > processor, but I suppose it's got to be done. ;-( |
21 |
|
22 |
|
23 |
> Does anybody know if AMD is doing advance returns of the defective |
24 |
> CPUs (ie they send the replacement CPU before receiving the original |
25 |
> back, typically with a hold on a credit card)? Mine also fails the |
26 |
> gcc test, though I don't think I've encountered the issue yet in |
27 |
> routine use (I suspect it is only a matter of time and it is only a |
28 |
> week old). I really don't want to be without a CPU for weeks on end. |
29 |
|
30 |
I bought mine from a shop (along with all the other components) in |
31 |
person, and paid in cash. Everything, bar the case, fitted into my |
32 |
rucksack. That case was getting darned heavy by the time I'd walked home |
33 |
with it. ;-( |
34 |
|
35 |
Presumable the -j17 setting has something to do with those seg faults. |
36 |
|
37 |
I'm hoping the shop will be able to get me a replacement before I have to |
38 |
return the defective processor to them. We'll see. |
39 |
|
40 |
> -- |
41 |
> Rich |
42 |
|
43 |
-- |
44 |
Alan Mackenzie (Nuremberg, Germany). |