Announcement

Collapse
No announcement yet.

New Ryzen Is Running Solid Under Linux, No Compiler Segmentation Fault Issue

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

  • New Ryzen Is Running Solid Under Linux, No Compiler Segmentation Fault Issue

    Phoronix: New Ryzen Is Running Solid Under Linux, No Compiler Segmentation Fault Issue

    As a quick update to the AMD Linux "Performance Marginality Problem" affecting some early Ryzen processors under heavy load, today I received a new Ryzen 7 processor and indeed it's been running strong now for the past few hours under demanding load and has yet to hit the compiler segumentation fault bug.

    http://www.phoronix.com/vr.php?view=25097

  • #2
    So does this mean that it takes a silicon fix to get around the bug or will it be possible to fix via microcode?

    Comment


    • #3
      Originally posted by chuckula View Post
      So does this mean that it takes a silicon fix to get around the bug or will it be possible to fix via microcode?
      I haven't been told anything from AMD about the possibility of a microcode fix. If affected by the issue they recommend contacting AMD Customer Care, which at least for now sounds like an RMA.
      Michael Larabel
      http://www.michaellarabel.com/

      Comment


      • #4
        For those us of who haven't upgraded yet. How do we buy a known good Ryzen from week 30 or newer?

        Comment


        • #5
          Originally posted by BillBroadley View Post
          For those us of who haven't upgraded yet. How do we buy a known good Ryzen from week 30 or newer?
          I don't think there is a way, but if you are running workloads that are affected contact AMD and they will swap your CPU with a fixed one.

          EDIT: If you are purchasing it in person you can look at the CPU thought the plastic cover on the side of the box and read the number written on it.
          Last edited by Spazturtle; 08-24-2017, 08:51 PM.

          Comment


          • #6
            Typo:

            Originally posted by phoronix View Post
            and has yet to hit the compiler segumentation fault bug.

            Comment


            • #7
              There is "1705" written under the picture of "1730" so things doesn't line up.

              Comment


              • #8
                Originally posted by chuckula View Post
                So does this mean that it takes a silicon fix to get around the bug or will it be possible to fix via microcode?
                I doubt that's CPU bug at all, more likely manufacturing problem, it's the same stepping.

                Comment


                • #9
                  Originally posted by Nille_kungen View Post
                  There is "1705" written under the picture of "1730" so things doesn't line up.
                  The other picture is underneath.
                  Michael Larabel
                  http://www.michaellarabel.com/

                  Comment


                  • #10
                    Originally posted by leipero View Post

                    I doubt that's CPU bug at all, more likely manufacturing problem, it's the same stepping.
                    Good observation!

                    Comment

                    Working...
                    X