| Summary: | [CI][SHARDS]igt@gem_exec_reuse@contexts - incomplete - Out of memory | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | high | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | SKL | i915 features: | GEM/Other |
|
Description
Lakshmi
2019-10-01 10:54:57 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * SKL: igt@gem_exec_reuse@contexts - incomplete - Out of memory - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6977/shard-skl9/igt@gem_exec_reuse@contexts.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6978/shard-skl7/igt@gem_exec_reuse@contexts.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-skl10/igt@gem_exec_reuse@contexts.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14594/shard-skl6/igt@gem_exec_reuse@contexts.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14598/shard-skl6/igt@gem_exec_reuse@contexts.html We've disabled kmemleak from normal builds (i.e. should still be enabled for kasan; check with Tomi for precise details or check the kconfig of the relevant run). Bisect ongoing as to how/why it suddenly exploded memusage wise. ickle@broadwell:~/linux$ git bisect bad c5665868183fec689dbab9fb8505188b2c4f0757 is the first bad commit commit c5665868183fec689dbab9fb8505188b2c4f0757 Author: Catalin Marinas <catalin.marinas@arm.com> Date: Mon Sep 23 15:34:05 2019 -0700 mm: kmemleak: use the memory pool for early allocations Currently kmemleak uses a static early_log buffer to trace all memory allocation/freeing before the slab allocator is initialised. Such early log is replayed during kmemleak_init() to properly initialise the kmemleak metadata for objects allocated up that point. With a memory pool that does not rely on the slab allocator, it is possible to skip this early log entirely. In order to remove the early logging, consider kmemleak_enabled == 1 by default while the kmem_cache availability is checked directly on the object_cache and scan_area_cache variables. The RCU callback is only invoked after object_cache has been initialised as we wouldn't have any concurrent list traversal before this. In order to reduce the number of callbacks before kmemleak is fully initialised, move the kmemleak_init() call to mm_init(). [akpm@linux-foundation.org: coding-style fixes] [akpm@linux-foundation.org: remove WARN_ON(), per Catalin] Link: http://lkml.kernel.org/r/20190812160642.52134-4-catalin.marinas@arm.com Signed-off-by: Catalin Marinas <catalin.marinas@arm.com> Cc: Matthew Wilcox <willy@infradead.org> Cc: Michal Hocko <mhocko@kernel.org> Cc: Qian Cai <cai@lca.pw> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Reverts cleanly, but still ooms. Hmm, maybe taken a wrong turn in bisecting. Fwiw, disabling kmemleak had the desired effected in preventing the incompletes during shard runs. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/471. |
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.