<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@gem_ppgtt@blt-vs-render-ctxn - incomplete - gem_ppgtt: page allocation failure: order:0, mode:0x14204d2(GFP_HIGHUSER|__GFP_RETRY_MAYFAIL|__GFP_RECLAIMABLE), nodemask=(null)" href="https://bugs.freedesktop.org/show_bug.cgi?id=104011#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@gem_ppgtt@blt-vs-render-ctxn - incomplete - gem_ppgtt: page allocation failure: order:0, mode:0x14204d2(GFP_HIGHUSER|__GFP_RETRY_MAYFAIL|__GFP_RECLAIMABLE), nodemask=(null)" href="https://bugs.freedesktop.org/show_bug.cgi?id=104011">bug 104011</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=104011#c2">comment #2</a>) > What is not so happy is the > > <4>[ 193.388010] hpet1: lost 7161 rtc interrupts > > A dead timer. That would explain why we never were able to retire requests > and so leaked everything, and everything remained marked as busy. No, it doesn't. If we thought everything was still active, we would not have filled swap (only inactive bo can be swapped). Which brings us back to a bo leak, but whose?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>