From: Chris Wilson <chris@chris-wilson.co.uk>
To: Marc MERLIN <marc_xorg@merlins.org>, intel-gfx@lists.freedesktop.org
Subject: Re: More crashes with intel driver 1.10.4 and corrupted stack traces for GM45
Date: Tue, 13 Dec 2011 23:16:17 +0000 [thread overview]
Message-ID: <f80fcd$2rco5p@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <20111213221318.GC11838@merlins.org>
On Tue, 13 Dec 2011 14:13:18 -0800, Marc MERLIN <marc_xorg@merlins.org> wrote:
> On Sun, Dec 11, 2011 at 12:32:00PM -0800, Marc MERLIN wrote:
> > Hi Eugeni and other folks on this list,
>
> Am I sending this to the wrong place or is GM45 unsupported?
Apologies, it is a known issue. I was thrown by the bizarre stack trace,
but it seems like it just the mmap failure blowing up in spectacular
fashion. The ENOSPC issues arises from when we have either exhausted
or badly fragmented the (on your system presumably) 32-bits of address
space for GTT mappings such that we are no longer able to allocate new
ones. I have recently begun to take a similar issue whereby we exhausted
the per-process map limit with over 65,000 vma keep open. The solution
there of capping the number of cached vma is likely to resolve this
problem as well.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2011-12-13 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 20:32 More crashes with intel driver 1.10.4 and corrupted stack traces for GM45 Marc MERLIN
2011-12-13 22:13 ` Marc MERLIN
2011-12-13 23:04 ` Daniel Vetter
2011-12-14 3:05 ` Marc MERLIN
2011-12-14 8:36 ` Chris Wilson
2011-12-26 23:15 ` intel_drv 2.17.0 hangs X at boot while 2.15.901 works but crashes (GM45) Marc MERLIN
2012-01-01 21:40 ` Marc MERLIN
2011-12-13 23:16 ` Chris Wilson [this message]
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='f80fcd$2rco5p@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marc_xorg@merlins.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