From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with [resend-for-CI,1/3] drm/i915: Use consistent forcewake auto-release timeout across kernel configs
Date: Tue, 12 Apr 2016 16:43:39 +0300 [thread overview]
Message-ID: <20160412134339.GS4329@intel.com> (raw)
In-Reply-To: <570CF939.9070201@linux.intel.com>
On Tue, Apr 12, 2016 at 02:33:45PM +0100, Tvrtko Ursulin wrote:
>
> On 08/04/16 08:02, Patchwork wrote:
> > Test kms_flip:
> > Subgroup basic-flip-vs-dpms:
> > pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
>
> Old friend unclaimed access prior to suspending:
> https://bugs.freedesktop.org/show_bug.cgi?id=94164
o_O
ILK doesn't even have a way to detect such things.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-12 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 16:04 [PATCH resend-for-CI 1/3] drm/i915: Use consistent forcewake auto-release timeout across kernel configs Tvrtko Ursulin
2016-04-07 16:04 ` [PATCH resend-for-CI 2/3] drm/i915: Simplify for_each_fw_domain iterators Tvrtko Ursulin
2016-04-07 16:04 ` [PATCH resend-for-CI 3/3] drm/i915: Do not serialize forcewake acquire across domains Tvrtko Ursulin
2016-04-08 7:02 ` ✗ Fi.CI.BAT: failure for series starting with [resend-for-CI,1/3] drm/i915: Use consistent forcewake auto-release timeout across kernel configs Patchwork
2016-04-08 8:38 ` Chris Wilson
2016-04-12 13:33 ` Tvrtko Ursulin
2016-04-12 13:43 ` Ville Syrjälä [this message]
2016-04-12 13:51 ` Tvrtko Ursulin
-- strict thread matches above, loose matches on Subject: below --
2016-04-06 9:33 [PATCH resend-for-CI 1/3] " Tvrtko Ursulin
2016-04-06 10:28 ` ✗ Fi.CI.BAT: failure for series starting with [resend-for-CI,1/3] " Patchwork
2016-04-06 11:05 ` 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=20160412134339.GS4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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