Announcement

Collapse
No announcement yet.

AMD Confirms Linux Performance Marginality Problem Affecting Some, Doesn't Affect Epyc / TR

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

  • I was getting segfaults with the kill-ryzen chip within 3 minutes. But with Vsoc set to 1.05V and Vcore offset set to +0.05V, I no longer get them (I don't know whether upping Vsoc is important or not). These are the only changes I made to the most recent BIOS. Which is interesting considering everyone ignored the people saying to up your Vcore in the last few threads. If I had just tried that I would have had the problem solved. But no, people said that was stupid so I didn't try it (so who's stupid, really?).

    At any rate, it still isn't really fair to expect a user to manually adjust their voltages in order to get a stable system, so I will push for an RMA. For me power dissipation is important, so I don't want to up the voltages if I don't need to. Furthermore, if I can lower power draw by undervolting, that might also help.

    Comment


    • AGESA 1.0.0.6b apparently resolves this issue!

      Comment


      • Well I do hope that's true, because I'm pulling the trigger on a R7 1700 next month.

        Comment


        • phoronix-test-suite run build-gcc might be having failed test runs because of this. I had 1-2 successful runs, then a failed one, then another successful one. Turning the opcode cache off gets rid of the problem or makes it disappear for hours. The performance penalty seems to be negligible in pts/build-kernel runs for me. The problem does still happen at higher Vcore at 1.25 and for RAM speeds from 2133-2800 with opcode cache on. I can't guarantee a good RMA with Newegg, so dealing with AMD customer care now. Hopefully this is a Global Foundry and/or AMD hiccup and really fixed in newer versions. Seems like the opcode cache wouldn't be shared between cores or chips...

          edit: Disabling the opcode cache would be a "performance maginality" in the grand scheme of things. That being said, AMD should have recognized the problem earlier and been more proactive in actually fixing the problem by replacing the processors or giving some sort of a discount.
          Last edited by audi100quattro; 09-15-2017, 04:57 AM.

          Comment


          • "agesa 1.0.0.6" bios f6

            [KERN] -- Logs begin at Sat 2017-09-16 23:06:35 UYT. --
            [KERN] Sep 16 23:06:43 amdryzen-AX370-Gaming-5 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-I-0
            [KERN] Sep 16 23:06:45 amdryzen-AX370-Gaming-5 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-I-0
            [KERN] Sep 16 23:06:45 amdryzen-AX370-Gaming-5 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-I-0
            [KERN] Sep 16 23:06:45 amdryzen-AX370-Gaming-5 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-I-0
            [KERN] Sep 16 23:06:45 amdryzen-AX370-Gaming-5 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-I-0
            [KERN] Sep 16 23:06:45 amdryzen-AX370-Gaming-5 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-I-0
            [KERN] Sep 16 23:06:46 amdryzen-AX370-Gaming-5 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DVI-I-0
            [KERN] Sep 16 23:07:37 amdryzen-AX370-Gaming-5 kernel: zram: Added device: zram0
            [KERN] Sep 16 23:07:37 amdryzen-AX370-Gaming-5 kernel: zram0: detected capacity change from 0 to 68719476736
            [KERN] Sep 16 23:07:37 amdryzen-AX370-Gaming-5 kernel: EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: discard
            _________________________________________________

            [loop-10] Sat Sep 16 23:11:16 UYT 2017 build failed
            [loop-10] TIME TO FAIL: 132 s
            [KERN] Sep 16 23:11:16 amdryzen-AX370-Gaming-5 kernel: bash[23348]: segfault at 91afc8 ip 000000000091afc8 sp 00007fff241e2460 error 15

            _________________________________________________

            _________________________________________________

            Agesa 1.0.0.6b -> bios f9 -> test 1

            [loop-9] TIME TO FAIL: 118 s
            [loop-0] TIME TO FAIL: 118 s
            [KERN] Sep 17 11:28:56 amdryzen-AX370-Gaming-5 kernel: bash[29611]: segfault at 64 ip 00000000004b88f0 sp 00007ffe1250ccb8 error 4 in bash[400000+f4000]
            [KERN] Sep 17 11:28:56 amdryzen-AX370-Gaming-5 kernel: bash[29506]: segfault at 64 ip 00000000004b88f0 sp 00007ffddc8ec938 error 4 in bash[400000+f4000]
            ___________

            test 2 -> emulation 60/64

            [loop-9] Sun Sep 17 11:46:24 UYT 2017 build failed
            [loop-9] TIME TO FAIL: 118 s
            [KERN] Sep 17 11:46:24 amdryzen-AX370-Gaming-5 kernel: traps: bash[27753] trap invalid opcode ip:48db90 sp:7ffc66b917c8 error:0 in bash[400000+f4000]
            -------------------- Test 3-> opcache control "disabled" It works better!

            [loop-13] Sun Sep 17 12:44:14 UYT 2017 start 0
            [loop-14] Sun Sep 17 12:44:15 UYT 2017 start 0
            [loop-15] Sun Sep 17 12:44:16 UYT 2017 start 0
            [KERN] Sep 17 13:14:36 amdryzen-AX370-Gaming-5 kernel: perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79750

            I don't understand the mistake at the end.
            Ryzen 1700 , ax370 gigabyte gaming 5 , 16 gb ram 2400mhz, gtx 970 sc nvidia, 1 ssd kingstone v300 + hdd 500gb. Linux mint 18.2 , gcc 7.1.0,kernel 4.13.2-041302-generi

            Comment

            Working...
            X