Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: bo problem, file-max limit reached within two days
Date: Thu, 12 Apr 2012 10:03:52 +0200	[thread overview]
Message-ID: <20120412080352.GD3705@phenom.ffwll.local> (raw)
In-Reply-To: <4F868A5F.6070502@t-online.de>

On Thu, Apr 12, 2012 at 09:55:11AM +0200, Knut Petersen wrote:
> Am 02.04.2012 10:44, schrieb Chris Wilson:
> >On Mon, 02 Apr 2012 10:36:44 +0200, Knut Petersen<Knut_Petersen@t-online.de>  wrote:
> >>After a few unattended hours Xorg was still running,
> >>but only a terminal window had survived the night :-(
> >>
> >>Xorg: git, a few days old, kernel: 3.3.
> >>
> >>Xorg.0.log: Nothing unusual
> >>
> >>dmesg:
> >>
> >>[156859.078080] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
> >>[179417.374016] VFS: file-max limit 204863 reached
> >>
> >>I built a new X server and tried kernel 3.2.12 - that does not seem to help as
> >>both the number of open files  and the number of gem objects still grow without
> >>obvious reasons.
> >It's the EFILE that is truly worrying. We have a patch in the queue to
> >help ease the ENOSPC issue, but the EFILE implies a bo reference leak.
> >And that I have not found yet.
> >
> >Happy hunting,
> >-Chris
> >
> 
> Well, it takes more than two days to trigger the EFILE limit here, but yesterday
> the ENOSPC bo problem appeared 6.5 hours after booting the system with current
> Xorg git and kernel 3.3.1. I wonder if this is one problem or if we face two independent bugs.

Can you try the drm-intel-next-queued branch from my git repo at

http://cgit.freedesktop.org/~danvet/drm-intel/

That contains a patch from Chris Wilson to mitigate mmio offset
exhaustion, one possible reason for a -ENOSPC failure.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-04-12  8:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02  8:36 bo problem, file-max limit reached within two days Knut Petersen
2012-04-02  8:44 ` Chris Wilson
2012-04-12  7:55   ` Knut Petersen
2012-04-12  8:03     ` Daniel Vetter [this message]
2012-04-12 12:50       ` Knut Petersen
2012-04-12  8:06     ` 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=20120412080352.GD3705@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=Knut_Petersen@t-online.de \
    --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