Bug 19474

Summary: [OGLC]oglconform case texsubimage.c fail on 64-bit systems
Product: Mesa Reporter: liuhaien <haien.liu>
Component: Drivers/DRI/i915Assignee: Ian Romanick <idr>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: medium CC: idr
Version: unspecified   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 20277    
Attachments: xorg.0.log
xorg conf file

Description liuhaien 2009-01-08 18:37:10 UTC
Created attachment 21818 [details]
xorg.0.log

System Environment:
--------------------------
Libdrm:         (master)badc63464cbd64606c6dff9ea561a787d072fd5f
Mesa:            (intel-2008-q4)eef0dcc298f65158dc750a09f80317ded1101dc7
Xorg:           7.2
Xserver: (server-1.6-branch)32e81074b967716865aef08b66ec29caf0fec2c5
Xf86_video_intel:        (xf86-video-intel-2.6-branch)
                         4447973345a2a7af20ba1d6cb18c5f1ed8949d00
GEM_kernel:       (drm-intel-2.6.28)a0b55c920a72959846837cfa18e0975c3c9c0229



Bug detailed description:
-------------------------
startx, run oglconform,the case "texsubimage" fail on x86_64 machines,but it is fine on all i386 machines.

Reproduce steps:
----------------
1.xinit&
2. run oglconform/texsubimage.c
Comment 1 liuhaien 2009-01-08 18:37:38 UTC
Created attachment 21819 [details]
xorg conf file
Comment 2 liuhaien 2009-03-22 20:38:06 UTC
still exists against:
Libdrm:         (master)00d8e960ca665b7f0528438331f4d0ae77fbb4cc
Mesa:(mesa_7_4_branch)b009a32bf428192fef2dc4787d25f022a472854f          
Xserver:        (server-1.6-branch)60c161545af80eb78eb790a05bde79409dfdf16e
Xf86_video_intel:       (2.7)e2465249a90b9aefe6d7a96eb56a51fde54698a0
Kernel:       (for-airlied)a2e785c32b886dd7f0289d1cf15fc14e9c81bc01
Comment 3 haihao 2009-10-27 18:55:56 UTC
Ian, this is an oglconform issue, could you take it?
Comment 4 Gordon Jin 2011-02-27 17:48:21 UTC
This doesn't exist now.

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.