Calling all Linux Ryzen owners! Submit your CPU numbers (uCode/ProdDate)

Hardware Hub CPU
, ,
16

The kill-ryzen script just tests for instability. There are also some outlined general steps in this other thread. If you want, you can have the Ryzen tech support walk you through double-checking everything (cooling/voltages/prime95/jdec memory/vql memory). In my case (pun intended), there were some intermittent i/o errors which were fixed with a different sata cable + port.

17

Recently I RMAd my Ryzen 1700 for segfault issues. After a long wait I finally received my replacement, a week 33 chip.

Using kill-ryzen.sh on ubuntu 16.0.4.3 with latest AEGESA, stock RAM speeds, memtest validated, had the following…

The good:

  • No segfault
  • No MCE reboot or system crashes

The bad?

  • “interrupt took too long…” message followed by failed builds.

I’m not familiar with this message. Does this suggest another bad chip or am I facing a kernel issue with new architecture blues?

Attached is a screenshot.

hmmm…

Screenshot_2017-09-22_07-42-37
Screenshot_2017-09-22_07-42-37.png1920x1080 340 KB

18

kernel version?
uname -a
EDIT: Ok I saw there it’s 4.10.0.35. Could you perhaps try to upgrade to a recent 4.12 kernel and see if things improve?

Aside from that what are the mainboard and other system details?

Also attach dmesg output when it occurs.

PS: I suspect you might simply be hitting the limit of RAM.

19

Regarding RAM, I agree.

FWIW I ran this test so far for 2 hours without issues. This segfault test doesn’t use up nearly as much RAM. It seems to be a valid test. AMD forum users report typical failure from 10-20min.


./run.sh 16 1000000000

Linux tiny-ryzen 4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

ASRock Fatal1ty x370 ITX

I’ll certainly look into an upgraded kernel.

Your help and ideas is much appreciated!

20

Check your build log

cat /mnt/ramdisk/workdir/buildloop.d/loop-0/build.log | grep -i error

I bet all the logs show the same. Error

./md-unwind-support.h:65:47: error: dereferencing pointer to incomplete type 'struct ucontext'

The kill-ryzen test is broken when attempting to build with newer gcc like 7.2.0 and the associated system dependencies.
You can manually patch the build script to download and build gcc 7.2.0 instead.

21

RMA replacement arrived in a questionable looking shipping box with questionable packaging . Inside was a sealed retail box with the following:

small
IMG_0034.small.jpg601x745 115 KB

UA 1733SUS

So post week 25, fabricated in: Suzhou, U, Saratoga
What is U again?

This one should be fine unless it was damaged during shipping. Will test using GCC for the next 5 days or so.

22

Assembled in SuzhoU diffused in Saratoga is the SUS code.

I got mine in a Large FedEx box. 1728SUS.
Seems like a lot of the replacement chips are SUS.

PS: The serial number is encoded in the Graphic Code, but its too low resolution to decode easily.

If yours didn’t have the small circular seal sticker on the bottom it’s one that was fished from the production line.

Mine funnily enough was shipped from Markham, Ontario Canada from ATI Technologies ULC

1 Like
23

I totally did not know that but makes sense now that I think about it. QC codes are surprisingly hardy so it would probably decode properly after using an upscaler.

24

I bough the last week a Ryzen 1700 in pccomponentes (Spain)
with Ubuntu 17.10 Beta 2
i compile Python 3.6 (the kill-ryzen dosent work (fail mount ramdisk) )
12 times whithout segmentation fault (only other warnings) problem using this:

first do ./configure

#!/bin/bash

export LANG=C

if [ $# -ge 1 ] ; then
  CONCURRENCY=$1
else
  CONCURRENCY=16
fi

for ((i=0;12;i++)) ; do
 echo 'Start test $i'
  if make -j$CONCURRENCY >/dev/null 2>>log.txt ; then
    echo "$i: $(date): OK" >>log.txt
  else
    echo "$i: $(date): NG" >>log.txt
  fi
  dmesg >dmesg.txt
  make clean >/dev/null 2>>log.txt
done

My CPU is 1717SUS

DMI: Gigabyte Technology Co., Ltd. AB350M-Gaming 3/AB350M-Gaming 3-CF, BIOS F7a 09/15/2017
model		: 1
model name	: AMD Ryzen 7 1700 Eight-Core Processor
stepping	: 1
microcode	: 0x8001129
1 Like
25

Dear,

I can replicate this problem in Windows ???
If not, emulating Linux can I execute replicate the problem, if my CPU is a problematic ???

My CPU is UA 1709PGT.
Microcode: 8001129

And I have a bad CPU apparently.
error_ryzen

26

Just use a live distro from USB. Manjaro XFCE runs perfectly fine these days and I just needed to build blender to trigger the segfault. Also ubuntu 17.10 is out so that might be another option for a live stick.

27

Now we can see the error more clearly.
I’m starting my RMA. Waiting for their respects.
I wanted to know who did it, if it was necessary to send the CPU before receiving the new copy. I can not stop.

error_ryzen_02

28

In my case, they said they would send the replacement after verifying the defective CPU was shipped, but it took several weeks before I got mine back (to be fair this about the time Irma happened, and they shipped it from Canada. The place they had me send the defective CPU to was in Miami).

Their customer service seems pretty decent, I would at least ask if they will do an advanced RMA.

Also, in your first email, to speed up the process, go ahead and include this info (it may take a day or two for them to reply in my experience):

  • Processor model
  • Make and model of motherboard
  • Motherboard BIOS version
  • Make and model of RAM
  • Make and model of power supply
  • CPU VCORE, SOC and RAM voltages (screenshot/picture of BIOS settings preferred)
  • Picture of the interior of the case, to rule out heating issues
3 Likes
29

This is the correct advice. Thanks for posting that for others.

In my case it was also shipped out of Canada at the same time as Irma was happening.
On the box the source address read “ATi Technologies LLC” of all things :smile_cat:

3 Likes
30

Just as a heads up… Amazon is still selling impacted CPU’s. Ordered an 1800x same day shipping (couldn’t resist the new $350 price, received an 1800X UA1721PGT with segfault issues…

3 Likes
31

At least you can return to amazon relatively easy.
Sucks tho.

1 Like
32

it probably was honestly stock that got pushed to the back

33

A little late here but here is my microcode

model : 1
model name : AMD Ryzen 7 1700 Eight-Core Processor
stepping : 1
microcode : 0x8001129
EDIT:
oh ya and
dmesg | grep -e 'DMI.*BIOS’
gave me this.
[ 0.000000] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P3.10 08/25/2017

35

Hmmn, now that I think about it. When I got my ryzen 1700 I was rendering unreal editor 4. It would crash and shut down the editor at random times… It did it in my windows boot a couple times… I actually used that as a test frame to set, voltage to clock speed. I thought I was clocking too much. And now I wonder.

36

That’s a difficult to debug & noisy test case.
Because Unreal ED can be buggy at the best of times and introduces too many variable that one can’t control for.

1 Like