Bug 19935

Summary:

[GME965] Major opcode of failed request: 135 (DRI2)

Product:

DRI

Reporter:

smith <stopads>

Component:

DRM/Intel

Assignee:

Gordon Jin <gordon.jin>

Status:

CLOSED FIXED

QA Contact:

Severity:

major

Priority:

medium

CC:

eric

Version:

unspecified

Keywords:

NEEDINFO

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Also shows output when LIBGL_ALWAYS_INDIRECT=1, but direct rendering: No	none
list of tarball versions used to build Xorg	none
Build script for creating Xorg from tarballs	none
config file showing usage of UXA	none
log file from Xorg	none
more system info, if desired	none

Description smith 2009-02-03 10:40:08 UTC

Bug description:

As usual, I'm not 100% sure what to file this bug under.  The closest reported bug involves Quake 4, therefore I'm opening this one because it can be reproduced *very* easily (no extra packages).

[joe@xyz ~]$ glxinfo
name of display: :0.0
X Error of failed request:  BadLength (poly request too large or internal Xlib length error)
  Major opcode of failed request:  135 (DRI2)
  Minor opcode of failed request:  1 ()
  Serial number of failed request:  16
  Current serial number in output stream:  16
[joe@xyz ~]$ 
Same for glxgears, neverball, etc.


System environment:
-- chipset:  GME965
-- system architecture: 32-bit
-- xf86-video-intel: 2.6.1
-- xserver: 1.5.99.902
-- mesa: 7.3
-- libdrm: 2.4.4
-- kernel: from http://intellinuxgraphics.org/2008Q4.html
-- Linux distribution: Fedora 10
-- Machine or mobo model: embedded board (Intel Core2 Duo CPU T7500 @ 2.20GHz, 2 GB RAM)
-- Display connector: DVI to HP LP2065

Reproducing steps:

1) Install components from http://intellinuxgraphics.org/2008Q4.html on Fedora 10.  (I also tried using the latest mesa and intel driver, as shown by my sources list.  No improvement.)

2) Run glxinfo, or glxgears, or neverball, etc.  They all fail the same way.

Additional info:

I am attaching my xorg build script, all associated logs, etc.

I am willing to test different combinations of components.  Please let me know.
Thanks!

Comment 1 smith 2009-02-03 10:42:09 UTC

Created attachment 22530 [details]
Also shows output when LIBGL_ALWAYS_INDIRECT=1, but direct rendering: No

Comment 2 smith 2009-02-03 10:43:03 UTC

Created attachment 22531 [details]
list of tarball versions used to build Xorg

Comment 3 smith 2009-02-03 10:43:32 UTC

Created attachment 22532 [details]
Build script for creating Xorg from tarballs

Comment 4 smith 2009-02-03 10:45:26 UTC

Created attachment 22533 [details]
config file showing usage of UXA

Comment 5 smith 2009-02-03 10:45:52 UTC

Created attachment 22534 [details]
log file from Xorg

Comment 6 smith 2009-02-03 10:46:14 UTC

Created attachment 22535 [details]
more system info, if desired

Comment 7 smith 2009-02-03 10:50:20 UTC

The output from building Xorg is too large (1.6 MB).  I can email the file if you want.

Again, I'm willing to test any changes.  Just let me know.

Comment 8 Gordon Jin 2009-02-05 22:25:18 UTC

Looks like a misconfiguration issue. Please paste output of "ldd /usr/bin/glxgears". Does that returns the right libGL path you've built and installed?

Comment 9 smith 2009-02-06 07:00:01 UTC

Good call!  The wrong libraries were being used.  So the missing piece is I have to export LD_LIBRARY_PATH *every* time.  I was led to believe that exporting the path once before launching X was all I needed.  In other words, I thought the path would be persistent for my entire X session.  Obviously it is not.

What's the best procedure for updating my system to point to a new Xorg build once I've determined it's stable?  For example, I'd like to continue building the driver in a separate directory so I don't corrupt my Fedora 10 installation with a bad build.  When it's time to make it permanent, how should I ask to Fedora to load the new Xorg instead of the old Xorg without manually exporting the LD_LIBRARY_PATH and manually starting X with the new path to Xorg?

BTW, I'll update the wiki to prevent others from having this problem.

Thanks!

Comment 10 Gordon Jin 2009-02-06 21:15:07 UTC

(In reply to comment #9)
> What's the best procedure for updating my system to point to a new Xorg build
> once I've determined it's stable?  

I have below lines in ~/.bashrc:
export PATH=/opt/X11R7/bin:$PATH
export LIBGL_DRIVERS_PATH=/opt/X11R7/lib/dri:/opt/X11R7/lib
export LD_LIBRARY_PATH=/opt/X11R7/lib

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.