From: Matt Roper <matthew.d.roper@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add two-stage ILK-style watermark programming (v11)
Date: Mon, 29 Feb 2016 08:42:30 -0800 [thread overview]
Message-ID: <20160229164230.GG20607@intel.com> (raw)
In-Reply-To: <56D3FFF2.1080701@linux.intel.com>
On Mon, Feb 29, 2016 at 09:23:14AM +0100, Maarten Lankhorst wrote:
> Op 25-02-16 om 17:48 schreef Matt Roper:
> > I never got a CI email for this (probably because fdo was down for a while),
> > but I can see the results below in patchwork
> >
> >> Test gem_cs_prefetch:
> >> Subgroup basic-default:
> >> incomplete -> PASS (ilk-hp8440p)
> >> Test kms_flip:
> >> Subgroup basic-flip-vs-dpms:
> >> pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
> > Pre-existing watermark bug here:
> > https://bugs.freedesktop.org/show_bug.cgi?id=93787
> >
> > I had hoped this patch might also fix that problem, but I guess further
> > investigation will be needed; it seems to be something very
> > ILK-specific, not seen on SNB, IVB, etc.
> >
> >
> >> Test kms_force_connector_basic:
> >> Subgroup force-edid:
> >> skip -> PASS (snb-x220t)
> >> pass -> SKIP (ivb-t430s)
> > Pre-existing:
> > https://bugs.freedesktop.org/show_bug.cgi?id=93769
> >
> >> Subgroup force-load-detect:
> >> dmesg-fail -> FAIL (snb-x220t)
> >> dmesg-fail -> FAIL (hsw-gt2)
> > The dmesg warning is gone now (a locking warning that I don't think my
> > patch should have affected); the remaining test failure is identical to
> > what it was before (temp->connection != DRM_MODE_UNKNOWNCONNECTION) and
> > unrelated.
> >
> > I don't see a bugzilla for this, which seems strange since it's a
> > pre-existing defect. Am I overlooking it or do I need to file a new
> > one?
> >
> >> fail -> SKIP (ilk-hp8440p)
> > Not sure what is actually plugged into the CI machine, so the skip may
> > be legitimate/expected? Doesn't seem related to anything in my patch
> > anyway.
> >
> >> Test kms_pipe_crc_basic:
> >> Subgroup suspend-read-crc-pipe-c:
> >> pass -> DMESG-WARN (bsw-nuc-2)
> > This one was happening sporadically before my patch; I think it's the
> > same bug filed here:
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=94164
> >
> > I'll update the bugzilla to indicate it also happens on this test.
> >
> >> Test pm_rpm:
> >> Subgroup basic-rte:
> >> pass -> DMESG-WARN (bsw-nuc-2)
> >> fail -> PASS (hsw-brixbox)
> > Same bug mentioned above (94164)
> >
> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Thanks for the review. Pushed to dinq.
Matt
--
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-29 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 1:20 [PATCH] drm/i915: Add two-stage ILK-style watermark programming (v11) Matt Roper
2016-02-24 1:24 ` Matt Roper
2016-02-24 8:20 ` Maarten Lankhorst
2016-02-25 16:48 ` Matt Roper
2016-02-29 8:23 ` Maarten Lankhorst
2016-02-29 16:42 ` Matt Roper [this message]
2016-02-29 19:52 ` Imre Deak
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=20160229164230.GG20607@intel.com \
--to=matthew.d.roper@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.