cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

bradc
Adept III

Re: gcc segmentation faults on Ryzen / Linux

oberbutze wrote:

Once you have received your replacement CPU, please update your motherboard BIOS to the latest version with AGESA 1.0.0.6b after installing the CPU.

I wonder why they'd ask for that. Nobody has been able to come up with what has been fixed in the microcode update.

0 Likes
bigdaveyl
Journeyman III

Re: gcc segmentation faults on Ryzen / Linux

I had a 1708 cpu, had the issues as I was running Gentoo.  I got the cpu from Newegg about 1 month ago.  Decided to RMA it through AMD based on the info on this thread as I didn't want to take a chance with Newegg sending me another one from before week 25. 

I sent back my old one and it looks like they overnighted me a new one - they required a signature and I am at work so I can see if I can pick it up after.

0 Likes
oberbutze
Adept II

Re: gcc segmentation faults on Ryzen / Linux

I hope FedEx is kidding me. They couldn't deliver the package today to AMD Netherlands and the new estimated delivery date is 28.9...

0 Likes
debaser
Adept I

Re: gcc segmentation faults on Ryzen / Linux

Well, AMD answered at last, they are sending my replacement tomorrow. I don't know if that means they are sending it to the Netherlands first, where I sent my defective unit, and then they'd send it to me.

0 Likes
scorpio810
Adept III

Re: gcc segmentation faults on Ryzen / Linux

debaser​ In my case, I searched for the Fedex tracking number send me by support and I saw big package (4.45 kgs) delivery on Thursday 9/07/2017 in ROZENBURG (NH), my RMAed CPU arrived at home (France) from ROZENBURG 3 days after.

Just wait.

Re: gcc segmentation faults on Ryzen / Linux

4.5kg? How many chips did you send

0 Likes
scorpio810
Adept III

Re: gcc segmentation faults on Ryzen / Linux

Just one CPU ..

Isn't for me uhuhu, but for AMD EU warehouse.

0 Likes
alonzotg
Adept II

Re: gcc segmentation faults on Ryzen / Linux

I had sent in my RMA last week. According to FedEx it was delivered on Monday so therefore, today, I was sent a notification that they were closing out the RMA ticket because I had neglected to send them a copy of the tracking number.

Look, I have a full time job contemplating how miserable and pathetic my life is because I don't have a full time job and can't get a full time job, again because I don't have a full time job... So yeah, I missed the line where they mentioned they wanted proof of shipment. Now that strikes me as a rather optional step because once they have the GD box in their grubby little hands I don't have to prove a single blessed, bloody, or GD thing to them... How they have had the box in their hands for three days and not sent out a replacement, instead notifying me that they're discontinuing the RMA because I had done nothing is beyond me...

They owe me a working 1800X!!!!!!

0 Likes
bsp2020
Elite

Re: gcc segmentation faults on Ryzen / Linux

I just got my replacement CPU 1800X and I ran kill-ryzen script and it still fails. The failure message looks different. Is this still segfault problem or am I dealing with some other problem? Please help...

