Quote:
Originariamente inviato da papugo1980
Credo intenda Rma dallo store e non da Amd
|
L'utente che ho linkato dal forum AMD aveva aperto una procedura di RMA con AMD. Riporta segfault, ma solo aumentando la frequenza della memoria usando il profilo XMP. Per questo ero curioso di sapere se effettuando overclock in tal senso (o diminuendo il vSoC, che pare sia correlato alla stabilità di memoria ed affini) potessero iniziare ad apparire segfault con le solite modalità, anche con processori che a default non mostrano nulla:
https://community.amd.com/message/28...822644#2822644 (#1347)
Quote:
After 3 weeks and half my replacement 1700X arrived today. I can't blame the delay on AMD. The problem was Brazilian customs.
It is also a 1725SUS (diffused in USA and made in China). It was certainly pre-tested as there are some small dents in the corners (it looks like they attached the cooler too tight). I hope they did not damage the CPU in any sense. I have just put the CPU back on my computer and started the kill-ryzen.sh test. I will report back in 48 hours.
|
https://community.amd.com/message/28...823637#2823637 (#1484)
Quote:
Bad news from my front. I have an RMAed CPU of week 25. It sustained 3 days of kill-ryzen.sh using BIOS defaults. After that I updated my BIOS and changed my memory profile to use XMP 2 (2400 instead of 2100 from Bios default).* Unfortunately, under this conditions I got a new failure in one of the loops:
*
-----------------
/mnt/ramdisk/workdir/gcc-7.1.0/gcc/config/i386/i386.c: In function 'int standard_sse_constant_p(rtx, machine_mode)':
/mnt/ramdisk/workdir/gcc-7.1.0/gcc/config/i386/i386.c:11699:8: internal compiler error: Segmentation fault
** mode = GET_MODE (x);
0x11ac5ec crash_signal
*** /mnt/ramdisk/workdir/gcc-7.1.0/gcc/toplev.c:337
0x104058c create_output_operand
*** /mnt/ramdisk/workdir/gcc-7.1.0/gcc/optabs.h:94
-----------------
*
I will now revert back memory to BIOS default. I think I read somewhere that Ryzen only officially supports 2100Hz when dealing with 64Gb.
*
I have to admit that I am really tired of this. It will be hard to really trust this CPU after so many problems.
|
.
Quote:
Originariamente inviato da papugo1980
@s12a il test è arrivato a 50 minuti e ancora va avanti
Al minuto 32 è apparso
Ubuntu kernel: perf: interrupt took too long (2501>2500), Lowering kerneL.perf_event nax sample rate to 79750
|
Questo è normale e non indica problemi con il processore.