[Bug 67391] [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]()

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Aug 18 22:06:36 PDT 2013


https://bugs.freedesktop.org/show_bug.cgi?id=67391

--- Comment #5 from yangguang <guang.a.yang at intel.com> ---
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Fix merged to dinq:
> > > 
> > > commit 48ca155d15d439d5d035a3daf1c56ed1a30afb17
> > > Author: Daniel Vetter <daniel.vetter at ffwll.ch>
> > > 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 <chris at chris-wilson.co.uk>
> > >     Reported-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
> > >     Cc: Maarten Lankhorst <maarten.lankhorst at canonical.com>
> > >     Tested-by: Armin K. <krejzi at email.com> (v1)
> > >     Acked-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
> > >     Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>
> > 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 bug #68166 (where nouveau isn't available and
> the test falls over) then I think we need a new bug report for this.

I reported one new bug #68253 to track this,It seems intel driver isn't
available so testcase failed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130819/8ed87e5e/attachment-0001.html>


More information about the intel-gfx-bugs mailing list