[Intel-gfx] X crashes when terminating application

[Grigory Trakhman]

This happens to me every time I run a 32-bit opengl app on ubuntu
karmic x86-64 with xorg-edgers.  I close it, and it crashes.  Also
happens with nexuiz sometimes.

On Wed, Aug 12, 2009 at 3:00 PM,
<intel-gfx-request at lists.freedesktop.org> wrote:
> Send Intel-gfx mailing list submissions to
>        intel-gfx at lists.freedesktop.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> or, via email, send a message with subject or body 'help' to
>        intel-gfx-request at lists.freedesktop.org
>
> You can reach the person managing the list at
>        intel-gfx-owner at lists.freedesktop.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Intel-gfx digest..."
>
>
> Today's Topics:
>
>   1. Re: X crashes when terminating application (Maurice van der Pot)
>   2. Re: X crashes when terminating application (David Amiel)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 12 Aug 2009 16:50:39 +0200
> From: Maurice van der Pot <griffon26 at kfk4ever.com>
> Subject: Re: [Intel-gfx] X crashes when terminating application
> To: intel-gfx at lists.freedesktop.org
> Message-ID: <20090812145038.GD27535 at kfk4ever.com>
> Content-Type: text/plain; charset="us-ascii"
>
> On Mon, Aug 10, 2009 at 11:23:32AM +0200, Maurice van der Pot wrote:
>>   error setting MTRR (base = 0xd0000000, size = 0x10000000, type = 1) Invalid argument (22)
>>   (EE) intel(0): Failed to initialize kernel memory manager
>
> I got rid of the above two errors by just enabling MTRR cleanup support
> in the kernel (CONFIG_MTRR_SANITIZER).
>
>>   Backtrace:
>>   0: Xorg(xorg_backtrace+0x3c) [0x8128b5c]
>>   1: Xorg(xf86SigHandler+0x52) [0x80bf322]
>>   2: [0xb809c400]
>>   3: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocate_memory+0x2f6) [0xb7b4bca6]
>>   4: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocate_framebuffer+0x321) [0xb7b4c3c1]
>>   5: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_allocate_2d_memory+0xf6) [0xb7b4c706]
>>   6: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b40da5]
>>   7: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b45d30]
>>   8: Xorg(AddScreen+0x192) [0x806e3c2]
>>   9: Xorg(InitOutput+0x1fe) [0x80a824e]
>>   10: Xorg(main+0x1db) [0x806eabb]
>>   11: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7d01a4c]
>>   12: Xorg [0x806e161]
>>
>>   Fatal server error:
>>   Caught signal 11.  Server aborting
>
> Using gdb I found out that the actual segfault is happening in
> drm_intel_bo_alloc(), because bufmgr is NULL. I found one reference to
> this on the net: http://patchwork.kernel.org/patch/38489/
>
> However, just avoiding the NULL dereference and failing allocation
> causes errors:
>
>  Dropping master
>  (EE) intel(0): Failed to allocate HW cursor space.
>  (EE) intel(0): Failed to allocate HW cursor space.
>  (EE) intel(0): Couldn't allocate video memory
>
>  Fatal server error:
>  AddScreen/ScreenInit failed for driver 0
>
> So I guess either bufmgr shouldn't be NULL at this point in time or the
> intel driver should not be going through reinitialisation.
>
> Maurice.
>
> --
> Maurice van der Pot
>
> Gentoo Linux Developer   griffon26 at gentoo.org    http://www.gentoo.org
> Gnome Planner Developer  griffon26 at kfk4ever.com  http://live.gnome.org/Planner
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 198 bytes
> Desc: not available
> Url : http://lists.freedesktop.org/archives/intel-gfx/attachments/20090812/1fff73eb/attachment-0001.pgp
>
> ------------------------------
>
> Message: 2
> Date: Wed, 12 Aug 2009 17:23:15 +0200
> From: "David Amiel" <david at lesamiel.fr>
> Subject: Re: [Intel-gfx] X crashes when terminating application
> To: intel-gfx at lists.freedesktop.org
> Message-ID:
>        <c75dda02449f9e9194d6d3fe7320d40c.squirrel at bubble.dyndns.org>
> Content-Type: text/plain;charset=utf-8
>
> Le Mer 12 ao?t 2009 16:50, Maurice van der Pot a ?crit :
>> On Mon, Aug 10, 2009 at 11:23:32AM +0200, Maurice van der Pot wrote:
>>>   error setting MTRR (base = 0xd0000000, size = 0x10000000, type = 1)
>>> Invalid argument (22)
>>>   (EE) intel(0): Failed to initialize kernel memory manager
>>
>> I got rid of the above two errors by just enabling MTRR cleanup support
>> in the kernel (CONFIG_MTRR_SANITIZER).
>
> it would be great to store those kind of information (error message + its
> resolution(s)) somewhere on the intel-gfx site.
> if someone has an error, probably other people are facing this error too.
>
> David
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
> End of Intel-gfx Digest, Vol 19, Issue 29
> *****************************************
>