From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org, Bob Paauwe <bob.j.paauwe@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fixes for runtime and system suspend/resume
Date: Fri, 22 Apr 2016 16:01:13 +0300 [thread overview]
Message-ID: <1461330073.30129.10.camel@intel.com> (raw)
In-Reply-To: <20160421120510.29237.30259@emeril.freedesktop.org>
On to, 2016-04-21 at 12:05 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/bxt: Fixes for runtime and system suspend/resume
> URL : https://patchwork.freedesktop.org/series/6009/
> State : failure
>
> == Summary ==
There was a previous email with 'success' for this same test run
(Patchwork_1966).
> Series 6009v1 drm/i915/bxt: Fixes for runtime and system
> suspend/resume
> http://patchwork.freedesktop.org/api/1.0/series/6009/revisions/1/mbox
> /
>
> Test gem_busy:
> Subgroup basic-blt:
> skip -> PASS (bsw-nuc-2)
> Test gem_sync:
> Subgroup basic-bsd:
> pass -> DMESG-FAIL (ilk-hp8440p)
GPU hang on BSD ring:
https://bugs.freedesktop.org/show_bug.cgi?id=94307
> Test kms_flip:
> Subgroup basic-flip-vs-wf_vblank:
> pass -> FAIL (byt-nuc)
(kms_flip:7340) CRITICAL: Test assertion failure function check_state, file kms_flip.c:692:
(kms_flip:7340) CRITICAL: Failed assertion: fabs((((double) diff.tv_usec) - usec_interflip) / usec_interflip) <= 0.005
(kms_flip:7340) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:7340) CRITICAL: inter-vblank ts jitter: 0s, 183433usec
Subtest basic-flip-vs-wf_vblank failed.
Thanks for the review, I pushed the patchset to -dinq.
I fixed while applying the WS error you found in patch 3/4 and fixed my
uninline vs. inline confusion in the commit message of 1/4.
--Imre
>
> bdw-
> ultra total:194 pass:170 dwarn:0 dfail:0 fail:1 skip:2
> 3
> bsw-nuc-
> 2 total:193 pass:154 dwarn:0 dfail:0 fail:0 skip:39
> byt-
> nuc total:193 pass:154 dwarn:0 dfail:0 fail:1 skip:3
> 8
> hsw-
> brixbox total:194 pass:170 dwarn:0 dfail:0 fail:0 skip:2
> 4
> hsw-
> gt2 total:194 pass:175 dwarn:0 dfail:0 fail:0 skip:1
> 9
> ilk-
> hp8440p total:194 pass:136 dwarn:0 dfail:1 fail:0 skip:5
> 7
> ivb-
> t430s total:194 pass:166 dwarn:0 dfail:0 fail:0 skip:2
> 8
> skl-i7k-
> 2 total:194 pass:168 dwarn:0 dfail:0 fail:1 skip:25
> skl-
> nuci5 total:194 pass:183 dwarn:0 dfail:0 fail:0 skip:1
> 1
> snb-
> dellxps total:152 pass:115 dwarn:0 dfail:0 fail:0 skip:3
> 6
>
> Results at /archive/results/CI_IGT_test/Patchwork_1966/
>
> 9dabb0053b63bc32ab6ad5d13209d1e43395313f drm-intel-nightly: 2016y-
> 04m-21d-09h-27m-12s UTC integration manifest
> 1969810 drm/i915/bxt: Enable DC5 during runtime resume
> 4e6ae40 drm/i915/bxt: Sanitize DC state tracking during system resume
> 5e7b5f6 drm/i915/bxt: Don't uninit/init display core twice during
> system suspend/resume
> b5a5dbd drm/i915: Uninline intel_suspend_complete
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-04-22 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 17:27 [PATCH 0/4] drm/i915/bxt: Fixes for runtime and system suspend/resume Imre Deak
2016-04-20 17:27 ` [PATCH 1/4] drm/i915: Uninline intel_suspend_complete Imre Deak
2016-04-20 20:59 ` Bob Paauwe
2016-04-20 17:27 ` [PATCH 2/4] drm/i915/bxt: Don't uninit/init display core twice during system suspend/resume Imre Deak
2016-04-20 21:03 ` Bob Paauwe
2016-04-20 17:27 ` [PATCH 3/4] drm/i915/bxt: Sanitize DC state tracking during system resume Imre Deak
2016-04-20 21:00 ` Bob Paauwe
2016-04-20 17:27 ` [PATCH 4/4] drm/i915/bxt: Enable DC5 during runtime resume Imre Deak
2016-04-20 21:01 ` Bob Paauwe
2016-04-21 10:27 ` ✓ Fi.CI.BAT: success for drm/i915/bxt: Fixes for runtime and system suspend/resume Patchwork
2016-04-21 12:05 ` ✗ Fi.CI.BAT: failure " Patchwork
2016-04-22 13:01 ` Imre Deak [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=1461330073.30129.10.camel@intel.com \
--to=imre.deak@intel.com \
--cc=bob.j.paauwe@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.