<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@drv_selftest@live_gtt - incomplete - oom_reaper: reaped process 6772 (python3), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB" href="https://bugs.freedesktop.org/show_bug.cgi?id=103718#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@drv_selftest@live_gtt - incomplete - oom_reaper: reaped process 6772 (python3), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB" href="https://bugs.freedesktop.org/show_bug.cgi?id=103718">bug 103718</a> from <a class="email" href="mailto:marta.lofstedt@intel.com" title="Marta Löfstedt <marta.lofstedt@intel.com>"> Marta Löfstedt</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=103718#c1">comment #1</a>) > Only seen once so far (I think at least), it looks to be a kernel leak. At > the moment, the obvious thing to do is a run with kmemleak, but my initial > guess is that it's a result of early fail not cleaning up properly. The > modules allocations (such as drm_mm, kmem_cache etc) are checked upon module > unload (and kselftest) but no warning seen, hence the search for something a > little more unusual. This incomplete is pretty frequent on APL, but due to ftrace messing up pstore and the recent 4.15.0-rc1 fire, we'll have to wait and see if we can get any reasonable data on this.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>