log in |
Message boards : Number crunching : FMA problems (Ryzen and others?)
1 · 2 · Next
Author | Message |
---|---|
I got the first few FMA Apps on my Ryzen ... not that good results | |
ID: 996 · ![]() | |
I marked the Windows X64 FMA application version as 'beta', so only users that agreed to 'Run test applications' in their profile should now get it. I know that Ryzen had some problems with FMA3 (although, afaik, we don't use FMA3 op-codes here, Daniel may say something about), see here: http://forum.hwbot.org/showthread.php?t=167605 | |
ID: 997 · ![]() | |
I changed it for my Bristol Ridge AMD, but have to wait for some FMA WUs because it have has much AVX in work for now | |
ID: 998 · ![]() | |
FMA app uses FMA3 instructions, they are supported by both AMD and Intel CPUs. FMA4 is supported by AMD only, so FMA app does not use them. | |
ID: 1000 · ![]() | |
I am waiting for a BIOS Update but the latest one is installed and i dont use any antivirus software. | |
ID: 1001 · ![]() | |
On Linux (4.10) the FMA app works fine on my R7. | |
ID: 1005 · ![]() | |
Same here with Ryzen 7 1700 and Win 10. | |
ID: 1008 · ![]() | |
I tried to disassemble compiled binary and things got interesting. All crash reports here mentions following error: Privileged Instruction (0xc0000096) at address 0x00000000004f5458 When I checked instruction at this address, I got "STI" which is a sensitive instruction according to https://support.microsoft.com/en-nz/help/114473/intel-privileged-and-sensitive-instructions. But when I tried to disassemble whole app, it turned out that address 0x00000000004f5458 is invalid - valid instruction starts one byte earlier, at 0x00000000004f5457. Instruction at this address is "vmovsd" - it is an AVX instruction. This instruction maps to line 160 in pc.cpp. It looks like Ryzen decided to jump to some invalid address and executed some random instruction there which turned out to be an STI instruction. Valterc, do you know if Windows 64-bit FMA app works fine on other CPUs? I wonder if this problem affects Ryzen CPUs only, or all users with FMA-capable CPUs and 64-bit Windows. ____________ ![]() | |
ID: 1009 · ![]() | |
I can give more information tomorrow but if you check my Windows hosts you may see one of them (I7 4770k) crunching happily with the fma app. | |
ID: 1010 · ![]() | |
The previous Windows FMA app (still with large output file), was that provided by Daniel, created with MingW/GCC? | |
ID: 1011 · ![]() | |
I test the fma app on my System with | |
ID: 1012 · ![]() | |
I suspect the MS compilers can't compile error free FMA binaries for Ryzen, something like that. | |
ID: 1013 · ![]() | |
Both Windows and Linux apps are compiled using gcc. Linux app was compiled using gcc 4.8.5. Windows one was compiled with gcc 5.4.0, so its code probably is better optimized than Linux one. There are also some system-specific changes, they also may play role here. | |
ID: 1014 · ![]() | |
Thanks for the info ;-) | |
ID: 1015 · ![]() | |
Any update on this? People on hwbot forum says that ASUS released new BIOS which resolved problem for them. Did you have change to test it, or one for your mainboard if available? | |
ID: 1016 · ![]() | |
My ASUS Mainboard died a few days ago and i changed to a MSI MB, but MSI removed the Beta BIOS with the new AGESA Update so i am not able to try and ASUS had no available because of a heavy bug in the AGESA Update. | |
ID: 1018 · ![]() | |
Thanks to an AGESA-Update with the new Beta-Bios for my ASUS Prime B350-Plus the FMA-App is noe working fine with my R7 1700. | |
ID: 1027 · ![]() | |
OK something is still strange. | |
ID: 1028 · ![]() | |
Thanks to an AGESA-Update with the new Beta-Bios for my ASUS Prime B350-Plus the FMA-App is noe working fine with my R7 1700. Did you install a BETA bios??? :-O | |
ID: 1029 · ![]() | |
I´m the risky kind of guy... ;) | |
ID: 1030 · ![]() | |
Message boards :
Number crunching :
FMA problems (Ryzen and others?)