Announcement

Collapse
No announcement yet.

Some FreeBSD Users Are Still Running Into Random Lock-Ups With Ryzen

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

  • #11
    Originally posted by soulsource View Post
    ... disabling C6 states via the firmware settings made the computer run rock solid. Not a single freeze since I changed this four months ago.
    Bug probably just have something to do with XFR, since disabling C6 also disables XFR that additional turbo speed... that is how this sounds to me.

    Are these non-X Ryzens same affected as these with X?
    Last edited by dungeon; 01-21-2018, 03:35 PM.

    Comment


    • #12
      Originally posted by Hi-Angel View Post
      The bug by far is not the worst. It's just a bug, that's it. It just happens, irrelevant to OS or hw. The worst is that AMD doesn't write about it, it looks like nobody is working, nobody care. It's a MAJOR problem on AMD side, and AMD does nothing about it.

      You know, you can do lots of good stuff, but then single fault may beat everything you did good. It is this bug for AMD.
      Yep , AMD should step up.

      When there is a hardware related issue but hardware vendor didn't care about it , it turns into a pretty annoying issue.

      Comment


      • #13
        Originally posted by Leopard View Post

        Yep , AMD should step up.

        When there is a hardware related issue but hardware vendor didn't care about it , it turns into a pretty annoying issue.
        I am sure if someone can find a way to replicate the issue, they will be able to fix it.
        This also don't happen on Windows AFAIK, so, it is a linux bug of some type.

        If you can't replicate it since it is too random, then it is a guessing game, and not much progress can be done.

        So, if you have this issue, then try to find a way to replicate it, then report the bugs.

        Comment


        • #14
          Whenever I plan to buy a Ryzen system, something comes up. First the segfault bug, then Meltdown/Spectre (at least AMD is invulnerable to the former), and now this.

          Holy fuck, AMD, fix your goddamn platform. I want a new PC.

          (Although, to be fair, this seems like an unfortunate combination of crap BIOS + crap motherboard and settings, or a power delivery issue.)

          Is Threadripper affected? It's evidently overkill, but at least it's significantly cheaper than Intel's space heater offerings in HEDT, and I would finally have MOAR COARS (and my e-peen would be significantly enlarged).

          For the record, enabling C6 on Kaveri causes random lockups when idle as well. Broken since forever (as is BAPM).

          Comment


          • #15
            Originally posted by vortex View Post

            I am sure if someone can find a way to replicate the issue, they will be able to fix it.
            This also don't happen on Windows AFAIK, so, it is a linux bug of some type.

            If you can't replicate it since it is too random, then it is a guessing game, and not much progress can be done.

            So, if you have this issue, then try to find a way to replicate it, then report the bugs.
            I have an Intel Cpu , i7 7700 HQ.

            I experienced a bios acpi related issue on this very Asus laptop but since it is not Windows related , they didn't care.

            Also when you look that mailing list , that cannot be considered as "too random ". Many people suffering from same issue , exact workarounds are working.
            Last edited by Leopard; 01-21-2018, 04:13 PM.

            Comment


            • #16
              I get random lockups when writing stuff with gvim which is very annoying when you happen to be computer science major whose favourite editor is (g)vim... I upgraded to the latest bios (F10 for my Gigabyte GA-AB350-Gaming motherboard; for some reason bios versions newer than F4 have issues with bcache setups) which didn't fix the lockups. Now I've disabled C-state power saving (I don't remember the exact setting) and it seems to be stable. I'm running Fedora 27 with stock kernels.

              The CPU has also the segfault bug when using many threads, but I can't yet replace it because I really need that cpu for now. Maybe in a month or two I can RMA it.
              Last edited by Tomin; 01-21-2018, 04:03 PM. Reason: forgot to mention my distribution

              Comment


              • #17
                Yes, Linux is certainly not free of this issue or any OS for that matter because this is a hardware issue. I half joked that you wouldn't see it on Windows because it's never idle for long enough. Turns out AMD have privately said exactly the same thing. So yes, they are aware of the issue but it doesn't seem like they're going to admit it publicly. They told me directly that it would be fixed in a BIOS update but I'm not holding my breath. For now, I am using the CONFIG_RCU_NOCB_CPU workaround (which I discovered, you're welcome ) and I have seen maybe two freezes in the months since. I can't swear they weren't caused by something else but I don't believe the workaround is 100% effective.

                Comment


                • #18
                  Originally posted by vortex View Post

                  I am sure if someone can find a way to replicate the issue, they will be able to fix it.
                  This also don't happen on Windows AFAIK, so, it is a linux bug of some type.
                  Or hardware issue which windows doesn't trigger, because it doesn't care about performance.

                  Comment


                  • #19
                    Originally posted by kravemir View Post
                    Makes me wonder, which cpu would ‚ÄčI pick today... Intel or AMD... More vulnerable or little (but annoying) unstable...
                    Just because Intel has known vulnerabilities, doesn't mean that AMD is any more secure. The just have advantage of being the little guy that nobody cares about.
                    I suspect that Intel validation/verification teams are much better than AMDs, especially after long time of AMD being in red numbers.

                    Comment


                    • #20
                      Originally posted by tpruzina View Post

                      Just because Intel has known vulnerabilities, doesn't mean that AMD is any more secure. The just have advantage of being the little guy that nobody cares about.
                      I suspect that Intel validation/verification teams are much better than AMDs, especially after long time of AMD being in red numbers.
                      Nothing surprising really.

                      Linux community is generally having their pitchforks ready for Intel and Nvidia hate at any negative news, but they gone silent when an AMD problem occurs.

                      Comment

                      Working...
                      X