From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: request ring to be pinned above GUC_WOPCM_TOP
Date: Thu, 22 Dec 2016 15:15:03 -0800 [thread overview]
Message-ID: <2e4b820c-927e-326b-f9ae-489116b1eaee@intel.com> (raw)
In-Reply-To: <20161222222326.23677.56729@emeril.freedesktop.org>
On 22/12/16 14:23, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: request ring to be pinned above GUC_WOPCM_TOP
> URL : https://patchwork.freedesktop.org/series/17147/
> State : failure
>
> == Summary ==
>
> Series 17147v1 drm/i915: request ring to be pinned above GUC_WOPCM_TOP
> https://patchwork.freedesktop.org/api/1.0/series/17147/revisions/1/mbox/
>
> Test gem_busy:
> Subgroup basic-busy-default:
> pass -> FAIL (fi-hsw-4770)
> pass -> FAIL (fi-hsw-4770r)
> pass -> FAIL (fi-byt-j1900)
> Subgroup basic-hang-default:
> pass -> FAIL (fi-hsw-4770)
> pass -> FAIL (fi-hsw-4770r)
> Test gem_wait:
> Subgroup basic-busy-all:
> pass -> FAIL (fi-ivb-3770)
> pass -> FAIL (fi-hsw-4770)
> pass -> FAIL (fi-ivb-3520m)
> Subgroup basic-wait-all:
> pass -> FAIL (fi-ivb-3770)
> pass -> FAIL (fi-hsw-4770)
> pass -> FAIL (fi-byt-j1900)
Clearly moving the ring for legacy submission as well was a bad idea,
although by looking at the logs I'm not clear as of why we're getting
these hangs and I don't have any pre-Gen8 device to try and reproduce
locally. I'll wait until tomorrow to see if there are any comments on
the patch and then I'll submit v2 with the change in offset gated by
HAS_GUC_SCHED.
Daniele
>
> fi-bdw-5557u total:246 pass:232 dwarn:0 dfail:0 fail:0 skip:14
> fi-bsw-n3050 total:246 pass:207 dwarn:0 dfail:0 fail:0 skip:39
> fi-bxt-j4205 total:246 pass:224 dwarn:0 dfail:0 fail:0 skip:22
> fi-bxt-t5700 total:82 pass:69 dwarn:0 dfail:0 fail:0 skip:12
> fi-byt-j1900 total:246 pass:217 dwarn:0 dfail:0 fail:2 skip:27
> fi-byt-n2820 total:246 pass:215 dwarn:0 dfail:0 fail:0 skip:31
> fi-hsw-4770 total:246 pass:223 dwarn:0 dfail:0 fail:4 skip:19
> fi-hsw-4770r total:246 pass:225 dwarn:0 dfail:0 fail:2 skip:19
> fi-ivb-3520m total:246 pass:224 dwarn:0 dfail:0 fail:1 skip:21
> fi-ivb-3770 total:246 pass:223 dwarn:0 dfail:0 fail:2 skip:21
> fi-kbl-7500u total:246 pass:225 dwarn:0 dfail:0 fail:0 skip:21
> fi-skl-6260u total:246 pass:233 dwarn:0 dfail:0 fail:0 skip:13
> fi-skl-6700hq total:246 pass:226 dwarn:0 dfail:0 fail:0 skip:20
> fi-skl-6700k total:246 pass:222 dwarn:3 dfail:0 fail:0 skip:21
> fi-skl-6770hq total:246 pass:233 dwarn:0 dfail:0 fail:0 skip:13
> fi-snb-2600 total:246 pass:214 dwarn:0 dfail:0 fail:0 skip:32
>
> 7165fdc7f0b0b536557fcd0a222d083a901be57c drm-tip: 2016y-12m-22d-19h-42m-25s UTC integration manifest
> 9d0d15f drm/i915: request ring to be pinned above GUC_WOPCM_TOP
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3380/
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-22 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 19:55 [PATCH] drm/i915: request ring to be pinned above GUC_WOPCM_TOP daniele.ceraolospurio
2016-12-22 20:58 ` Srivatsa, Anusha
2016-12-22 22:23 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-12-22 23:15 ` Daniele Ceraolo Spurio [this message]
2016-12-23 7:44 ` Chris Wilson
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=2e4b820c-927e-326b-f9ae-489116b1eaee@intel.com \
--to=daniele.ceraolospurio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.