From: Knut Petersen <Knut_Petersen@t-online.de>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: bo problem, file-max limit reached within two days
Date: Mon, 02 Apr 2012 10:36:44 +0200 [thread overview]
Message-ID: <4F79651C.7050407@t-online.de> (raw)
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
[156869.197310] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[156870.008424] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[156871.268130] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[156872.988325] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[156879.187113] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[156880.046793] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[156898.079853] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170448.897871] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170449.982378] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170450.399949] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170451.999312] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170458.007902] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170458.795343] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170756.249755] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170756.572389] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170769.156889] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170769.392065] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170770.703797] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170772.407662] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170779.460247] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170788.713283] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170795.466570] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170796.491909] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170798.477484] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170804.722188] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[170805.534740] [drm:drm_gem_create_mmap_offset] *ERROR* failed to allocate offset for bo 0
[179417.374016] VFS: file-max limit 204863 reached
[179418.373995] VFS: file-max limit 204863 reached
[179419.373969] VFS: file-max limit 204863 reached
[179420.373982] VFS: file-max limit 204863 reached
[179422.373995] VFS: file-max limit 204863 reached
[179423.374002] VFS: file-max limit 204863 reached
[179425.373970] VFS: file-max limit 204863 reached
[179427.404335] VFS: file-max limit 204863 reached
[179428.373994] VFS: file-max limit 204863 reached
[179429.373992] VFS: file-max limit 204863 reached
[179430.381375] VFS: file-max limit 204863 reached
[179431.374017] VFS: file-max limit 204863 reached
[179432.380678] VFS: file-max limit 204863 reached
[179433.373972] VFS: file-max limit 204863 reached
[179434.385198] VFS: file-max limit 204863 reached
[179435.374010] VFS: file-max limit 204863 reached
[179437.373992] VFS: file-max limit 204863 reached
[179438.373992] VFS: file-max limit 204863 reached
[179440.374007] VFS: file-max limit 204863 reached
[179442.420661] VFS: file-max limit 204863 reached
[179443.373989] VFS: file-max limit 204863 reached
[179444.373998] VFS: file-max limit 204863 reached
[179445.394205] VFS: file-max limit 204863 reached
[179446.373974] VFS: file-max limit 204863 reached
[179447.395051] VFS: file-max limit 204863 reached
[179448.373964] VFS: file-max limit 204863 reached
[179449.402791] VFS: file-max limit 204863 reached
[179450.373994] VFS: file-max limit 204863 reached
[179452.374004] VFS: file-max limit 204863 reached
[179453.374010] VFS: file-max limit 204863 reached
[179455.374067] VFS: file-max limit 204863 reached
[179455.797582] VFS: file-max limit 204863 reached
[179472.450203] VFS: file-max limit 204863 reached
[179473.373970] VFS: file-max limit 204863 reached
[179474.374087] VFS: file-max limit 204863 reached
[179475.424852] VFS: file-max limit 204863 reached
[179476.401695] VFS: file-max limit 204863 reached
[179477.427067] VFS: file-max limit 204863 reached
[179478.398170] VFS: file-max limit 204863 reached
[179479.425794] VFS: file-max limit 204863 reached
[179480.373985] VFS: file-max limit 204863 reached
[179482.374007] VFS: file-max limit 204863 reached
[179483.373988] VFS: file-max limit 204863 reached
[179485.373987] 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.
Any idea?
cu,
Knut
next reply other threads:[~2012-04-02 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 8:36 Knut Petersen [this message]
2012-04-02 8:44 ` bo problem, file-max limit reached within two days Chris Wilson
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=4F79651C.7050407@t-online.de \
--to=knut_petersen@t-online.de \
--cc=chris@chris-wilson.co.uk \
--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.