<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [HD Graphics 4000] Segfault accessing rq->bo->handle"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91577#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [HD Graphics 4000] Segfault accessing rq->bo->handle"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91577">bug 91577</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to Dominic from <a href="show_bug.cgi?id=91577#c19">comment #19</a>)
<span class="quote">> The patches change the segfault but cannot prevent it. The segault I just
> got did not yield a meaningful backtrace, however. (heap corruption?)
>
> [ 365.632] kgem_cleanup_cache
> [ 365.632] kgem_cleanup_cache: sync on cleanup
> [ 365.632] __kgem_retire_requests_upto(handle=2)
> [ 365.632] __kgem_retire_rq: request 2 complete
> [ 365.632] kgem_retire, need_retire?=1
> [ 365.632] __kgem_busy: handle=17, busy=1, wedged=0
> [ 365.632] kgem_retire__flushing: 18 bo on flushing list
> [ 365.632] kgem_retire__requests_ring: ring=0, 0 outstanding requests,
> oldest=0
> [ 365.632] __kgem_busy: handle=3, busy=1, wedged=0
> [ 365.632] kgem_retire__requests_ring: ring=1, 2 outstanding requests,
> oldest=3
> [ 365.632] kgem_retire -- retired=0, need_retire=1
> [ 365.632] kgem_bo_is_busy: handle=64390, domain: 0 exec? 0, rq? 0
> [ 365.632] gen6_render_retire: resetting idle vbo
> [ 365.632] __kgem_bo_clear_busy: handle=3
> [ 365.632] __kgem_bo_clear_busy: handle=65024
> [ 365.632] kgem_cleanup_cache: need_expire?=0
> [ 365.632] __kgem_bo_map__cpu: failed to mmap handle=64326 (prime? 0),
> 65536 bytes, into CPU domain: 12
> [ 365.632] kgem_new_batch: unable to map batch bo, mallocing(size=65536)
> [ 365.632] _kgem_bo_destroy: handle=64326, proxy? 0
> [ 365.632] __kgem_bo_destroy: handle=64326, size=65536
> [ 365.632] __kgem_bo_destroy: handle=64326, purged
> [ 365.632] kgem_bo_move_to_inactive: moving handle=64326 to inactive</span >
Hmm. That's an odd place for the log to stop. I've tweaked the DBG statements,
maybe that will be clearer?
(In reply to Dominic from <a href="show_bug.cgi?id=91577#c20">comment #20</a>)
<span class="quote">> Xorg reaches ~20% MEM at the time of crash - that should be about 4GiB. How
> can I see the object count reliably?</span >
cat /sys/kernel/debug/dri/0/i915_gem_objects</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>