Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Knut Petersen <Knut_Petersen@t-online.de>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: bo problem, file-max limit reached within two days
Date: Mon, 02 Apr 2012 09:44:47 +0100	[thread overview]
Message-ID: <1333356312_198045@CP5-2952> (raw)
In-Reply-To: <4F79651C.7050407@t-online.de>

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

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-04-02  8:45 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 [this message]
2012-04-12  7:55   ` Knut Petersen
2012-04-12  8:03     ` Daniel Vetter
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=1333356312_198045@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --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