Summary: | X crash: intel(0): Failed to submit rendering commands (Cannot allocate memory), disabling acceleration. | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | David Biesack <David.Biesack> | ||||||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||
Severity: | normal | ||||||||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||||||||
Version: | XOrg git | ||||||||||||||
Hardware: | Other | ||||||||||||||
OS: | All | ||||||||||||||
Whiteboard: | |||||||||||||||
i915 platform: | i915 features: | ||||||||||||||
Attachments: |
|
Description
David Biesack
2016-02-11 14:58:31 UTC
System ran out of memory, and malloc failed - obviously one is unguarded. More interesting would be the full Xorg.0.log, cat /sys/kernel/debug/dri/0/i915_gem_objects and xrestop after a day or so of uptime. Created attachment 121709 [details]
/var/log/Xorg.0.log.old leading up to latest X crash
Created attachment 121710 [details]
xrestop.log
output of xrestop -b -m 0
after X has been up for a short while (few hours)
Created attachment 121725 [details]
xrestop -b -m 1
Latest output of
xrestop -b -m 1
Server has now been running
Created attachment 121726 [details]
/sys/kernel/debug/dri/0/i915_gem_objects
Content of /sys/kernel/debug/dri/0/i915_gem_objects file
also after the X server has been up and running for 6+ hours
conky is reporting "Mem 8.25GiB of 15.6GiB (53%)"
via the .conkyrc line "Mem $mem of $memmax ($memperc%)"
That looks consistent with commit 2d26643cab33a32847afaf13b50d326d09d58bf7 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Nov 13 19:03:36 2015 +0000 sna/dri2: Drop the reference on the fence when complete Fixes regression from commit 8d9e496670f48b4eec64dfe1bcedb49793cf3073 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Jul 22 11:14:01 2015 +0100 sna/dri2: Take over the placeholder vblank After noting the fence was complete, we would clear it. But I forgot that we actually held a reference on to it, and so we would leak the 64k batch, and starve the system of available memory in about 18 minutes of SwapBuffers. Reported-by: Arkadiusz Miskiewicz <arekm@maven.pl> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92911 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> *** This bug has been marked as a duplicate of bug 92911 *** |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.