Created attachment 136962 [details] screenshot of artifact with compatibility profile While enabling GL 4.x core profiles on Radeon HD 6770 (Juniper), applications such as genymotion and most wine games crash without any error. WHen using 4.xCOMPAT profile instead of core, they do not crash, however, some games in wine have serious graphical corruption (such as in atachment). This is with mesa-git (with all commits to this date) and earlier versions, just to report it so it can be solved before enabling core profiles by default.
Are you running Wine-Nine? I remember such 'red'ich' colors with Nine. Then it could be the current Mesa git Nine bug.
(In reply to Dieter Nützel from comment #1) > Are you running Wine-Nine? > I remember such 'red'ich' colors with Nine. > Then it could be the current Mesa git Nine bug. No, this glitch is under Wine CSMT D3D, when using nine it is actually proper picture with compatibility mode, with core profile, it is irrelevant what I use (nine or wine d3d) it would crash instantly without any trace in terminal, but standard wine output error in "Windows like" dialog. With core profile, same would happen to native GNU/Linux application genymotion, but it does work with COMPAT profile. If you are asking me is wine patched with nine, yes it is, but that should be irrelevant when "nine" is unticked and CSMT or non-CSMT wine translation is used.
(In reply to lei.pero from comment #2) > (In reply to Dieter Nützel from comment #1) > > Are you running Wine-Nine? > > I remember such 'red'ich' colors with Nine. > > Then it could be the current Mesa git Nine bug. > > No, this glitch is under Wine CSMT D3D, when using nine it is actually > proper picture with compatibility mode, with core profile, it is irrelevant > what I use (nine or wine d3d) it would crash instantly without any trace in > terminal, but standard wine output error in "Windows like" dialog. > > With core profile, same would happen to native GNU/Linux application > genymotion, but it does work with COMPAT profile. > > If you are asking me is wine patched with nine, yes it is, but that should > be irrelevant when "nine" is unticked and CSMT or non-CSMT wine translation > is used. Yes,right. Is this a regression (worked before)? Can you bisect?
(In reply to Dieter Nützel from comment #3) > (In reply to lei.pero from comment #2) > > (In reply to Dieter Nützel from comment #1) > > > Are you running Wine-Nine? > > > I remember such 'red'ich' colors with Nine. > > > Then it could be the current Mesa git Nine bug. > > > > No, this glitch is under Wine CSMT D3D, when using nine it is actually > > proper picture with compatibility mode, with core profile, it is irrelevant > > what I use (nine or wine d3d) it would crash instantly without any trace in > > terminal, but standard wine output error in "Windows like" dialog. > > > > With core profile, same would happen to native GNU/Linux application > > genymotion, but it does work with COMPAT profile. > > > > If you are asking me is wine patched with nine, yes it is, but that should > > be irrelevant when "nine" is unticked and CSMT or non-CSMT wine translation > > is used. > > Yes,right. > > Is this a regression (worked before)? > Can you bisect? As far as I know it isn't regression, the first time I've tried to enable 4.1 profile it did behave that way, I think it was on Mesa 12.0, but don't hold me for a word. I did not reported at that time because there was no full support for r600, but now, I reported it just in case decision comes to enable 4.x profile by default, not to "slip" in stable realese. With core profile 3.3 (default one) everything works as expected, none of these issues. I could try to bisect, but I don't think distribution would alow me to go that far, and if even there is a point of doing so because almost full support for r600 was added just recently.
How exactly do you enable compat or core profiles? Afaik Gallium Nine should not be affected by any OpenGL related options... Also, when wine program crashes and you refuse the dialog (press ESC?), the debugger would dump all info (including backtrace) in the terminal. Since the winedbg does not recognize modern debug symbols, you should compile mesa3d with only dwarf2, as described in ixit nine website debug section. Of course, this is if the backtrace is showing mesa3d related functions at all.
It doesn't matter how I enabled it, results are the same. However, I tested now, with Mesa 18.1.4 and it does not crash applications that were crashing before, everything seems to work fine with any OpenGL CORE profile from 4.1 to 4.5 (did not test earlier or latter versions). COMPAT profile still has artifacts but that's to be expected I guess. So, it seems that problem is resolved, have to test a bit more, if anything goes wrong I will post.
So... How have we been doing? Can this be closed?
(In reply to mirh from comment #7) > So... How have we been doing? Can this be closed? Still keeping Core profile 4.5, no problem so far, as far as I'm concerned, it can be closed, not sure what fixed it tho.
-- 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/626.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.