Bug 30224 - mesa case tests/jkrahantest fails
Summary: mesa case tests/jkrahantest fails
Status: CLOSED DUPLICATE of bug 30234
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-16 04:01 UTC by fangxun
Modified: 2012-10-30 06:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
xorg log file (21.65 KB, text/plain)
2010-09-16 04:01 UTC, fangxun 		Details
View All

Description fangxun 2010-09-16 04:01:21 UTC 
Created attachment 38741 [details]
xorg log file

System Environment:
--------------------------
Platform:   pineview
Libdrm:     (master)2.4.21-21-g7ec9a1effa4f551897f91f3b017723a8adf011d9
Mesa:       (7.9)83f5f50f2f69adae497c71ac48e4e0177979ebff
Xserver:    (master)xorg-server-1.9.0
Xf86_video_intel: (master)2.12.0-87-g08c2caca48323d6d5701dcef3486f850619d7905
Kernel: (master)2.6.5.34-9fe6206f400646a2322096b56c59891d530e8d51


Bug detailed description:
-------------------------
Errors on screen output:
libGL: OpenDriver: trying /opt/X11R7/lib/dri/i915_dri.so
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  153 (GLX)
  Minor opcode of failed request:  11 (X_GLXSwapBuffers)
  Serial number of failed request:  48
  Current serial number in output stream:  49

This issue happens on piketon and pineview. It is regression. The last known good package is following:
Libdrm:         (master)2.4.21-21-g7ec9a1effa4f551897f91f3b017723a8adf011d9
Mesa:           (master)78109952d47046bfb8d179f32493daa1b5e98615
Xserver:            (master)xorg-server-1.9.0
Xf86_video_intel:    (master)2.12.0-85-g0515256490d5bcd55f85af83b8491 


Reproduce steps:
----------------
1. run tests/jkrahantest
Comment 1 fangxun 2010-09-18 22:42:51 UTC 

*** This bug has been marked as a duplicate of bug 30234 ***

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.