Attachment 123709 Details for Bug 95387 – kbl_output_bo-too-big

kbl_output_bo-too-big

kbl_output_bo-too-big.txt (text/plain), 3.56 KB, created by cprigent on 2016-05-13 16:59:47 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: cprigent

Created: 2016-05-13 16:59:47 UTC

Size: 3.56 KB

patch

obsolete

># ./kms_flip --run-subtest bo-too-big
>IGT-Version: 1.14-NOT-GIT (x86_64) (Linux: 4.6.0-rc7-nightly+ x86_64)
>Using monotonic timestamps
>Beginning bo-too-big on pipe A, connector eDP-1
>  3200x1800 60 3200 3248 3280 3316 1800 1802 1807 1816 0xa 0x48 361310
>(kms_flip:1397) CRITICAL: Test assertion failure function run_test_on_crtc_set, file kms_flip.c:1396:
>(kms_flip:1397) CRITICAL: Failed assertion: do_page_flip(o, o->fb_ids[1], 1) == -7
>(kms_flip:1397) CRITICAL: error: 0 != -7
>Stack trace:
>  #0 [__igt_fail_assert+0xf1]
>  #1 [run_test_on_crtc_set.constprop.12+0x63e]
>  #2 [run_test+0x25a]
>  #3 [main+0x508]
>  #4 [__libc_start_main+0xf0]
>  #5 [_start+0x29]
>  #6 [<unknown>+0x29]
>Subtest bo-too-big failed.
>**** DEBUG ****
>(kms_flip:1397) DEBUG: Test requirement passed: (flags & TEST_HANG) == 0 || !is_wedged(drm_fd)
>(kms_flip:1397) DEBUG: Test requirement passed: modes
>(kms_flip:1397) INFO: Beginning bo-too-big on pipe A, connector eDP-1
>(kms_flip:1397) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=3200, height=1800, format=0x34325258, tiling=0x0, size=0)
>(kms_flip:1397) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=2, pitch=12800)
>(kms_flip:1397) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=3200, height=1800, format=0x34325258, tiling=0x0, size=1073741824)
>(kms_flip:1397) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=3, pitch=12800)
>(kms_flip:1397) igt-kms-INFO:   3200x1800 60 3200 3248 3280 3316 1800 1802 1807 1816 0xa 0x48 361310
>(kms_flip:1397) CRITICAL: Test assertion failure function run_test_on_crtc_set, file kms_flip.c:1396:
>(kms_flip:1397) CRITICAL: Failed assertion: do_page_flip(o, o->fb_ids[1], 1) == -7
>(kms_flip:1397) CRITICAL: error: 0 != -7
>****  END  ****
>Subtest bo-too-big: FAIL (1,102s)
>root@KBLU1:/opt/X11R7/src/intel-gpu-tools/tests# ./kms_flip --run-subtest bo-too-big-interruptible
>IGT-Version: 1.14-NOT-GIT (x86_64) (Linux: 4.6.0-rc7-nightly+ x86_64)
>Using monotonic timestamps
>Beginning bo-too-big-interruptible on pipe A, connector eDP-1
>  3200x1800 60 3200 3248 3280 3316 1800 1802 1807 1816 0xa 0x48 361310
>(kms_flip:1447) CRITICAL: Test assertion failure function run_test_on_crtc_set, file kms_flip.c:1396:
>(kms_flip:1447) CRITICAL: Failed assertion: do_page_flip(o, o->fb_ids[1], 1) == -7
>(kms_flip:1447) CRITICAL: error: 0 != -7
>Stack trace:
>  #0 [__igt_fail_assert+0xf1]
>  #1 [run_test_on_crtc_set.constprop.12+0x63e]
>  #2 [run_test+0x25a]
>  #3 [main+0x540]
>  #4 [__libc_start_main+0xf0]
>  #5 [_start+0x29]
>  #6 [<unknown>+0x29]
>Subtest bo-too-big-interruptible failed.
>**** DEBUG ****
>(kms_flip:1447) DEBUG: Test requirement passed: (flags & TEST_HANG) == 0 || !is_wedged(drm_fd)
>(kms_flip:1447) DEBUG: Test requirement passed: modes
>(kms_flip:1447) INFO: Beginning bo-too-big-interruptible on pipe A, connector eDP-1
>(kms_flip:1447) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=3200, height=1800, format=0x34325258, tiling=0x0, size=0)
>(kms_flip:1447) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=2, pitch=12800)
>(kms_flip:1447) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=3200, height=1800, format=0x34325258, tiling=0x0, size=1073741824)
>(kms_flip:1447) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=3, pitch=12800)
>(kms_flip:1447) igt-kms-INFO:   3200x1800 60 3200 3248 3280 3316 1800 1802 1807 1816 0xa 0x48 361310
>(kms_flip:1447) CRITICAL: Test assertion failure function run_test_on_crtc_set, file kms_flip.c:1396:
>(kms_flip:1447) CRITICAL: Failed assertion: do_page_flip(o, o->fb_ids[1], 1) == -7
>(kms_flip:1447) CRITICAL: error: 0 != -7
>****  END  ****
>Subtest bo-too-big-interruptible: FAIL (1,144s)

Actions: View

Attachments on bug 95387: 123709 | 123710 | 123902 | 123903

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.