From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: bo problem, file-max limit reached within two days Date: Thu, 12 Apr 2012 10:03:52 +0200 Message-ID: <20120412080352.GD3705@phenom.ffwll.local> References: <4F79651C.7050407@t-online.de> <1333356312_198045@CP5-2952> <4F868A5F.6070502@t-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by gabe.freedesktop.org (Postfix) with ESMTP id 95EE19E70A for ; Thu, 12 Apr 2012 01:03:00 -0700 (PDT) Received: by wibhj13 with SMTP id hj13so3987949wib.12 for ; Thu, 12 Apr 2012 01:02:59 -0700 (PDT) Content-Disposition: inline In-Reply-To: <4F868A5F.6070502@t-online.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Knut Petersen Cc: intel-gfx List-Id: intel-gfx@lists.freedesktop.org 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 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