[Bug 89051] New: [SNG]igt/gem_reloc_vs_gpu/faulting-reloc-interruptible-hang fail.

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Feb 9 19:16:42 PST 2015


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

            Bug ID: 89051
           Summary: [SNG]igt/gem_reloc_vs_gpu/faulting-reloc-interruptible
                    -hang fail.
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: hengx.ding at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 113292
  --> https://bugs.freedesktop.org/attachment.cgi?id=113292&action=edit
dmesg

==System Environment==
--------------------------
Regression: no, This is a new issue.

no-working platforms: SNB
==kernel==
--------------------------
drm-intel-nightly-2015-02-10/ad95125eaef18eebb9f47261ce3c99957f5953de

==Bug detailed description==
./gem_reloc_vs_gpu  --run-subtest faulting-reloc-interruptible-hang
IGT-Version: 1.9-gbef692d (x86_64) (Linux:
3.19.0_drm-intel-nightly_ad9512_20150210+ x86_64)
(gem_reloc_vs_gpu:4073) CRITICAL: Test assertion failure function do_test, file
gem_reloc_vs_gpu.c:240:
(gem_reloc_vs_gpu:4073) CRITICAL: Failed assertion: test == 0xdeadbeef
(gem_reloc_vs_gpu:4073) CRITICAL: mismatch in buffer 0: 0x00000000 instead of
0xdeadbeef
Subtest faulting-reloc-interruptible-hang: FAIL (104.713s)



==Reproduce steps==
---------------------------- 
1. ./gem_reloc_vs_gpu --run-subtest faulting-reloc-interruptible-hang

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


More information about the intel-gfx-bugs mailing list