Bug 10473

Summary: [855] glxgears and others segfault
Product: Mesa Reporter: Rudi Lippert <fd.o>
Component: Drivers/DRI/i915Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: glxinfo for my system
GDB backtrace of crashed glxgears

Description Rudi Lippert 2007-03-30 06:34:40 UTC
When enabling DRI in XOrg 7.1.1, I get satisfactory information from glxinfo, but glxgears and most other GLX software segfault.
My graphics chip is
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
and I'm using i810-1.7.4, libdrm-2.3.0, x11-drm-20060608 (modules), and kernel 2.6.18.2 (vanilla). I also tried the drm modules from the 2.6.18.2 kernel, but there is no difference.
GDB tells me that the problem occurs in
0xb768d685 in intel_render_quad_strip_verts ()
   from /usr/lib/dri/i915_dri.so
I have lots of other information to share. Please tell me what else would be useful to find the problem.
Comment 1 Michel Dänzer 2007-03-30 07:17:46 UTC
x11-drm-20060608 sounds pretty old, does this also happen with the DRM that comes with the kernel? Which version of Mesa do you have?
Comment 2 Rudi Lippert 2007-03-30 07:35:50 UTC
As I mentioned previously, this also happens with the DRM modules from the 2.6.18.6 kernel.
My MESA version is 6.5.1 (mesa-progs as well).

Gentoo has x11-drm-20070314 on testing. I'll go and try those, too.
Comment 3 Michel Dänzer 2007-03-30 07:49:04 UTC
Would be nice if you could try newer Mesa as well.
Comment 4 Rudi Lippert 2007-03-30 08:24:13 UTC
After upgrading to drm-20070314 and mesa-6.5.2, I cannot get DRI to work at all.
drmSetBusid failed, Permission denied
DRIScreenInit failed. Disabling DRI

I'll keep trying. Any hints for now?
Comment 5 Michel Dänzer 2007-03-30 08:33:51 UTC
(In reply to comment #4)
> drmSetBusid failed, Permission denied

Sounds like something is keeping the DRM device open. What does

sudo lsof /dev/dri/card0

say?
Comment 6 Rudi Lippert 2007-03-30 09:17:07 UTC
it keeps getting weirder...
this should be the most interesting part:

(II) I810(0): Initialized DRM memory manager, 8192 AGP pages
        at AGP offset 0x6000
(--) RandR disabled
Error -12
Failed to initialize batch pool - possible incorrect agpgart installed
(EE) AIGLX error: Calling driver entry point failed(EE) AIGLX: reverting to software rendering

I never changed anything with the agpgart, of course.

lsof reports only the one X server with two entries (FD: mem and 10u)
Comment 7 Michel Dänzer 2007-03-30 09:28:25 UTC
(In reply to comment #6)
> (II) I810(0): Initialized DRM memory manager, 8192 AGP pages
>         at AGP offset 0x6000
> (--) RandR disabled
> Error -12
> Failed to initialize batch pool - possible incorrect agpgart installed

Does Option "Legacy3D" help with that?
Comment 8 Rudi Lippert 2007-03-30 11:06:50 UTC
Ok, now we're back to the previous problem. DRI loads, but glxgears crashes in intel_render_quad_strip_verts again.
There are also lots of warnings like these two:
DISPATCH ERROR! _glapi_add_dispatch failed to add glVertexAttrib1fv!
(WW) AIGLX: 3D driver claims to not support visual 0x23

I probably won't have time for more testing until Sunday, but I'll check back then.
Comment 9 Rudi Lippert 2007-04-02 00:51:18 UTC
Not much has changed so far. I'm on fairly recent versions of x11-drm, mesa, libdrm and video-i810.
Is there any other helpful information I could provide, like gdb backtraces or Xorg.?.log files?
Comment 10 Rudi Lippert 2007-04-04 02:08:06 UTC
Created attachment 9473 [details]
glxinfo for my system
Comment 11 Rudi Lippert 2007-04-04 02:10:15 UTC
Created attachment 9474 [details]
GDB backtrace of crashed glxgears

Obviously, the problem occurs deep inside i915_dri.so
Comment 12 Michael Fu 2007-09-28 01:02:13 UTC
Hmm.. we didn't see this before. glxgears works fine on 855 platform. what distro are you using? does this bug still bother you?
Comment 13 Gordon Jin 2007-10-28 20:19:25 UTC
Closing this aging bug report. Please reopen if you still can reproduce with the latest driver.

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.