5/27/2023 0 Comments Cpu stress test for ryzen masterAs soon as one test finishes, another is fired up. Using PTS_CONCURRENT_TEST_RUNS=4 TOTAL_LOOP_TIME=60 phoronix-test-suite stress-run build-linux-kernel build-php build-apache pgbench apache redis will have the Phoronix Test Suite continually running four different benchmarks simultaneously for a period of 60 minutes. Rather than benchmarking for performance, stress-run allows executing multiple test profiles in parallel for fully loading the system with whatever workloads you would like. The stress-run command within the Phoronix Test Suite has been used by enterprise customers for stress testing / burn-ins of hardware and checking for stability. Disabling SMT seems to be the closest workaround those experiencing this problem more often in the community have done to try to avoid problems, but then you lose half the threads of the CPU.īesides using ryzen-test to hammer the CPU to easily reproduce the issue, I also decided to use phoronix-test-suite stress-run. When disabling SMT, it takes much longer for the problem to come to head, but it does eventually happen. I also tried setting the memory to its defaults at DDR4-2133, but the issue occurred still in 83 seconds. Sure enough, in the stock configuration of the Ryzen 7 1800X and with the DDR4-3200 speed activated, the first segmentation fault with ryzen-test happened in just 88 seconds. I have been using the latest BIOS, 7A31v17, which is built with AGESA 1.0.0.6. I have been running some tests with a Ryzen 7 1800X with the MSI X370 XPOWER TITANIUM GAMING motherboard with Linux 4.13 and Corsair DDR4-3200 memory. JavaScript is required to view these results or log-in to Phoronix Premium. The problem really comes to light just under very heavy and continuous workloads it seems. In my day-to-day benchmarking of Ryzen CPUs, however, I haven't hit this problem or even on my main production desktop with using Ryzen 5. The ryzen-test script will build GCC in parallel loops from a compressed ramdisk, in order to easily stress the CPU. There is even ryzen-test to easily try reproducing the issue. If carrying out the same tests on Intel CPUs, the segmentation faults do not occur. This Google Doc remains among the resources trying to track this issue on Linux while on the Gentoo Forums, AMD Forums, and elsewhere are more reports of various problems encountered under extreme workloads - like a ton of code compiling for hours on end, but can also happen in other scenarios.ĪMD hasn't publicly commented on the problem and as of Linux 4.13 the issue is still happening. I did and still am able to reproduce the problem.įor those that missed our earlier article on the matter from early June, heavy workloads can cause problems on Ryzen, in particular segmentation faults while there have also been reports of some stability problems. With running a number of new Ryzen Linux tests lately, a number of readers requested I take a fresh look at the reported Ryzen segmentation fault issues / bugs affecting a number of many Linux users.
0 Comments
Leave a Reply. |