[Bug 105798] New: [Ci] igt at kms-* - fail - Failed assertion: __gem_create(fd, size, &handle) == 0 - igt_kms-WARNING: connector 52/VGA-1 has no modes - only on one shard, on one machine

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 105798
           Summary: [Ci] igt at kms-* - fail - Failed assertion:
                    __gem_create(fd, size, &handle) == 0 -
                    igt_kms-WARNING: connector 52/VGA-1 has no modes -
                    only on one shard, on one machine
           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: marta.lofstedt at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Starting at:

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4004/shard-snb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-gtt.html

(kms_frontbuffer_tracking:1331) ioctl_wrappers-CRITICAL: Test assertion failure
function gem_create, file ../lib/ioctl_wrappers.c:572:
(kms_frontbuffer_tracking:1331) ioctl_wrappers-CRITICAL: Failed assertion:
__gem_create(fd, size, &handle) == 0
(kms_frontbuffer_tracking:1331) ioctl_wrappers-CRITICAL: error: -22 != 0
Test kms_frontbuffer_tracking failed.

Note that
igt at kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-gtt has
always been skipped on this machine before.

Then shard-SNB4 has very odd results on shard 3.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4004/shard-snb4/igt@kms_vblank@pipe-a-wait-busy.html

(kms_vblank:1337) igt_kms-WARNING: connector 52/VGA-1 has no modes
(kms_vblank:1337) igt_kms-CRITICAL: Test assertion failure function
kmstest_dumb_create, file ../lib/igt_kms.c:610:
(kms_vblank:1337) igt_kms-CRITICAL: Failed assertion: igt_ioctl((fd),
((((2U|1U) << (((0+8)+8)+14)) | ((('d')) << (0+8)) | (((0xB2)) << 0) |
((((sizeof(struct drm_mode_create_dumb)))) << ((0+8)+8)))), (&create)) == 0
(kms_vblank:1337) igt_kms-CRITICAL: Last errno: 22, Invalid argument
(kms_vblank:1337) igt_kms-CRITICAL: error: -1 != 0
Subtest pipe-A-wait-busy failed.

Then on the following frontbuffer_tracking test we get:

(kms_frontbuffer_tracking:1391) ioctl_wrappers-CRITICAL: Test assertion failure
function gem_create, file ../lib/ioctl_wrappers.c:572:
(kms_frontbuffer_tracking:1391) ioctl_wrappers-CRITICAL: Failed assertion:
__gem_create(fd, size, &handle) == 0
(kms_frontbuffer_tracking:1391) ioctl_wrappers-CRITICAL: error: -22 != 0
Test kms_frontbuffer_tracking failed.

the last failing frontbuffer_tracking is:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4004/shard-snb4/igt@kms_frontbuffer_tracking@fbcpsrdrrs-1p-primscrn-pri-shrfb-draw-mmap-cpu.html

I see nothing obvious in dmesg.
On the shards after the machine has "normal" results.

This is good to check for which tests that was in this shard:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4004/shards.html

-- 
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: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180329/8a6af90f/attachment.html>