Bug 28292 - [i915 i965] oglc/pxstore-depth.c failed
Summary: [i915 i965] oglc/pxstore-depth.c failed
Status: CLOSED WONTFIX
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i915 (show other bugs)
Version: git
Hardware: Other Linux (All)
: medium normal
Assignee: Eric Anholt
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-27 23:18 UTC by Shuang He
Modified: 2015-06-16 02:02 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shuang He 2010-05-27 23:18:40 UTC
System Environment:
--------------------------
Libdrm:         (master)fcf3e616eeeb289f96af1436d809f0a1a42bebb7
Mesa:           (master)ba404c8f2a7e7ae25cccb66bdf378b4106d2a4df
Xserver:                (master)531ff40301975519af7b20109c17d296312d3f2b
Xf86_video_intel:              
(master)03bbb4c896ef3cd275312b413a2c85d9f499c032
Kernel:       (for-linus)722154e4cacf015161efe60009ae9be23d492296

Bug detailed description:
-------------------------

OGLC/pxstore-depth.c failed on G45 and 945GM
This bug is for tracking residual issue from bug 23670.
This case once passed with following configuration:
Libdrm 	(master)73b59c894380995a2889b98e79acadd2da0bb237
Mesa 	(master)165e87c49180380b67b096211b4c5f9670e3020a
Xf86_video_intel 	(master)5812531e08147576de776b2dd64e7f94c08eb851
Kernel 	(drm-intel-next)dd64c8407d828796f638e40931f707ab96009c6e
Comment 1 Ouping Zhang 2011-04-28 19:06:58 UTC
System Environment:
--------------------------
Libdrm:    (master)2.4.25
Mesa:      (7.10)73f4273b8647abe0020ad3c2d593e009092d2be5
Xserver:   (server-1.10-branch)xorg-server-1.10.1
Xf86_video_intel:   (master)2.15.0-6-g67e5a74e997f199327f9115c7ba867df3c49da8d

case pxstore-depth still fails on PineView, G45 and Piketon.
Comment 2 Gordon Jin 2015-06-16 02:02:34 UTC
closing as won't fix.


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.