From: Dave Gordon <david.s.gordon@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Ro.CI.BAT: failure for drm/i915: Treat eDP as always connected, again
Date: Mon, 18 Jul 2016 14:01:13 +0100 [thread overview]
Message-ID: <578CD319.7040100@intel.com> (raw)
In-Reply-To: <578CD07B.6090303@intel.com>
On 18/07/16 13:50, Dave Gordon wrote:
> On 18/07/16 13:29, Daniel Vetter wrote:
>> On Mon, Jul 18, 2016 at 11:43:08AM -0000, Patchwork wrote:
>>> == Series Details ==
>>>
>>> Series: drm/i915: Treat eDP as always connected, again
>>> URL : https://patchwork.freedesktop.org/series/9977/
>>> State : failure
>>>
>>> == Summary ==
>>>
>>> Series 9977v1 drm/i915: Treat eDP as always connected, again
>>> http://patchwork.freedesktop.org/api/1.0/series/9977/revisions/1/mbox
>>>
>>> Test gem_exec_suspend:
>>> Subgroup basic-s3:
>>> pass -> DMESG-WARN (fi-skl-i5-6260u)
>>> Test gem_sync:
>>> Subgroup basic-store-each:
>>> pass -> DMESG-FAIL (ro-bdw-i7-5600u)
>>
>> I tried to find the bug reports for these, and we don't track them.
>> And at
>> least the 2nd one looks like it's a one-off, so who knows what's going
>> on.
>>
>> But while trying to figure out what's going on I stumbled over about 5
>> other sporadic CI issues in those boxes which aren't event tracked
>> either.
>>
>> /me cries
>>
>> So normally not good enough for CI, but regressions win even against our
>> shitty CI. Hence applied and will cherry-pick over to -fixes.
>> -Daniel
>
> Looks like the failure in basic-store-each has been happening since at
> least 2016-07-10, but only on one specific BDW machine
> (ro-bdw-i7-5600u). Failure is:
>
> > Failed assertion: intel_detect_and_clear_missed_interrupts(fd) == 0
>
> Intermittent, though, as Chris's recent results show:
>
>> Test gem_sync:
>> Subgroup basic-store-each:
>> dmesg-fail -> PASS (ro-bdw-i7-5600u)
>
> making it very difficult to determine whether it's a real regression or
> some problem with that specific machine -- it doesn't happen on the
> other BDWs, but they're all slightly different.
>
> .Dave.
Bug filed: Bug 96975 - [BAT BDW] basic-store-each fails,
intel_detect_and_clear_missed_interrupts(fd) == 0
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-07-18 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 10:15 [PATCH] drm/i915: Treat eDP as always connected, again ville.syrjala
2016-07-18 11:43 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-07-18 12:29 ` Daniel Vetter
2016-07-18 12:45 ` Ville Syrjälä
2016-07-18 12:50 ` Dave Gordon
2016-07-18 13:01 ` Dave Gordon [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=578CD319.7040100@intel.com \
--to=david.s.gordon@intel.com \
--cc=daniel@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.