[Bug 81704] [BYT Bisected]igt/kms_pipe_crc_basic causes system hang
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 11 22:02:47 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=81704
Guo Jinxian <jinxianx.guo at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--- Comment #8 from Guo Jinxian <jinxianx.guo at intel.com> ---
Verified on latest -nightly(907d7b0519abe7b8eac453089decfe0fc5049171)
root at x-bytm02:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time
./kms_pipe_crc_basic
IGT-Version: 1.8-g107151c (x86_64) (Linux:
3.17.0-rc4_drm-intel-nightly_907d7b_20140912+ x86_64)
Subtest bad-pipe: SUCCESS (0.000s)
Subtest bad-source: SUCCESS (0.000s)
Subtest bad-nb-words-1: SUCCESS (0.000s)
Subtest bad-nb-words-3: SUCCESS (0.000s)
read-crc-pipe-A: Testing connector eDP-1 using pipe A
read-crc-pipe-A: Testing connector VGA-1 using pipe A
Subtest read-crc-pipe-A: SUCCESS (6.653s)
read-crc-pipe-A-frame-sequence: Testing connector eDP-1 using pipe A
Test assertion failure function test_read_crc_for_output, file
kms_pipe_crc_basic.c:188:
Failed assertion: igt_crc_equal(&crcs[j], &crcs[j + 1])
Subtest read-crc-pipe-A-frame-sequence: FAIL (5.516s)
rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Sep 12 20:30:50 2014
suspend-read-crc-pipe-A: Testing connector eDP-1 using pipe A
Test assertion failure function igt_pipe_crc_new, file igt_debugfs.c:384:
Failed assertion: pipe_crc->crc_fd != -1
Last errno: 16, Device or resource busy
Subtest suspend-read-crc-pipe-A: FAIL (4.136s)
hang-read-crc-pipe-A: Testing connector eDP-1 using pipe A
Test assertion failure function igt_pipe_crc_new, file igt_debugfs.c:384:
Failed assertion: pipe_crc->crc_fd != -1
Last errno: 16, Device or resource busy
Subtest hang-read-crc-pipe-A: FAIL (6.747s)
read-crc-pipe-B: Testing connector eDP-1 using pipe B
Test assertion failure function test_read_crc_for_output, file
kms_pipe_crc_basic.c:188:
Failed assertion: igt_crc_equal(&crcs[j], &crcs[j + 1])
Subtest read-crc-pipe-B: FAIL (27.501s)
read-crc-pipe-B-frame-sequence: Testing connector eDP-1 using pipe B
Test assertion failure function igt_pipe_crc_new, file igt_debugfs.c:384:
Failed assertion: pipe_crc->crc_fd != -1
Last errno: 16, Device or resource busy
Subtest read-crc-pipe-B-frame-sequence: FAIL (0.583s)
rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Sep 12 20:31:59 2014
suspend-read-crc-pipe-B: Testing connector eDP-1 using pipe B
Test assertion failure function igt_pipe_crc_new, file igt_debugfs.c:384:
Failed assertion: pipe_crc->crc_fd != -1
Last errno: 16, Device or resource busy
Subtest suspend-read-crc-pipe-B: FAIL (21.517s)
hang-read-crc-pipe-B: Testing connector eDP-1 using pipe B
Test assertion failure function igt_pipe_crc_new, file igt_debugfs.c:384:
Failed assertion: pipe_crc->crc_fd != -1
Last errno: 16, Device or resource busy
Subtest hang-read-crc-pipe-B: FAIL (6.413s)
Test requirement not met in function test_read_crc, file
kms_pipe_crc_basic.c:211:
Test requirement: !(pipe >= data->display.n_pipes)
Last errno: 16, Device or resource busy
Subtest read-crc-pipe-C: SKIP (0.000s)
Test requirement not met in function test_read_crc, file
kms_pipe_crc_basic.c:211:
Test requirement: !(pipe >= data->display.n_pipes)
Last errno: 16, Device or resource busy
Subtest read-crc-pipe-C-frame-sequence: SKIP (0.000s)
rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Sep 12 20:32:57 2014
Test requirement not met in function test_read_crc, file
kms_pipe_crc_basic.c:211:
Test requirement: !(pipe >= data->display.n_pipes)
Last errno: 16, Device or resource busy
Subtest suspend-read-crc-pipe-C: SKIP (10.694s)
Test requirement not met in function test_read_crc, file
kms_pipe_crc_basic.c:211:
Test requirement: !(pipe >= data->display.n_pipes)
Subtest hang-read-crc-pipe-C: SKIP (5.700s)
real 3m10.666s
user 0m0.080s
sys 0m0.561s
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140912/a5aaede2/attachment.html>
More information about the intel-gfx-bugs
mailing list