From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [01/10] drm/i915: Add windowing for primary planes on gen2/3 and chv
Date: Wed, 5 Jun 2019 18:48:02 +0300 [thread overview]
Message-ID: <20190605154802.GP5942@intel.com> (raw)
In-Reply-To: <52ef0b6c-1d98-8da7-299a-2a350a841599@linux.intel.com>
On Wed, Jun 05, 2019 at 04:01:05PM +0200, Maarten Lankhorst wrote:
> Op 31-05-2019 om 15:05 schreef Ville Syrjälä:
> > On Thu, May 30, 2019 at 05:43:00AM -0000, Patchwork wrote:
> >> == Series Details ==
> >>
> >> Series: series starting with [01/10] drm/i915: Add windowing for primary planes on gen2/3 and chv
> >> URL : https://patchwork.freedesktop.org/series/61345/
> >> State : failure
> >>
> >> == Summary ==
> >>
> >> CI Bug Log - changes from CI_DRM_6165_full -> Patchwork_13133_full
> >> ====================================================
> >>
> >> Summary
> >> -------
> >>
> >> **FAILURE**
> >>
> >> Serious unknown changes coming with Patchwork_13133_full absolutely need to be
> >> verified manually.
> >>
> >> If you think the reported changes have nothing to do with the changes
> >> introduced in Patchwork_13133_full, please notify your bug team to allow them
> >> to document this new failure mode, which will reduce false positives in CI.
> >>
> >>
> >>
> >> Possible new issues
> >> -------------------
> >>
> >> Here are the unknown changes that may have been introduced in Patchwork_13133_full:
> >>
> >> ### IGT changes ###
> >>
> >> #### Possible regressions ####
> >>
> >> * igt@kms_plane@pixel-format-pipe-a-planes:
> >> - shard-glk: [PASS][1] -> [FAIL][2]
> >> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6165/shard-glk3/igt@kms_plane@pixel-format-pipe-a-planes.html
> >> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13133/shard-glk8/igt@kms_plane@pixel-format-pipe-a-planes.html
> > <7> [125.370679] [drm:drm_mode_debug_printmodeline] Modeline "1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x48 0x5
> > ...
> > <7> [125.542650] [drm:intel_dump_cdclk_state [i915]] Changing CDCLK to 79200 kHz, VCO 633600 kHz, ref 19200 kHz, bypass 19200 kHz, voltage
> > level 4
> > ...
> > <7> [133.682144] [drm:skl_check_pipe_max_pixel_rate [i915]] Max supported pixel clock with scaling exceeded
> >
> > Max pixel rate for 64bpp is 79.2*2 * 8/9 = 140.8 Mhz, which we are
> > exceeding. We'd need some way to bump the cdclk for this case, but
> > the kernel will only do that for modesets, and it won't account for
> > that 8/9 factor. Not sure there is a great way to handle these sorts
> > of cases.
> >
> >> * igt@kms_plane_scaling@pipe-c-scaler-with-pixel-format:
> >> - shard-apl: [PASS][3] -> [FAIL][4] +4 similar issues
> >> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6165/shard-apl5/igt@kms_plane_scaling@pipe-c-scaler-with-pixel-format.html
> >> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13133/shard-apl7/igt@kms_plane_scaling@pipe-c-scaler-with-pixel-format.html
> > <7> [1749.831610] [drm:drm_atomic_helper_check_plane_state] Invalid scaling of plane
> > <7> [1749.831620] [drm:drm_rect_debug_print] src: 8.000000x8.000000+0.000000+0.000000
> > <7> [1749.831625] [drm:drm_rect_debug_print] dst: 1920x1080+0+0
> >
> > Not quite sure what's going on here. Unfortunately the debugs don't have
> > enough information to see what's going on.
>
> For first 6 patches
>
> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Thanks.
>
> What happens on < gen9 btw with half float support?
>
> Enabling patches look sane, but worried about hw coverage.
>
> So if you are sure it works on <gen9 for those on all clocks, go ahead and add my r-b on those too. But I would like to have no regressions so have to get gen9 fixed first before pushing. :)
We do have some missing checks for the cdclk vs. fp16 case on pre-gen9,
as well as missing similar cdclk vs. scaling checks. I think I have some
kind of plan to remedy that. And I can probably tweak that into bumping
the cdclk for fp16 as well (assuming a modeset is allowed for the commit
in question of course).
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-05 15:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 16:05 [PATCH 01/10] drm/i915: Add windowing for primary planes on gen2/3 and chv Ville Syrjala
2019-05-29 16:05 ` [PATCH 02/10] drm/i915: Disable sprite gamma on ivb-bdw Ville Syrjala
2019-05-29 16:05 ` [PATCH 03/10] drm/i915: Program plane gamma ramps Ville Syrjala
2019-05-29 16:05 ` [PATCH 04/10] drm/i915: Deal with cpp==8 for g4x watermarks Ville Syrjala
2019-05-29 16:06 ` [PATCH 05/10] drm/i915: Cosmetic fix for skl+ plane switch statement Ville Syrjala
2019-05-29 16:06 ` [PATCH 06/10] drm/i915: Clean up skl vs. icl plane formats Ville Syrjala
2019-05-29 16:06 ` [PATCH 07/10] drm/i915: Add support for half float framebuffers for skl+ Ville Syrjala
2019-05-29 16:06 ` [PATCH 08/10] drm/i915: Add support for half float framebuffers for gen4+ primary planes Ville Syrjala
2019-05-29 16:06 ` [PATCH 09/10] drm/i915: Add support for half float framebuffers for ivb+ sprites Ville Syrjala
2019-05-29 16:06 ` [PATCH 10/10] drm/i915: Add support for half float framebuffers on snb sprites Ville Syrjala
2019-05-29 17:38 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/10] drm/i915: Add windowing for primary planes on gen2/3 and chv Patchwork
2019-05-29 17:42 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-05-29 18:12 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-30 5:43 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-05-31 13:05 ` Ville Syrjälä
2019-06-05 14:01 ` Maarten Lankhorst
2019-06-05 15:48 ` Ville Syrjälä [this message]
2019-06-05 15:44 ` Ville Syrjälä
2019-05-31 8:13 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-31 16:55 ` ✗ Fi.CI.IGT: failure " Patchwork
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=20190605154802.GP5942@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@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 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.