Announcement

Collapse
No announcement yet.

Ryzen-Test & Stress-Run Make It Easy To Cause Segmentation Faults On Zen CPUs

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • caligula
    replied
    I can also confirm I get random segfaults on a 1700X system which is mostly used for compiling packages with gcc. Let's see how it will go with this new test.

    Leave a comment:


  • Qaridarium
    replied
    Originally posted by bridgman View Post
    just that I would make sure the info and concerns were getting to the right people.
    the ryzen GCC compiling segfault bug in the closed source microcode is the best example why open-source from top to bottom matters.
    and on an opensource system from top to botton this bug would not happen...
    it just monopoles the bug-fix to one company otherwise if it was open-source many companies can compete to fix the bug
    in the end it is just magic security features so in the end we all can be "save" ,... and "save" in this meaning means that we are save to say that we can not and we should not fix bugs instead we need to obey our masters and hope for an update.

    Leave a comment:


  • Silverthorn
    replied
    I got curious and tried ryzen-test/kill-ryzen.sh on my system and it took almost 40 minutes until I got the segmentation fault. Hopefully this behaviour gets fixed and while doing so also fixed other more rare crashes and stability issues.

    Leave a comment:


  • c2h5oh
    replied
    Originally posted by schmidtbag View Post
    My motherboard's BIOS keeps my RAM voltage at 1.2v, even though it's supposed to be 1.3v. This alone makes the RAM very unstable.
    Most DDR4 faster than 2333 requires 1.35V

    Leave a comment:


  • bridgman
    replied
    Originally posted by nightmarex View Post
    (John there's threads you promised to drop an update in and haven't please do so)
    Is "John" in this case me ? If so, I don't think I promised (or even "said") that I would provide an update, just that I would make sure the info and concerns were getting to the right people. I did that, and posted back to confirm it.

    If that isn't how you read things could you try to point me to the threads ? Thanks...

    Leave a comment:


  • macchky
    replied
    Originally posted by cde1 View Post
    This is anecdotal evidence but I underclocked my A10-7870K to 0.2V below normal and while everything seemed fine in Windows, when in Linux the system had L1 parity errors that were corrected most of the time. At -0.1V the problem did not appear, so I'm not surprised a problem with voltages could lead to what people see with Ryzen.

    Also in another thread on Phoronix I explained how to underclock the RX 470/480 by patching the amdgpu-pro kernel source. After a few months it appears the voltage I chose (820mV) is too low as it sometimes leads to page faults in the GPU. When that happens only a reboot helps.
    This thread is about RYZEN CPU not APU mate

    Leave a comment:


  • cde1
    replied
    Originally posted by nightmarex View Post

    This problem happens on intel chips as well, the "kill_ryzen" script was ridiculed for throwing segfaults on every cpu it was tested on.
    Incorrect, kill_ryzen would only lead to segfaults on Ivy bridge and this is a know hardware defect that newer generations don't have (or is fixed in microcode already).

    Leave a comment:


  • cde1
    replied
    This is anecdotal evidence but I underclocked my A10-7870K to 0.2V below normal and while everything seemed fine in Windows, when in Linux the system had L1 parity errors that were corrected most of the time. At -0.1V the problem did not appear, so I'm not surprised a problem with voltages could lead to what people see with Ryzen.

    Also in another thread on Phoronix I explained how to underclock the RX 470/480 by patching the amdgpu-pro kernel source. After a few months it appears the voltage I chose (820mV) is too low as it sometimes leads to page faults in the GPU. When that happens only a reboot helps.

    Leave a comment:


  • macchky
    replied
    This probrem may be caused by 0x40 address shifts errata?

    Investigated by japanese user.

    Ryzenにまつわる2つの問題 - 覚書 http://satoru-takeuchi.hatenablog.co...7/04/24/135914
    日記 (2017 年 6 月下旬) http://www.e-hdk.com/diary/d201706c.html#20-2

    Leave a comment:


  • GruenSein
    replied
    Originally posted by Qaridarium View Post

    and they still try to claim that we do not need open-source hardware ISA and opensource firmware and opensource bios...
    and then closed source microcode cause massiv problems and they still downplay the role of opensource sollutions.
    Can we post-pone this debate for now? This has been discussed so many times concerning so many types of hardware and in this particular case people are actually reporting ways to circumvent or even fix (if it proves permanent) the problem. Please don't drift off into another political debate...

    Leave a comment:

Working...
X