From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Ro.CI.BAT: failure for drm: BIT(DRM_ROTATE_?) -> DRM_ROTATE_?
Date: Mon, 25 Jul 2016 13:23:56 +0300 [thread overview]
Message-ID: <1469442236.5495.48.camel@linux.intel.com> (raw)
In-Reply-To: <20160725073940.18649.36455@emeril.freedesktop.org>
On ma, 2016-07-25 at 07:39 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm: BIT(DRM_ROTATE_?) -> DRM_ROTATE_?
> URL : https://patchwork.freedesktop.org/series/10229/
> State : failure
>
> == Summary ==
>
> Series 10229v1 drm: BIT(DRM_ROTATE_?) -> DRM_ROTATE_?
> http://patchwork.freedesktop.org/api/1.0/series/10229/revisions/1/mbox
>
> Test drv_module_reload_basic:
> pass -> SKIP (ro-hsw-i3-4010u)
> Test gem_sync:
> Subgroup basic-store-each:
> pass -> DMESG-FAIL (ro-bdw-i7-5600u)
Filed a new bug;
https://bugs.freedesktop.org/show_bug.cgi?id=97071
Kernel error:
[drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed...
video enhancement ring idle
>
> ro-bdw-i5-5250u total:244 pass:219 dwarn:4 dfail:0 fail:8 skip:13
> ro-bdw-i7-5600u total:244 pass:203 dwarn:0 dfail:1 fail:8 skip:32
> ro-bsw-n3050 total:218 pass:173 dwarn:0 dfail:0 fail:2 skip:42
> ro-byt-n2820 total:244 pass:197 dwarn:0 dfail:0 fail:9 skip:38
> ro-hsw-i3-4010u total:244 pass:211 dwarn:0 dfail:0 fail:8 skip:25
> ro-hsw-i7-4770r total:244 pass:212 dwarn:0 dfail:0 fail:8 skip:24
> ro-ilk-i7-620lm total:244 pass:172 dwarn:0 dfail:0 fail:9 skip:63
> ro-ilk1-i5-650 total:239 pass:172 dwarn:0 dfail:0 fail:9 skip:58
> ro-ivb-i7-3770 total:244 pass:203 dwarn:0 dfail:0 fail:8 skip:33
> ro-skl3-i5-6260u total:244 pass:224 dwarn:0 dfail:0 fail:8 skip:12
> ro-snb-i7-2620M total:244 pass:193 dwarn:0 dfail:0 fail:9 skip:42
> ro-bdw-i7-5557U failed to connect after reboot
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1594/
>
> 5c9e3d9 drm-intel-nightly: 2016y-07m-25d-06h-32m-37s UTC integration manifest
> 7e91383 drm: BIT(DRM_ROTATE_?) -> DRM_ROTATE_?
>
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-25 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 7:00 [PATCH] drm: BIT(DRM_ROTATE_?) -> DRM_ROTATE_? Joonas Lahtinen
2016-07-25 7:39 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-07-25 10:23 ` Joonas Lahtinen [this message]
[not found] ` <1469430025-13540-1-git-send-email-joonas.lahtinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-07-26 9:05 ` [PATCH] " Liviu Dudau
2016-07-26 11:53 ` Joonas Lahtinen
2016-07-26 12:41 ` Ville Syrjälä
2016-07-26 14:49 ` Sean Paul
[not found] ` <CAOw6vbKGJYdN+aZqM7+EDGut3LU3YkDD1HT4QE=AObh4r2UVtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-28 6:44 ` Joonas Lahtinen
2016-07-28 14:04 ` Sean Paul
2016-07-29 5:49 ` Joonas Lahtinen
2016-07-29 5:51 ` Joonas Lahtinen
2016-07-29 5:50 ` [PATCH v2] " Joonas Lahtinen
2016-07-29 19:33 ` Sean Paul
2016-07-29 6:16 ` ✗ Ro.CI.BAT: failure for drm: BIT(DRM_ROTATE_?) -> DRM_ROTATE_? (rev3) Patchwork
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=1469442236.5495.48.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--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