From: Knut Petersen <Knut_Petersen@t-online.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: bo problem, file-max limit reached within two days
Date: Thu, 12 Apr 2012 14:50:32 +0200 [thread overview]
Message-ID: <4F86CF98.5080006@t-online.de> (raw)
In-Reply-To: <20120412080352.GD3705@phenom.ffwll.local>
Am 12.04.2012 10:03, schrieb Daniel Vetter:
> 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
It´s a short time for a test, but drm-intel-next-queued does not look better than other kernels:
date; cat /proc/sys/fs/file-nr; cat /sys/kernel/debug/dri/0/i915_gem_objects
Do 12. Apr 13:21:50 CEST 2012
9323 0 204854
1275 objects, 81797120 bytes
1251 [1251] objects, 84410368 [84410368] bytes in gtt
19 [19] active objects, 11051008 [11051008] bytes
2 [2] pinned objects, 5373952 [5373952] bytes
1230 [1230] inactive objects, 67985408 [67985408] bytes
0 [0] freed objects, 0 [0] bytes
3 pinned mappable objects, 13762560 bytes
786 fault mappable objects, 16318464 bytes
268435456 [268435456] gtt total
Do 12. Apr 14:09:41 CEST 2012
12387 0 204854
4317 objects, 82264064 bytes
4282 [4282] objects, 84713472 [84713472] bytes in gtt
15 [15] active objects, 11304960 [11304960] bytes
2 [2] pinned objects, 5373952 [5373952] bytes
4265 [4265] inactive objects, 68034560 [68034560] bytes
0 [0] freed objects, 0 [0] bytes
3 pinned mappable objects, 13762560 bytes
3809 fault mappable objects, 27975680 bytes
268435456 [268435456] gtt total
Do 12. Apr 14:47:18 CEST 2012
15616 0 204854
7015 objects, 148389888 bytes
905 [905] objects, 73834496 [73834496] bytes in gtt
15 [15] active objects, 11304960 [11304960] bytes
2 [2] pinned objects, 5373952 [5373952] bytes
888 [888] inactive objects, 57155584 [57155584] bytes
0 [0] freed objects, 0 [0] bytes
3 pinned mappable objects, 13762560 bytes
699 fault mappable objects, 13668352 bytes
268435456 [268435456] gtt total
Files, total number of objects, inactive objects and fault mappable objects raise at a rate comparable
to kernels 3.3.1, 3.2.* and 3.1*.
I searched about 15 months of log files - both error messages appeared for the first time about 14 days ago.
Kernel 3.2 is much older, and the system survived _much_ longer uptimes previously. Either it´s not a kernel problem,
or that kernel problem is exposed by some recent (max 6 weeks) change in Xorg, KDE, ... etc. Unfortunately there were
a lot of changes in that time.
cu,
Knut
next prev parent reply other threads:[~2012-04-12 12:50 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
2012-04-12 12:50 ` Knut Petersen [this message]
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=4F86CF98.5080006@t-online.de \
--to=knut_petersen@t-online.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.