All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: intel-gfx@lists.freedesktop.org,
	"Jani Nikula" <jani.nikula@intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Manasi Navare" <manasi.d.navare@intel.com>,
	"Ville Syrjälä" <ville.syrjala@intel.com>,
	"Lyude Paul" <lyude@redhat.com>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
	Dave Airlie <airlied@redhat.com>
Subject: drm-intel-fixes CI issues
Date: Wed, 10 Oct 2018 15:53:36 -0700	[thread overview]
Message-ID: <20181010225335.GI6934@intel.com> (raw)

Hi all,

I need your help to decide what to do with this round of fixes.

I have collected these patches this week:

commit b43e8916172a ("drm/i915/dp: Link train Fallback on eDP only if fallback link BW can fit panel's native mode")
commit 5abb01e541ed ("drm/i915: Fix intel_dp_mst_best_encoder()")
commit 02713246296d ("drm/i915: Skip vcpi allocation for MSTB ports that are gone")
commit cc6e027f5f50 ("drm/i915: Don't unset intel_connector->mst_port")
commit f5aec50ba21e ("drm/i915: Use the correct crtc when sanitizing plane mapping")
commit 6547684bf50a ("drm/i915: Restore vblank interrupts earlier")

CI_DIF_309 represents Greg's v4.19-rc7 and it is clean.

However 2 following CI runs are kind of strange.

There's few underruns here and there, but those looks flip-flops.

My biggest concern is specially around:

igt@kms_plane@pixel-format-pipe-a-planes:
https://intel-gfx-ci.01.org/tree/drm-intel-fixes/shards.html

https://intel-gfx-ci.01.org/tree/drm-intel-fixes/CI_DIF_311/shard-glk8/igt@kms_plane@pixel-format-pipe-c-planes.html

Thoughts?

I'm holding the pull request for now and will try to do some local tests here
to see if I can identify a culprit.

Thanks,
Rodrigo.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2018-10-10 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 22:53 Rodrigo Vivi [this message]
2018-10-10 23:17 ` drm-intel-fixes CI issues David Airlie
2018-10-10 23:34   ` Lyude Paul
2018-10-11 19:38   ` Manasi Navare
2018-10-15 19:59   ` Lyude Paul
2018-10-15 21:20     ` Rodrigo Vivi
2018-10-15 21:31       ` Lyude Paul

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=20181010225335.GI6934@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=lyude@redhat.com \
    --cc=manasi.d.navare@intel.com \
    --cc=ville.syrjala@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 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.