From: Daniel Vetter <daniel@ffwll.ch>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: ✗ Fi.CI.BAT: failure for drm: Take mode_config.mutex in setcrtc ioctl (rev2)
Date: Fri, 7 Apr 2017 09:25:21 +0200 [thread overview]
Message-ID: <20170407072521.z7x4xk5g7345dnon@phenom.ffwll.local> (raw)
In-Reply-To: <20170406193441.14286.19801@emeril.freedesktop.org>
On Thu, Apr 06, 2017 at 07:34:41PM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm: Take mode_config.mutex in setcrtc ioctl (rev2)
> URL : https://patchwork.freedesktop.org/series/22605/
> State : failure
>
> == Summary ==
>
> Series 22605v2 drm: Take mode_config.mutex in setcrtc ioctl
> https://patchwork.freedesktop.org/api/1.0/series/22605/revisions/2/mbox/
>
> Test core_auth:
> Subgroup basic-auth:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test core_prop_blob:
> Subgroup basic:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test drv_getparams_basic:
> Subgroup basic-eu-total:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup basic-subslice-total:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test drv_hangman:
> Subgroup error-state-basic:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_basic:
> Subgroup bad-close:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup create-close:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup create-fd-close:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_busy:
> Subgroup basic-busy-default:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup basic-hang-default:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_close_race:
> Subgroup basic-process:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup basic-threads:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_cpu_reloc:
> Subgroup basic:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_cs_tlb:
> Subgroup basic-default:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_ctx_basic:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_ctx_create:
> Subgroup basic:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup basic-files:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_ctx_exec:
> Subgroup basic:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_ctx_param:
> Subgroup basic:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup basic-default:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_ctx_switch:
> Subgroup basic-default:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup basic-default-heavy:
> pass -> DMESG-WARN (fi-ivb-3770)
> Test gem_exec_basic:
> Subgroup basic-blt:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup basic-bsd:
> pass -> DMESG-WARN (fi-ivb-3770)
> Subgroup basic-default:
> pass -> INCOMPLETE (fi-ivb-3770)
Anyone have an idea what happened to this poor ivb? Lots of flip_done
timed-out, then eventually machine death.
-Daniel
>
> fi-bdw-5557u total:278 pass:267 dwarn:0 dfail:0 fail:0 skip:11 time: 434s
> fi-bdw-gvtdvm total:278 pass:256 dwarn:8 dfail:0 fail:0 skip:14 time: 423s
> fi-bsw-n3050 total:278 pass:242 dwarn:0 dfail:0 fail:0 skip:36 time: 569s
> fi-bxt-j4205 total:278 pass:259 dwarn:0 dfail:0 fail:0 skip:19 time: 505s
> fi-bxt-t5700 total:278 pass:258 dwarn:0 dfail:0 fail:0 skip:20 time: 546s
> fi-byt-j1900 total:278 pass:254 dwarn:0 dfail:0 fail:0 skip:24 time: 489s
> fi-byt-n2820 total:278 pass:250 dwarn:0 dfail:0 fail:0 skip:28 time: 487s
> fi-hsw-4770 total:278 pass:262 dwarn:0 dfail:0 fail:0 skip:16 time: 407s
> fi-hsw-4770r total:278 pass:262 dwarn:0 dfail:0 fail:0 skip:16 time: 403s
> fi-ilk-650 total:278 pass:228 dwarn:0 dfail:0 fail:0 skip:50 time: 432s
> fi-ivb-3520m total:278 pass:260 dwarn:0 dfail:0 fail:0 skip:18 time: 494s
> fi-ivb-3770 total:27 pass:0 dwarn:24 dfail:0 fail:0 skip:2 time: 0s
> fi-kbl-7500u total:278 pass:260 dwarn:0 dfail:0 fail:0 skip:18 time: 451s
> fi-kbl-7560u total:278 pass:267 dwarn:1 dfail:0 fail:0 skip:10 time: 566s
> fi-skl-6260u total:278 pass:268 dwarn:0 dfail:0 fail:0 skip:10 time: 458s
> fi-skl-6700hq total:278 pass:261 dwarn:0 dfail:0 fail:0 skip:17 time: 573s
> fi-skl-6700k total:278 pass:256 dwarn:4 dfail:0 fail:0 skip:18 time: 463s
> fi-skl-6770hq total:278 pass:268 dwarn:0 dfail:0 fail:0 skip:10 time: 494s
> fi-skl-gvtdvm total:278 pass:265 dwarn:0 dfail:0 fail:0 skip:13 time: 434s
> fi-snb-2520m total:278 pass:250 dwarn:0 dfail:0 fail:0 skip:28 time: 528s
> fi-snb-2600 total:278 pass:249 dwarn:0 dfail:0 fail:0 skip:29 time: 410s
>
> e087f8395ca39c6988de8680bd6f80a20b08c0f4 drm-tip: 2017y-04m-06d-13h-28m-42s UTC integration manifest
> 09c592e drm: Take mode_config.mutex in setcrtc ioctl
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_4426/
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-04-07 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 18:55 [PATCH] drm: Take mode_config.mutex in setcrtc ioctl Daniel Vetter
2017-04-06 19:02 ` Alex Deucher
2017-04-06 19:06 ` Daniel Vetter
2017-04-06 19:09 ` Alex Deucher
2017-04-06 20:49 ` Daniel Vetter
2017-04-06 19:34 ` ✗ Fi.CI.BAT: failure for drm: Take mode_config.mutex in setcrtc ioctl (rev2) Patchwork
2017-04-07 7:25 ` Daniel Vetter [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=20170407072521.z7x4xk5g7345dnon@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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 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.