Summary: | [CI][SHARDS] igt@gem_exec_reuse@baggage - dmesg-warn - ODEBUG: Out of memory. ODEBUG disabled | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | high | CC: | intel-gfx-bugs |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | BXT | i915 features: | GEM/Other |
Description
Martin Peres
2018-11-07 15:13:09 UTC
I get the feeling that rc1 brought in a slew of new debugobject users, too many for the debugobject preallocation to handle. The current preallocation code dates from Feb 2018 so unlikely to be behind the recent discovery. I wonder if we've enabled rcu debug objects recently. That ties in with the recent reports for untracked rcu objects on what seems to be an old problem. Something else to note is that the debugobject preallocation is done in debug_object_init, and so if we have not been calling them for our obj->rcu that's a lot of debugobjects being allocated without any preallocation! commit 8811d616dfaa8c6e1905a20ce0543ec401275997 (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Nov 9 09:03:11 2018 +0000 drm/i915: Initialise the obj->rcu head Make the rcu_head known to the system, in particular for debugobjects. And having declared it for debugobjects, we need to tidy up afterwards. v2: mark the obj->rcu as being destroyed when we reuse its location for the freed list. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108691 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20181109090311.15321-1-chris@chris-wilson.co.uk This indeed fixed it, thanks! |
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.