From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org, Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Balance assert_rpm_wakelock_held() for !IS_ENABLED(CONFIG_PM)
Date: Fri, 26 Feb 2016 13:02:47 +0200 [thread overview]
Message-ID: <1456484567.30921.7.camel@intel.com> (raw)
In-Reply-To: <20160226070048.30358.99095@emeril.freedesktop.org>
On Fri, 2016-02-26 at 07:00 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Balance assert_rpm_wakelock_held() for
> !IS_ENABLED(CONFIG_PM)
> URL : https://patchwork.freedesktop.org/series/3827/
> State : failure
>
> == Summary ==
>
> Series 3827v1 drm/i915: Balance assert_rpm_wakelock_held() for
> !IS_ENABLED(CONFIG_PM)
> http://patchwork.freedesktop.org/api/1.0/series/3827/revisions/1/mbox
> /
>
> Test drv_hangman:
> Subgroup error-state-basic:
> pass -> INCOMPLETE (snb-dellxps)
> Test gem_sync:
> Subgroup basic-bsd:
> pass -> DMESG-FAIL (hsw-brixbox)
> pass -> DMESG-FAIL (ilk-hp8440p)
> Test kms_flip:
> Subgroup basic-flip-vs-wf_vblank:
> pass -> FAIL (snb-x220t)
> Test pm_rpm:
> Subgroup basic-pci-d3-state:
> dmesg-warn -> PASS (byt-nuc)
> Subgroup basic-rte:
> pass -> DMESG-WARN (bsw-nuc-2)
> fail -> PASS (bdw-nuci7)
> fail -> PASS (bdw-ultra)
All tests are run with CONFIG_PM enabled, and the patch changes
behavior only with !CONFIG_PM. Even in case of !CONFIG_PM only the
generation of wakeref messages are affected and not any other
functionality. So I'm confident the above failures are unrelated.
> bdw-
> nuci7 total:165 pass:154 dwarn:0 dfail:0 fail:0 skip:1
> 1
> bdw-
> ultra total:168 pass:154 dwarn:0 dfail:0 fail:0 skip:1
> 4
> bsw-nuc-
> 2 total:168 pass:136 dwarn:1 dfail:0 fail:1 skip:30
> byt-
> nuc total:168 pass:143 dwarn:0 dfail:0 fail:0 skip:2
> 5
> hsw-
> brixbox total:168 pass:153 dwarn:0 dfail:1 fail:0 skip:1
> 4
> hsw-
> gt2 total:168 pass:157 dwarn:0 dfail:1 fail:0 skip:1
> 0
> ilk-
> hp8440p total:168 pass:117 dwarn:0 dfail:2 fail:0 skip:4
> 9
> ivb-
> t430s total:168 pass:153 dwarn:0 dfail:0 fail:1 skip:1
> 4
> skl-i7k-
> 2 total:168 pass:151 dwarn:1 dfail:0 fail:0 skip:16
> snb-
> dellxps total:154 pass:132 dwarn:0 dfail:0 fail:1 skip:2
> 0
> snb-
> x220t total:168 pass:144 dwarn:0 dfail:0 fail:3 skip:2
> 1
>
> Results at /archive/results/CI_IGT_test/Patchwork_1479/
>
> 38f0cd5314ecb02d15d019631e388d3642275600 drm-intel-nightly: 2016y-
> 02m-25d-15h-33m-53s UTC integration manifest
> f7a63002de7ec2829aeae48527217bc4d1d9b106 drm/i915: Balance
> assert_rpm_wakelock_held() for !IS_ENABLED(CONFIG_PM)
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-26 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 21:10 [PATCH] drm/i915: Balance assert_rpm_wakelock_held() for !IS_ENABLED(CONFIG_PM) Chris Wilson
2016-02-25 22:20 ` Imre Deak
2016-02-26 14:05 ` [Intel-gfx] " Imre Deak
2016-02-26 7:00 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-02-26 11:02 ` 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=1456484567.30921.7.camel@intel.com \
--to=imre.deak@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomi.p.sarvela@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