From: Patchwork <patchwork@annarchy.freedesktop.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for drm/i915: Lock mode_config.mutex in intel_display_resume.
Date: Tue, 16 Feb 2016 16:21:53 -0000 [thread overview]
Message-ID: <20160216162153.1004.1271@annarchy.freedesktop.org> (raw)
In-Reply-To: <1455632862-18557-1-git-send-email-maarten.lankhorst@linux.intel.com>
== Summary ==
Series 3485v1 drm/i915: Lock mode_config.mutex in intel_display_resume.
http://patchwork.freedesktop.org/api/1.0/series/3485/revisions/1/mbox/
Test drv_module_reload_basic:
fail -> PASS (snb-dellxps)
Test gem_mmap_gtt:
Subgroup basic-write:
pass -> DMESG-WARN (bsw-nuc-2)
Test kms_force_connector_basic:
Subgroup force-edid:
skip -> PASS (snb-x220t)
skip -> PASS (ivb-t430s)
Subgroup prune-stale-modes:
skip -> PASS (ivb-t430s)
Test kms_pipe_crc_basic:
Subgroup suspend-read-crc-pipe-a:
dmesg-warn -> PASS (skl-i5k-2)
dmesg-warn -> PASS (snb-dellxps)
dmesg-warn -> PASS (hsw-brixbox)
dmesg-warn -> PASS (byt-nuc)
Subgroup suspend-read-crc-pipe-b:
pass -> DMESG-WARN (skl-i5k-2)
dmesg-warn -> PASS (hsw-gt2)
dmesg-warn -> PASS (snb-dellxps)
dmesg-warn -> PASS (hsw-brixbox)
dmesg-warn -> PASS (byt-nuc)
Subgroup suspend-read-crc-pipe-c:
dmesg-warn -> PASS (bsw-nuc-2)
dmesg-warn -> INCOMPLETE (hsw-gt2)
dmesg-warn -> PASS (hsw-brixbox)
Test pm_rpm:
Subgroup basic-pci-d3-state:
pass -> DMESG-WARN (byt-nuc)
Subgroup basic-rte:
dmesg-warn -> PASS (bsw-nuc-2)
bdw-ultra total:165 pass:152 dwarn:0 dfail:0 fail:0 skip:13
bsw-nuc-2 total:165 pass:135 dwarn:1 dfail:0 fail:0 skip:29
byt-nuc total:165 pass:140 dwarn:1 dfail:0 fail:0 skip:24
hsw-brixbox total:165 pass:151 dwarn:0 dfail:0 fail:0 skip:14
hsw-gt2 total:85 pass:78 dwarn:0 dfail:0 fail:0 skip:6
ivb-t430s total:165 pass:150 dwarn:0 dfail:0 fail:1 skip:14
skl-i5k-2 total:165 pass:149 dwarn:1 dfail:0 fail:0 skip:15
snb-dellxps total:165 pass:142 dwarn:0 dfail:0 fail:1 skip:22
snb-x220t total:165 pass:142 dwarn:0 dfail:0 fail:2 skip:21
Results at /archive/results/CI_IGT_test/Patchwork_1415/
d6fbb21195050d1fcff27e5918114fb5ef66c137 drm-intel-nightly: 2016y-02m-16d-14h-37m-16s UTC integration manifest
8b2c8ef0acd075cbacd9d3b59fa6514d0cd67897 drm/i915: Lock mode_config.mutex in intel_display_resume.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-16 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 14:27 [PATCH] drm/i915: Lock mode_config.mutex in intel_display_resume Maarten Lankhorst
2016-02-16 15:12 ` Daniel Vetter
2016-02-16 16:21 ` 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=20160216162153.1004.1271@annarchy.freedesktop.org \
--to=patchwork@annarchy.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).