public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc_xorg@merlins.org>
To: Daniel Vetter <daniel@ffwll.ch>, Chris Wilson <chris@chris-wilson.co.uk>
Cc: 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 19:05:34 -0800	[thread overview]
Message-ID: <20111214030534.GA411@merlins.org> (raw)
In-Reply-To: <f80fcd$2rco5p@fmsmga001.fm.intel.com> <20111213230402.GC18675@phenom.ffwll.local>

On Wed, Dec 14, 2011 at 12:04:03AM +0100, Daniel Vetter wrote:
> > > One of my X logs had some of these:
> > > [1535818.200] (WW) intel(0): intel_uxa_prepare_access: bo map failed: No space left on device
> > > [1535818.208] (WW) intel(0): intel_uxa_prepare_access: bo map failed: No space left on device
> > > [1535818.208] (WW) intel(0): intel_uxa_prepare_access: bo map failed: No space left on device
> 
> This one sounds like a vma exhausting issue Chris Wilson recently fixed.
> Please retest with the latest versions of xf86-video-intel and libdrm from
> git.

On Tue, Dec 13, 2011 at 11:16:17PM +0000, Chris Wilson wrote:
> 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.

Since I'm a newbie at thie, there isn't a 'head' per se, and I see that
not all patches are production ready.
Could you point me on what I could sync from and that would be
reasonably likely to work? :)

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/

  reply	other threads:[~2011-12-14  3:05 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 [this message]
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   ` More crashes with intel driver 1.10.4 and corrupted stack traces for GM45 Chris Wilson

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=20111214030534.GA411@merlins.org \
    --to=marc_xorg@merlins.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --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