Bug 90828 - [BSW Bisected]GpuTest GiMark fail to run due to GLSL 3.30 is not supported
Summary: [BSW Bisected]GpuTest GiMark fail to run due to GLSL 3.30 is not supported
Status: VERIFIED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Tapani Pälli
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-03 11:29 UTC by wendy.wang
Modified: 2015-06-24 06:22 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
geeks3d_gputest_log.txt (2.83 KB, text/plain)
2015-06-03 11:29 UTC, wendy.wang
Details
geeks3d_gputest_scores (230 bytes, text/plain)
2015-06-03 11:30 UTC, wendy.wang
Details
dmesg (117.89 KB, text/plain)
2015-06-03 11:31 UTC, wendy.wang
Details

Description wendy.wang 2015-06-03 11:29:27 UTC
Created attachment 116263 [details]
geeks3d_gputest_log.txt

==System Environment==       
-----------------------------------------------------
Mesa Regression: Yes
Not working platform: BSW

Failed GFX SW stack:
 Libdrm:		(master)libdrm-2.4.61-13-g97be70b45eccc37e98a1cecf360593f36956ea42
 Mesa:		(master)065978d36b8a8ba5aa23248c6bcd0f0e4d6e86de
 Xserver:		(master)xorg-server-1.17.0-157-gcbb7eb73b5399e31a7afb800363504d539df0ecf
 Kernel:   (drm-intel-nightly)b44f6771cba2cc90525d037445330ed766377aa


Bisect result show first bad commit is:
commit 9b5e92f4ccc6ee1cb9caea947f6efaad2b391cf1
Author:     Ian Romanick <ian.d.romanick@intel.com>
AuthorDate: Wed Apr 29 16:12:40 2015 -0700
Commit:     Ian Romanick <ian.d.romanick@intel.com>
CommitDate: Thu May 28 16:56:31 2015 -0700

    mesa: Allow overriding the version of ES2+ contexts

    Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
    Reviewed-by: Tapani Pälli <tapani.palli@intel.com>


==Bug detailed description==
--------------------------------------------------
GpuTest GiMark fail to run with below error message in log.
Pixel shader error: 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES

2015:06:03@19:18:50, ID=27 >> - Render thread - GiMark init failed.
2015:06:03@19:18:50, ID=28 >> Stopping gxl3d engine...
2015:06:03@19:18:50, ID=29 >> Exit from Geeks3D GpuTest.

Log files attached.


==Reproduce steps==
----------------------------
1. cd /usr/local/games/OpenGL/GpuTest_0.5
2. export MESA_GL_VERSION_OVERRIDE=3.2
3. xinit &
4. ./GpuTest /test=gi /width=1920 /height=1080 /benchmark /no_scorebox
Comment 1 wendy.wang 2015-06-03 11:30:44 UTC
Created attachment 116264 [details]
geeks3d_gputest_scores
Comment 2 wendy.wang 2015-06-03 11:31:16 UTC
Created attachment 116265 [details]
dmesg
Comment 3 Tapani Pälli 2015-06-03 16:27:02 UTC
does the patch in bug #90797 fix this one?
Comment 4 Ding Heng 2015-06-08 08:33:34 UTC
(In reply to Tapani Pälli from comment #3)
> does the patch in bug #90797 fix this one?

Case pass with this patch
Comment 5 Tapani Pälli 2015-06-23 17:43:23 UTC
Fixed in master:

commit 7d88ab42b9dda825feddbae774a2a48ddf3cbec2
Author: Tapani Pälli <tapani.palli@intel.com>
Date:   Tue Jun 16 13:46:47 2015 +0300

    mesa: set override_version per api version override
    
    Before 9b5e92f get_gl_override was called only once, but now it is
    called for multiple APIs (GLES2, GL), version needs to be set always.
Comment 6 wendy.wang 2015-06-24 06:22:28 UTC
Bug has been verified as fixed with latest Mea master branch:

 Libdrm:		(master)libdrm-2.4.61-13-g97be70b45eccc37e98a1cecf360593f36956ea42
 Mesa:		(master)028590cbc758e877b963ba430f0a0cb49e882a6b
 Xserver:		(master)xorg-server-1.17.0-158-gfa12f2c150b2f50de9dac4a2b09265f13af353af
 Xf86_video_intel:		(master)2.99.917-366-g87b5ca2c3ed45a46ac037e71e96922b1a7f8c10f
 Cairo:		(master)2cf2d8e340a325adb205baf8e4bd64e1d1858008
 Libva:		(master)5d07b29687db6d17811b7ecf9b779377e9851a27
 Libva_intel_driver:		(master)0f6143e2e4bd70217887e1ad86a76200ad8b38a8
 Kernel:   (drm-intel-nightly)be39a7ed43b45f63aff1ad3b61008f67692db202


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.