Bug 42190 - [SNB]ES 1.1 conformance linehv.c fail
Summary: [SNB]ES 1.1 conformance linehv.c fail
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: All Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2011-10-25 01:05 UTC by bo.b.wang
Modified: 2019-09-25 18:49 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Description bo.b.wang 2011-10-25 01:05:46 UTC
System Environment:
Libdrm:        (master)2.4.26-12-gb317c96361f88a0a4ccb2faeff09b0476d142c68
Mesa:        (master)116b7bb5eac836953fbfbc627cabca4a7ee39937
Cairo:        (master)26c9994393f590c43714ba8d799093b84dd94dc6
Libva:        (master)c532920f95c9cd55516c038d769f236ac7e88ccc
Kernel:    (drm-intel-next) 64a742fac3a22f57303d8f1b7e34

Bug Description:
Ogles1conform/ogles1conform/es1/conform/conform/conform -s -v 2 -1 linehv.c fail on SandyBridge
Comment 1 Kenneth Graunke 2011-10-28 10:59:53 UTC
Confirmed.  I haven't investigated this, but I'm somewhat afraid it might be similar to oglconform horizontal/vertical line rasterization tests where our hardware just doesn't work the way it wants.
Comment 2 Elio 2015-09-23 17:59:40 UTC
As a matter of fact , Horizontal and Vertical Line test is failing with the following configuration:

System enviroment
Platform = Skylake U
Kernel = 4.2 drm-intel-testing 2015-08-28.
Mesa = 10.6.7
xf86-video-intel = 2.99.917 
libdrm = 2.4.64 
libva = 1.6.1 
vaapi-intel-driver = 1.6.1
Cairo = 1.14.2 
Xorg Xserver = 1.17.2 
intel-gpu-tools = v1.12
Comment 3 GitLab Migration User 2019-09-25 18:49:07 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/1380.

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.