AMDGPU-PRO 16.60 Vulkan vs. Mesa 17.1-dev RADV Performance

[Amarildo]

Just like I thought, it's still buggy.
Great, another 2 months just to see if AMD will even support my card at all. I should have just bought a NVIDIA card instead, I wouldn't have problems at all.

[difron]

Just like I thought, it's still buggy.

Did you test it with 4.9 kernel? It may happen to work with 4.10, which is less then 2 months away.

[bridgman]

Just like I thought, it's still buggy.
Great, another 2 months just to see if AMD will even support my card at all. I should have just bought a NVIDIA card instead, I wouldn't have problems at all.

What issues did you encounter ? Good bug reports can get *your* system running a lot more quickly.

Even better, test with all-open amdgpu on your spare drive, report bugs (which can be fixed more quickly because of the development model), and then try running OpenCL over the all-open stack as others have suggested.

[Amarildo]

"CL_HOST_OUT_OF_MEMORY" or something like that, I don't remember the exact message. It's the same message I saw when I tried 16.50. The difference now is that Blender/clinfo detect my card as "Pitcairn", but all the rest is still wrong: model, clocks, etc.

I'm not even in the mood to try with the open stack, because I tried it with 16.50 and the results were the same on 'Arch+OSS Stack' and 'Ubuntu+AMDGPU-PRO'.

[difron]

"CL_HOST_OUT_OF_MEMORY" or something like that, I don't remember the exact message. It's the same message I saw when I tried 16.50. The difference now is that Blender/clinfo detect my card as "Pitcairn", but all the rest is still wrong: model, clocks, etc.

I'm not even in the mood to try with the open stack, because I tried it with 16.50 and the results were the same on 'Arch+OSS Stack' and 'Ubuntu+AMDGPU-PRO'.

I have same error on Arch+OSS amdgpu+16.60 opencl on Cape Verde with 4.9 kernel. So don't think it works for you as well.
bridgman So where should I submit such bugreport then?

[Amarildo]

Did you test it with 4.9 kernel? It may happen to work with 4.10, which is less then 2 months away.

I tested with 4.4 (the default Kernel on Ubuntu 16.04), which is the Kernel AMD tests this driver AFAIK.
Last time I tested on Arch with the 4.7-staging Kernel.

[Amarildo]

I have same error on Arch+OSS amdgpu+16.60 opencl on Cape Verde with 4.9 kernel. So don't think it works for you as well.
bridgman So where should I submit such bugreport then?

What specific model? I believe Cape Verde is not too far apart from my 270X.

These are the models 16.60 supposedly supports: AMD Radeon™ HD7700/7800/8500/8600

[bridgman]

Which app/test are you both running when you get this message ? Guessing Blender for Amarildo, does it happen with any simpler apps ?

If Blender, did it run successfully on the same system with fglrx ? Thanks !

[Amarildo]

Which app/test are you both running when you get this message ? Guessing Blender for Amarildo, does it happen with any simpler apps ?

If Blender, did it run successfully on the same system with fglrx ? Thanks !

Yes, Blender. I don't use OpenCL for other programs, but I'll try Luxmark on Ubuntu tonight to see if it works.

Interestingly enough, Catalyst doesn't work either. I tested it a few times in the last few months with different version of Blender (from the archive, and also from git) and it just didn't work. It did work for one specific version of Blender, which I don't remember, but then it just stopped working for some reason. I think Blender did something that crippled Catalyst 's OpenCL and also the Windows driver OpenCL for me, then I reported the problem (to AMD) and you fixed it quickly on Windows.

[Amarildo]

Luxmark doesn't work either, clearly something related to the OpenCL driver. You can see in the mid-right part of this image how a lot of information is just wrong: http://i.imgur.com/axSmPY9.png