<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [IVB]igt/prime_nv_api cause WARNING: CPU: 6 PID: 4095 at drivers/gpu/drm/i915/i915_gem.c:3977 i915_gem_free_object+0xf3/0x19d [i915]()"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67391#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [IVB]igt/prime_nv_api cause WARNING: CPU: 6 PID: 4095 at drivers/gpu/drm/i915/i915_gem.c:3977 i915_gem_free_object+0xf3/0x19d [i915]()"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67391">bug 67391</a>
from <span class="vcard"><a class="email" href="mailto:guang.a.yang@intel.com" title="yangguang <guang.a.yang@intel.com>"> <span class="fn">yangguang</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=67391#c4">comment #4</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=67391#c3">comment #3</a>)
> > (In reply to <a href="show_bug.cgi?id=67391#c2">comment #2</a>)
> > > Fix merged to dinq:
> > >
> > > commit 48ca155d15d439d5d035a3daf1c56ed1a30afb17
> > > Author: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
> > > Date: Thu Aug 8 09:10:37 2013 +0200
> > >
> > > drm/i915: unpin backing storage in dmabuf_unmap
> > >
> > > This fixes a WARN in i915_gem_free_object when the
> > > obj->pages_pin_count isn't 0.
> > >
> > > v2: Add locking to unmap, noticed by Chris Wilson. Note that even
> > > though we call unmap with our own dev->struct_mutex held that won't
> > > result in an immediate deadlock since we never go through the dma_buf
> > > interfaces for our own, reimported buffers. But it's still easy to
> > > blow up and anger lockdep, but that's already the case with our ->map
> > > implementation. Fixing this for real will involve per dma-buf ww mutex
> > > locking by the callers. And lots of fun. So go with the duct-tape
> > > approach for now.
> > >
> > > Cc: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> > > Reported-by: Maarten Lankhorst <<a href="mailto:maarten.lankhorst@canonical.com">maarten.lankhorst@canonical.com</a>>
> > > Cc: Maarten Lankhorst <<a href="mailto:maarten.lankhorst@canonical.com">maarten.lankhorst@canonical.com</a>>
> > > Tested-by: Armin K. <<a href="mailto:krejzi@email.com">krejzi@email.com</a>> (v1)
> > > Acked-by: Maarten Lankhorst <<a href="mailto:maarten.lankhorst@canonical.com">maarten.lankhorst@canonical.com</a>>
> > > Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
> > The Call Trace issue disappears, but after running it shows:
> > Test requirement not met in function main, file prime_nv_api.c:522:
> > Test requirement: (intel_fd != -1)
> > Test requirement not met in function main, file prime_nv_api.c:523:
> > Test requirement: (intel_fd2 != -1)
> > DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
> > Assuming 131072kB available aperture size.
> > May lead to reduced performance or incorrect rendering.
> > get chip id failed: -1 [9]
> > param: 4, val: 0
> > Test assertion failure function main, file prime_nv_api.c:527:
> > Failed assertion: bufmgr
> > prime_nv_api: drmtest.c:816: igt_fail: Assertion `!test_with_subtests'
> > failed.
> >
> > So do I need to file a new bug?
>
> At least on a machine with intel graphics setting opening the intel kernel
> driver and setting up the bufmgr (which is what fails above) should never
> fail.
>
> If this is not a duplicate of <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - igt/prime_nv_api/i915_nv_double_export aborted"
href="show_bug.cgi?id=68166">bug #68166</a> (where nouveau isn't available and
> the test falls over) then I think we need a new bug report for this.</span >
I reported one new <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - igt/prime_nv_api cause Aborted (core dumped)"
href="show_bug.cgi?id=68253">bug #68253</a> to track this,It seems intel driver isn't
available so testcase failed.</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>