Bug 56918

Summary: [R350] Black labels on MapsGL
Product: Mesa Reporter: madbiologist <madbiologist2016>
Component: Drivers/Gallium/r300Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: madbiologist2016
Version: 9.0   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: screenshot from Mesa 9.0
radeon debug output
MESA_GLSL plus RADEON_DEBUG output
new screenshot from Mesa 9.0

Description madbiologist 2012-11-09 13:03:54 UTC
Created attachment 69809 [details]
screenshot from Mesa 9.0

Using a Radeon 9800 Pro 128MB (R350) on both Mesa 8.04 and Mesa 9.0. All of the labels in Google MapsGL are black rectangles.  This is actually slightly worse on Mesa 9.0, with which the location names (at lower zoom levels) park, national park and state forest labels now show text on a black background instead of normal text as before.  On both versions of Mesa the street names are not shown, there are only black rectangles where the street names should be.

Attached screenshot is from Firefox 16.0.2 running on Mesa 9.0 on Ubuntu 12.10.  The 3.5.0-2-generic #2-Ubuntu kernel is a bit out of date - I can update to the 3.5.0-17.28 kernel (which rebases to upstream 3.5.5 plus a few small changes) if that is important.

Please note that this is NOT the same as bug 49088.  The fix for that was specifically included in 8.0.4-0ubuntu0.1 and mentioned in the changelog.
Comment 1 Tom Stellard 2012-11-09 13:17:08 UTC
(In reply to comment #0)
> Created attachment 69809 [details]
> screenshot from Mesa 9.0
> 
> Using a Radeon 9800 Pro 128MB (R350) on both Mesa 8.04 and Mesa 9.0. All of
> the labels in Google MapsGL are black rectangles.  This is actually slightly
> worse on Mesa 9.0, with which the location names (at lower zoom levels)
> park, national park and state forest labels now show text on a black
> background instead of normal text as before.  On both versions of Mesa the
> street names are not shown, there are only black rectangles where the street
> names should be.
> 
> Attached screenshot is from Firefox 16.0.2 running on Mesa 9.0 on Ubuntu
> 12.10.  The 3.5.0-2-generic #2-Ubuntu kernel is a bit out of date - I can
> update to the 3.5.0-17.28 kernel (which rebases to upstream 3.5.5 plus a few
> small changes) if that is important.
> 
> Please note that this is NOT the same as bug 49088.  The fix for that was
> specifically included in 8.0.4-0ubuntu0.1 and mentioned in the changelog.

Can you set the environment variable RADEON_DEBUG=fp,vp and then post the debugging output you get with firefox and Google MapsGL.
Comment 2 madbiologist 2012-11-09 14:54:32 UTC
How do I set that?  In the GRUB kernel boot options?  Or with "setenv"?  And where do I look for the debugging output?  dmesg?  Xorg.log?  Or somewhere else?
Comment 3 Tom Stellard 2012-11-09 14:58:12 UTC
(In reply to comment #2)
> How do I set that?  In the GRUB kernel boot options?  Or with "setenv"?  And
> where do I look for the debugging output?  dmesg?  Xorg.log?  Or somewhere
> else?

Open a terminal a start firefox like this:

RADEON_DEBUG=fp,vp firefox &>mapsgl.log

Then do some stuff with MapsGL, close firefox and post the mapsgl.log file.
Comment 4 madbiologist 2012-11-09 15:28:32 UTC
Created attachment 69823 [details]
radeon debug output

Thanks.  Attached file is from using Google MapsGL on Firefox 16.0.2 with Mesa 9.0.
Comment 5 Tom Stellard 2012-11-13 15:10:34 UTC
There are two failing shaders here.

The first shader fails with too many instructions.  It looks like we could get it to pass if we had a Common Subexpression Elimination optimization.

The second shader fails because it uses 7 Texture indirections and the hardware can only do 4.  However three of the Texture indirections contain only KIL instructions, so I think we may be able to fix it, but I need to see what the GLSL looks like.  Can you add the environment variable MESA_GLSL=dump and post the output again:

MESA_GLSL=dump RADEON_DEBUG=fp,vp firefox &>mapsgl.log
Comment 6 madbiologist 2012-11-15 14:44:26 UTC
Created attachment 70121 [details]
MESA_GLSL plus RADEON_DEBUG output

Here is the new output while using Google MapsGL on Firefox 16.02 with Mesa 9.0.  I'm now using the newer Ubuntu kernel mentioned above, and definitely Mesa 9.0.

The previous log should be with Mesa 9.0, although I did upgrade from Mesa 8.04 while running an Ubuntu 12.10 alpha 2 LiveCD and obviously could not reboot - is a reboot necessary?. I'm now running the LiveCD of Ubuntu 12.10 final.  I only mention this because the result looks slightly different for the park, national park, state forest, etc labels - they now have no visible text, just a black rectangle like the street names.  The street names are unchanged, just black rectangles like before.  I will attach a new screenshot.
Comment 7 madbiologist 2012-11-15 14:46:40 UTC
Created attachment 70122 [details]
new screenshot from Mesa 9.0
Comment 8 madbiologist 2012-11-15 16:22:18 UTC
Woops, sorry about that last attachment.  Thanks Alex for fixing it.
Comment 9 Tomasz P. 2013-01-11 22:02:31 UTC
So your issue is fixed or not ?
Comment 10 madbiologist 2013-01-18 18:33:44 UTC
Only 2 days waiting for a response before closing this bug?  I think someone might be trigger happy.

My comment 8 was referring to the fact that I had uploaded an attachment with the wrong MIME type, and that Alex Deucher was good enough to change the MIME type to the correct one.

This issue is still occurring on Firefox 18.0 and continues to occur after updating to the xorg-edgers PPA.  This PPA has Mesa 9.1~git20130104.r1.b8b1d61e-0ubuntu0ricotz~precise
Comment 11 madbiologist 2013-05-03 10:13:33 UTC
Any update on this?
Comment 12 GitLab Migration User 2019-09-18 18:51:13 UTC
-- 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/344.

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.