intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Wait until after wm optimization to drop runtime PM reference
Date: Tue, 22 Mar 2016 18:25:03 +0200	[thread overview]
Message-ID: <1458663903.20080.60.camel@intel.com> (raw)
In-Reply-To: <20160322155619.GD20526@intel.com>

On ti, 2016-03-22 at 08:56 -0700, Matt Roper wrote:
> On Tue, Mar 22, 2016 at 04:17:58PM +0200, Imre Deak wrote:
> > On ti, 2016-03-22 at 15:51 +0200, Jani Nikula wrote:
> > > On Tue, 22 Mar 2016, Imre Deak <imre.deak@intel.com> wrote:
> > > > [ text/plain ]
> > > > On ti, 2016-03-08 at 09:26 -0800, Matt Roper wrote:
> > > > > On Mon, Mar 07, 2016 at 11:47:51AM +0000, Patchwork wrote:
> > > > > > == Series Details ==
> > > > > > 
> > > > > > Series: drm/i915: Wait until after wm optimization to drop
> > > > > > runtime
> > > > > > PM reference
> > > > > > URL   : https://patchwork.freedesktop.org/series/4135/
> > > > > > State : failure
> > > > > > 
> > > > > > == Summary ==
> > > > > > 
> > > > > > Series 4135v1 drm/i915: Wait until after wm optimization to
> > > > > > drop
> > > > > > runtime PM reference
> > > > > > http://patchwork.freedesktop.org/api/1.0/series/4135/revisi
> > > > > > ons/
> > > > > > 1/mb
> > > > > > ox/
> > > > > > 
> > > > > > Test kms_flip:
> > > > > >         Subgroup basic-flip-vs-wf_vblank:
> > > > > >                 fail       -> PASS       (bsw-nuc-2)
> > > > > >         Subgroup basic-plain-flip:
> > > > > >                 dmesg-warn -> PASS       (hsw-gt2)
> > > > > > Test kms_force_connector_basic:
> > > > > >         Subgroup force-load-detect:
> > > > > >                 pass       -> SKIP       (ivb-t430s)
> > > > > 
> > > > > https://bugs.freedesktop.org/show_bug.cgi?id=93769
> > > > > 
> > > > > > Test kms_pipe_crc_basic:
> > > > > >         Subgroup read-crc-pipe-c:
> > > > > >                 dmesg-warn -> PASS       (hsw-gt2)
> > > > > >         Subgroup suspend-read-crc-pipe-a:
> > > > > >                 dmesg-warn -> PASS       (skl-i5k-2)
> > > > > >                 skip       -> PASS       (hsw-brixbox)
> > > > > >         Subgroup suspend-read-crc-pipe-c:
> > > > > >                 pass       -> DMESG-WARN (bsw-nuc-2)
> > > > > 
> > > > > https://bugs.freedesktop.org/show_bug.cgi?id=93294
> > > > > 
> > > > > >                 pass       -> INCOMPLETE (hsw-gt2)
> > > > > 
> > > > > Seems like the machine just died completely?  No
> > > > > stdout/stderr/command/dmesg output available from CI and time
> > > > > is
> > > > > given
> > > > > as 0:00:00.  Doesn't seem like it could be related to this
> > > > > patch.
> > > > > 
> > > > > 
> > > > > > Test pm_rpm:
> > > > > >         Subgroup basic-pci-d3-state:
> > > > > >                 dmesg-warn -> PASS       (snb-dellxps)
> > > > > >         Subgroup basic-rte:
> > > > > >                 pass       -> DMESG-WARN (bsw-nuc-2)
> > > > > 
> > > > > https://bugs.freedesktop.org/show_bug.cgi?id=94164
> > > > > 
> > > > > 
> > > > > Matt
> > > > 
> > > > Pushed to -dinq, thanks for the patch and the review.
> > > > 
> > > > I had to rebase it on top of Ville's recent
> > > > s/crtc_state/old_crtc_state/ change, please double check it.
> > > > 
> > > > Jani, this is for -fixes.
> > > 
> > > Surely you added either
> > > 
> > > Cc: drm-intel-fixes@lists.freedesktop.org
> > > 
> > > or
> > > 
> > > Cc: stable@vger.kernel.org
> > > 
> > > in the commit when you pushed, then?
> > 
> > No, I haven't will do that in the future. Btw, what's the rule for
> > deciding that something is for -fixes or stable only after it's
> > been
> > pushed? Just ping you in case for -fixes and resend it in case of
> > stable?
> > 
> > --Imre
> 
> Are you sure we need this for -fixes?  The patch that introduced the
> regression isn't in drm-next/4.6 as far as I know.

The regressing commit ed4a6a7ca853 is in drm-intel-next, so I think we
do need it for -fixes.

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

  reply	other threads:[~2016-03-22 16:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 23:59 [PATCH] drm/i915: Wait until after wm optimization to drop runtime PM reference Matt Roper
2016-03-05  1:25 ` Imre Deak
2016-03-07 16:10   ` Matt Roper
2016-03-07 16:28     ` Imre Deak
2016-03-07 11:47 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-03-08 17:26   ` Matt Roper
2016-03-22 12:55     ` Imre Deak
2016-03-22 13:51       ` Jani Nikula
2016-03-22 14:17         ` Imre Deak
2016-03-22 15:56           ` Matt Roper
2016-03-22 16:25             ` Imre Deak [this message]
2016-03-22 16:31               ` Jani Nikula
2016-03-23  8:38                 ` Daniel Vetter
2016-03-07 11:53 ` [PATCH] " Maarten Lankhorst
2016-03-07 16:26   ` Matt Roper
2016-03-22 11:04 ` Ville Syrjälä

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=1458663903.20080.60.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=matthew.d.roper@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;
as well as URLs for NNTP newsgroup(s).