public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
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 13:50:03 +0100	[thread overview]
Message-ID: <578CD07B.6090303@intel.com> (raw)
In-Reply-To: <20160718122945.GZ17101@phenom.ffwll.local>

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.

>> fi-hsw-i7-4770k  total:242  pass:210  dwarn:0   dfail:0   fail:12  skip:20
>> fi-kbl-qkkr      total:242  pass:176  dwarn:27  dfail:0   fail:12  skip:27
>> fi-skl-i5-6260u  total:242  pass:218  dwarn:1   dfail:0   fail:11  skip:12
>> fi-skl-i7-6700k  total:107  pass:84   dwarn:0   dfail:0   fail:0   skip:22
>> fi-snb-i7-2600   total:242  pass:190  dwarn:0   dfail:0   fail:12  skip:40
>> ro-bdw-i5-5250u  total:243  pass:214  dwarn:4   dfail:0   fail:12  skip:13
>> ro-bdw-i7-5557U  total:243  pass:215  dwarn:0   dfail:0   fail:12  skip:16
>> ro-bdw-i7-5600u  total:243  pass:199  dwarn:0   dfail:1   fail:11  skip:32
>> ro-bsw-n3050     total:218  pass:173  dwarn:0   dfail:0   fail:2   skip:42
>> ro-byt-n2820     total:243  pass:191  dwarn:0   dfail:0   fail:14  skip:38
>> ro-hsw-i3-4010u  total:243  pass:206  dwarn:0   dfail:0   fail:13  skip:24
>> ro-hsw-i7-4770r  total:243  pass:206  dwarn:0   dfail:0   fail:13  skip:24
>> ro-ilk-i7-620lm  total:243  pass:166  dwarn:0   dfail:0   fail:14  skip:63
>> ro-ilk1-i5-650   total:238  pass:166  dwarn:0   dfail:0   fail:14  skip:58
>> ro-ivb-i7-3770   total:243  pass:197  dwarn:0   dfail:0   fail:13  skip:33
>> ro-skl3-i5-6260u total:243  pass:218  dwarn:1   dfail:0   fail:12  skip:12
>> ro-snb-i7-2620M  total:243  pass:188  dwarn:0   dfail:0   fail:13  skip:42
>> fi-bsw-n3050 failed to connect after reboot
>>
>> Results at /archive/results/CI_IGT_test/RO_Patchwork_1517/
>>
>> 74bd981 drm-intel-nightly: 2016y-07m-18d-10h-05m-42s UTC integration manifest
>> c3022da drm/i915: Treat eDP as always connected, again
>>
>> _______________________________________________
>> 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

  parent reply	other threads:[~2016-07-18 12:50 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 [this message]
2016-07-18 13:01       ` Dave Gordon

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=578CD07B.6090303@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox