Bug 109574

The HD 2600 Pro and  HD 4850 are slightly different hardware, so that the shader code generated by the drivers might be somewhat different. 

In any case, you can try to run blender with

  R600_DEBUG=nosb blender 

and see whether this helps. If this doesn't help then you please add the logging output by running 

  R600_DUMP_SHADERS=1 blender 

from both computers. This will print the shaders and one might be able to spot a difference that gives an idea where to look.

These messages:

Received X11 Error:
	error code:   182
	request code: 156
	minor code:   34
	error text:   GLXBadFBConfig
[...]
Received X11 Error:
	error code:   8
	request code: 156
	minor code:   34
	error text:   BadMatch (invalid parameter attributes)

indicate that blender fails to create a GLX context multiple times. Do you get these messages on the other system with an HD 2600 Pro as well? If not, it might be helpful if you attach the Xorg log files and the outputs of glxinfo from both systems.

Created attachment 143338 [details]
glxinfo HD 4850

Created attachment 143339 [details]
r600dumpsshaders_HD4850_output

Created attachment 143340 [details]
Xorg Logs of HD4850

Created attachment 143341 [details]
glxinfo HD2600pro

Created attachment 143342 [details]
R600_DUMP_SHADERS_hd2600pro

Created attachment 143343 [details]
xorg log files hd2600pro

Blender version: 2.80 (sub 44), commit date: 2019-02-07 23:15, hash: 3d16a268ee68

Mr. Wollny,

I tried R600_DEBUG=nosb blender but nothing's changed. I added the log files you asked.


Mr. Michel,

I also get these messages on my other system. I discovered that both system's aren't able to run blender without a problem. Even though the interface is good, I experienced crashes on my HD2600 system. 

I added log files you asked also.

One difference between the glxinfo outputs is that there are no 10 bit per component FBConfigs with the HD 2600 Pro. Does running blender like this:

 allow_rgb10_configs=false blender

avoid the problem?

Unfortunately no. Nothing's changed.

for one thing you are actually running different versions of mesa: 
This is the 2600:
-    Device: AMD RV630 (DRM 2.50.0 / 4.15.0-45-generic, LLVM 7.0.0) (0x9589)
-    Version: 18.3.3

and this is the 4850: 
+    Device: AMD RV770 (DRM 2.50.0 / 4.15.0-45-generic, LLVM 7.0.0) (0x9442)
+    Version: 18.2.2

Now I have Padoka PPA installed in both systems. Problem still occurs. I tried again "R600_DEBUG=nosb blender" and "R600_DUMP_SHADERS=1 blender" but nothing's changed.

I've seen a few differences in the shaders created on HD2600 vs. HD4850 (one has a R6xx class chip, the other a R7xx chip), i.e. at some points in the shader creatied for HD2600  contain workarounds for hardware bugs in R6xx. It might be that some of those also would apply to R7xx chips, but I can't test this, because I don't have the hardware. As cards using the r600 drivers go I now only have a HD 5450 which uses the "Evergreen" code path, and there everything looks okay (with R600_DEBUG=nosb).

FWIW; I see the same GLX errors on this card that don't show up when I run the radeonsi card (Since both cards are in the same system there is no difference in the software).

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/652.