'''

Using 16 parallel processes

[KERN] -- Logs begin at Wed 2017-09-20 20:38:52 PDT. --

[KERN] Sep 20 20:38:52 FijiX2 kernel:  sdb: sdb1

[KERN] Sep 20 20:38:52 FijiX2 kernel: input: CHICONY HP Basic USB Keyboard as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-6/1-6:1.0/0003:03F0:0024.0003/input/input15

[KERN] Sep 20 20:38:52 FijiX2 kernel: sd 10:0:0:0: [sdb] Attached SCSI removable disk

[KERN] Sep 20 20:38:53 FijiX2 kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready

[KERN] Sep 20 20:38:53 FijiX2 kernel: hid-generic 0003:03F0:0024.0003: input,hidraw2: USB HID v1.10 Keyboard [CHICONY HP Basic USB Keyboard] on usb-0000:03:00.0-6/input0

[KERN] Sep 20 20:38:53 FijiX2 kernel: r8169 0000:05:00.0 enp5s0: link down

[KERN] Sep 20 20:38:53 FijiX2 kernel: r8169 0000:05:00.0 enp5s0: link down

[KERN] Sep 20 20:38:53 FijiX2 kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready

[KERN] Sep 20 20:38:55 FijiX2 kernel: r8169 0000:05:00.0 enp5s0: link up

[KERN] Sep 20 20:38:55 FijiX2 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready

[loop-0] Wed Sep 20 20:43:39 PDT 2017 start 0

[loop-1] Wed Sep 20 20:43:40 PDT 2017 start 0

[loop-2] Wed Sep 20 20:43:41 PDT 2017 start 0

[loop-3] Wed Sep 20 20:43:42 PDT 2017 start 0

[loop-4] Wed Sep 20 20:43:43 PDT 2017 start 0

[loop-5] Wed Sep 20 20:43:44 PDT 2017 start 0

[loop-6] Wed Sep 20 20:43:45 PDT 2017 start 0

[loop-7] Wed Sep 20 20:43:46 PDT 2017 start 0

[loop-8] Wed Sep 20 20:43:47 PDT 2017 start 0

[loop-9] Wed Sep 20 20:43:48 PDT 2017 start 0

[loop-10] Wed Sep 20 20:43:49 PDT 2017 start 0

[loop-11] Wed Sep 20 20:43:50 PDT 2017 start 0

[loop-12] Wed Sep 20 20:43:51 PDT 2017 start 0

[loop-13] Wed Sep 20 20:43:52 PDT 2017 start 0

[loop-14] Wed Sep 20 20:43:53 PDT 2017 start 0

[loop-15] Wed Sep 20 20:43:54 PDT 2017 start 0

[KERN] Sep 20 20:54:14 FijiX2 kernel: [drm] Atomic commit: RESET. crtc id 0:[ffff8fc94114a000]

[KERN] Sep 20 20:54:14 FijiX2 kernel: [drm] dc_commit_streams: 0 streams

[KERN] Sep 20 20:54:14 FijiX2 kernel: [drm] Atomic commit: RESET. crtc id 0:[ffff8fc94114a000]

[loop-2] Wed Sep 20 20:59:50 PDT 2017 build failed

[loop-1] Wed Sep 20 20:59:50 PDT 2017 build failed

[loop-5] Wed Sep 20 20:59:50 PDT 2017 build failed

[loop-0] Wed Sep 20 20:59:50 PDT 2017 build failed

[loop-4] Wed Sep 20 20:59:50 PDT 2017 build failed

[loop-6] Wed Sep 20 20:59:50 PDT 2017 build failed

[loop-3] Wed Sep 20 20:59:50 PDT 2017 build failed

[loop-1] TIME TO FAIL: 971 s

[loop-5] TIME TO FAIL: 971 s

[loop-6] TIME TO FAIL: 971 s

[loop-4] TIME TO FAIL: 971 s

[loop-2] TIME TO FAIL: 971 s

[loop-3] TIME TO FAIL: 971 s

[loop-0] TIME TO FAIL: 971 s

[loop-15] Wed Sep 20 21:00:00 PDT 2017 build failed

[loop-15] TIME TO FAIL: 981 s

[loop-7] Wed Sep 20 21:00:00 PDT 2017 build failed

[loop-7] TIME TO FAIL: 981 s

[loop-14] Wed Sep 20 21:00:00 PDT 2017 build failed

[loop-14] TIME TO FAIL: 981 s

[loop-11] Wed Sep 20 21:00:02 PDT 2017 build failed

[loop-11] TIME TO FAIL: 983 s

[loop-13] Wed Sep 20 21:00:02 PDT 2017 build failed

[loop-13] TIME TO FAIL: 983 s

[loop-8] Wed Sep 20 21:02:15 PDT 2017 build failed

[loop-8] TIME TO FAIL: 1116 s

[loop-10] Wed Sep 20 21:02:15 PDT 2017 build failed

[loop-10] TIME TO FAIL: 1116 s

[loop-12] Wed Sep 20 21:02:15 PDT 2017 build failed

[loop-12] TIME TO FAIL: 1116 s

[loop-9] Wed Sep 20 21:02:15 PDT 2017 build failed

[loop-9] TIME TO FAIL: 1116 s

[KERN] Sep 20 21:15:30 FijiX2 kernel: [drm] Atomic commit: SET crtc id 0: [ffff8fc94114a000]

[KERN] Sep 20 21:15:30 FijiX2 kernel: [drm] dc_commit_streams: 1 streams

[KERN] Sep 20 21:15:30 FijiX2 kernel: [drm] core_stream 0x2e7d1000: src: 0, 0, 1920, 1080; dst: 0, 0, 1920, 1080, colorSpace:1

[KERN] Sep 20 21:15:30 FijiX2 kernel: [drm]         pix_clk_khz: 148500, h_total: 2200, v_total: 1125, pixelencoder:1, displaycolorDepth:2

[KERN] Sep 20 21:15:30 FijiX2 kernel: [drm]         sink name: SMB2330, serial: 1347760691

[KERN] Sep 20 21:15:30 FijiX2 kernel: [drm]         link: 0

[KERN] Sep 20 21:15:30 FijiX2 kernel: [drm] dce_get_required_clocks_state: clocks unsupported

[KERN] Sep 20 21:15:30 FijiX2 kernel: [drm] [Mode]        [DVI][ConnIdx:0] {1920x1080, 2200x1125@148500Khz}^

'''

0 Likes
bsp2020
Elite

Re: gcc segmentation faults on Ryzen / Linux

It looks like I'm running out of disk space. I cleaned up all the temporary files and tried again. But kill-ryzen script fill up 20GB of free space in about 40 minutes. How are you running the script for days when it generates so much files?

0 Likes