From: Paul Menzel <paulepanter@users.sourceforge.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: 4500MHD driver crash
Date: Fri, 16 Jul 2010 10:04:41 +0200 [thread overview]
Message-ID: <1279267481.4164.4.camel@mattotaupa> (raw)
In-Reply-To: <201007160150.51214.tfjellstrom@shaw.ca>
[-- Attachment #1.1: Type: text/plain, Size: 3710 bytes --]
Am Freitag, den 16.07.2010, 01:50 -0600 schrieb Thomas Fjellstrom:
> I've been having this little problem with the intel-gfx driver for a couple
> months at least. Basically the xorg intel driver crashes with these errors:
>
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
> (WW) intel(0): i830_uxa_prepare_access: gtt bo map failed: Cannot allocate memory
>
> Backtrace:
> 0: /usr/bin/X (xorg_backtrace+0x28) [0x466808]
> 1: /usr/bin/X (0x400000+0x67c79) [0x467c79]
> 2: /lib/libpthread.so.0 (0x7ff19b297000+0xef60) [0x7ff19b2a5f60]
> 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff197986000+0x34684) [0x7ff1979ba684]
> 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff197986000+0x3524a) [0x7ff1979bb24a]
> 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff197986000+0x3547a) [0x7ff1979bb47a]
> 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff197986000+0x36a1b) [0x7ff1979bca1b]
> 7: /usr/bin/X (0x400000+0xd4750) [0x4d4750]
> 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7ff197986000+0x319a2) [0x7ff1979b79a2]
> 9: /usr/bin/X (0x400000+0xd4a7e) [0x4d4a7e]
> 10: /usr/bin/X (0x400000+0xca92e) [0x4ca92e]
> 11: /usr/bin/X (0x400000+0x4c7a4) [0x44c7a4]
> 12: /usr/bin/X (0x400000+0x25b4a) [0x425b4a]
> 13: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7ff199d9bc4d]
> 14: /usr/bin/X (0x400000+0x256f9) [0x4256f9]
> Segmentation fault at address 0x29
>
> Fatal server error:
> Caught signal 11 (Segmentation fault). Server aborting
>
>
> After a little google, I've found the following, seemingly similar issues:
>
> http://www.pubbs.net/201001/mandriva/43247-cooker-x-crashing.html
> http://lists.opensuse.org/opensuse-bugs/2010-04/msg01805.html
>
> This crash happens every few days, most of the time when I'm not even using
> the laptop, and the lid is closed, but today it happened while I was
> working. Was somewhat interesting to see things just disappear.
>
> I've been trying to track this issue down for a while, someone said it
> might be an app leaking pixmaps, but I haven't seen xrestop show more than
> 80MB of pixmaps for quite a while. Also, it usually occurs some time after
> graphics start getting really slow (though this last time I didn't really
> notice things getting slow). Talking a second or two for window or
> desktop switching. At no time was there any errors or warnings in dmesg
> related to this, nor was I running out of memory according to "free" or
> the plasma system load viewer applet. Usually I had 1-2GB of ram available
> (not including cache).
At least information about the versions of the X stack you are using are
missing.
If you do not get any answer from the developers, I recommend to proceed
as documented in [1].
Thanks,
Paul
[1] http://intellinuxgraphics.org/how_to_report_bug.html
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2010-07-16 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 7:50 4500MHD driver crash Thomas Fjellstrom
2010-07-16 8:04 ` Paul Menzel [this message]
2010-07-16 8:12 ` Thomas Fjellstrom
2010-07-16 21:02 ` Thomas Fjellstrom
2010-07-16 21:17 ` Niccolò Belli
2010-07-17 6:16 ` Thomas Fjellstrom
2010-07-17 20:01 ` Thomas Fjellstrom
2010-07-18 17:46 ` Thomas Fjellstrom
2010-07-19 14:02 ` Thomas Fjellstrom
2010-07-21 1:42 ` Thomas Fjellstrom
2010-07-21 3:05 ` Thomas Fjellstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1279267481.4164.4.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox