From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Ro.CI.BAT: warning for RFC: hot-unplug safe connector list locking
Date: Tue, 21 Jun 2016 10:28:53 -0000 [thread overview]
Message-ID: <20160621102853.12986.26007@emeril.freedesktop.org> (raw)
In-Reply-To: <1466500235-21282-1-git-send-email-daniel.vetter@ffwll.ch>
== Series Details ==
Series: RFC: hot-unplug safe connector list locking
URL : https://patchwork.freedesktop.org/series/8974/
State : warning
== Summary ==
Series 8974v1 RFC: hot-unplug safe connector list locking
http://patchwork.freedesktop.org/api/1.0/series/8974/revisions/1/mbox
Test gem_ctx_basic:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Test gem_ctx_create:
Subgroup basic:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Subgroup basic-files:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Test gem_ctx_switch:
Subgroup basic-default:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Test gem_storedw_loop:
Subgroup basic-blt:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Subgroup basic-bsd:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Subgroup basic-vebox:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Test gem_sync:
Subgroup basic-all:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Subgroup basic-each:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Test gem_tiled_fence_blits:
Subgroup basic:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Test gem_tiled_pread_basic:
pass -> DMESG-WARN (ro-hsw-i3-4010u)
Test kms_flip:
Subgroup basic-flip-vs-wf_vblank:
fail -> PASS (ro-snb-i7-2620M)
Test kms_force_connector_basic:
Subgroup force-connector-state:
pass -> DMESG-WARN (ro-ivb2-i7-3770)
pass -> DMESG-WARN (ro-ilk1-i5-650)
pass -> DMESG-WARN (ro-snb-i7-2620M)
Test kms_pipe_crc_basic:
Subgroup suspend-read-crc-pipe-c:
pass -> SKIP (ro-bdw-i7-5557U)
Test kms_sink_crc_basic:
pass -> DMESG-WARN (ro-bdw-i7-5600u)
fi-skl-i5-6260u total:225 pass:182 dwarn:18 dfail:0 fail:2 skip:23
fi-skl-i7-6700k total:225 pass:186 dwarn:0 dfail:0 fail:2 skip:37
ro-bdw-i7-5557U total:225 pass:198 dwarn:0 dfail:0 fail:0 skip:27
ro-bdw-i7-5600u total:225 pass:184 dwarn:1 dfail:0 fail:0 skip:40
ro-byt-n2820 total:225 pass:173 dwarn:0 dfail:0 fail:3 skip:49
ro-hsw-i3-4010u total:225 pass:179 dwarn:11 dfail:0 fail:0 skip:35
ro-hsw-i7-4770r total:225 pass:190 dwarn:0 dfail:0 fail:0 skip:35
ro-ilk-i7-620lm total:225 pass:150 dwarn:0 dfail:0 fail:1 skip:74
ro-ilk1-i5-650 total:220 pass:149 dwarn:1 dfail:0 fail:1 skip:69
ro-ivb-i7-3770 total:225 pass:181 dwarn:0 dfail:0 fail:0 skip:44
ro-ivb2-i7-3770 total:225 pass:184 dwarn:1 dfail:0 fail:0 skip:40
ro-skl3-i5-6260u total:225 pass:201 dwarn:1 dfail:0 fail:0 skip:23
ro-snb-i7-2620M total:225 pass:173 dwarn:1 dfail:0 fail:1 skip:50
fi-hsw-i7-4770k failed to connect after reboot
fi-snb-i7-2600 failed to connect after reboot
ro-bdw-i5-5250u failed to connect after reboot
Results at /archive/results/CI_IGT_test/RO_Patchwork_1251/
79c69c3 drm-intel-nightly: 2016y-06m-21d-08h-53m-58s UTC integration manifest
00fc9d2 drm: Drop mode_config.mutex from _reset()
5a86f0a drm: Drop mode_config.mutex from get_resources ioctl
c390398 drm: Drop mode_config.mutex from connector_register_all
0c61ea6 drm: Revamp connector_list protection
a85943f drm: Drop cargo-culted modeset_lock_all from encoder/plane init/cleanup
c71630b drm/i915: Roll out drm_for_each_connector in intel_hotplug.c
8ae4924 drm/i915: Use use the drm_for_each_connector in i915_debugfs.c
39fab56 drm: Add explicit iter struct to drm_for_each_connector
9449105 drm: Don't compute obj counts expensively in get_resources
ad7b8e5 drm/amd-kfd: Clean up inline handling
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-06-21 10:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 9:10 [PATCH 00/10] RFC: hot-unplug safe connector list locking Daniel Vetter
2016-06-21 9:10 ` [PATCH 01/10] drm/amd-kfd: Clean up inline handling Daniel Vetter
2016-06-21 19:11 ` Oded Gabbay
2016-06-21 19:22 ` Daniel Vetter
2016-06-22 7:35 ` Daniel Vetter
2016-06-21 9:10 ` [PATCH 02/10] drm: Don't compute obj counts expensively in get_resources Daniel Vetter
2016-06-21 9:48 ` Chris Wilson
2016-06-21 12:21 ` Daniel Vetter
2016-06-21 12:29 ` [PATCH] " Daniel Vetter
2016-06-21 12:40 ` Chris Wilson
2016-06-21 9:10 ` [PATCH 03/10] drm: Add explicit iter struct to drm_for_each_connector Daniel Vetter
2016-06-21 9:10 ` [PATCH 04/10] drm/i915: Use use the drm_for_each_connector in i915_debugfs.c Daniel Vetter
2016-06-21 9:10 ` [PATCH 05/10] drm/i915: Roll out drm_for_each_connector in intel_hotplug.c Daniel Vetter
2016-06-21 9:10 ` [PATCH 06/10] drm: Drop cargo-culted modeset_lock_all from encoder/plane init/cleanup Daniel Vetter
2016-06-21 9:10 ` [PATCH 07/10] drm: Revamp connector_list protection Daniel Vetter
2016-06-22 9:09 ` Daniel Vetter
2016-06-21 9:10 ` [PATCH 08/10] drm: Drop mode_config.mutex from connector_register_all Daniel Vetter
2016-06-21 9:10 ` [PATCH 09/10] drm: Drop mode_config.mutex from get_resources ioctl Daniel Vetter
2016-06-21 9:44 ` Chris Wilson
2016-06-21 12:41 ` [PATCH] " Daniel Vetter
2016-06-21 9:10 ` [PATCH 10/10] drm: Drop mode_config.mutex from _reset() Daniel Vetter
2016-06-21 10:28 ` Patchwork [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160621102853.12986.26007@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox