From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v2 RESEND] tests/kms_fbcon_fbt: Report fbc_status on error
Date: Mon, 06 Nov 2017 18:00:32 -0200 [thread overview]
Message-ID: <1509998432.2586.19.camel@intel.com> (raw)
In-Reply-To: <87y3njxofu.fsf@dilma.collabora.co.uk>
Em Seg, 2017-11-06 às 16:16 -0200, Gabriel Krisman Bertazi escreveu:
> Paulo Zanoni <paulo.r.zanoni@intel.com> writes:
>
> > Em Seg, 2017-10-30 às 15:54 -0200, Gabriel Krisman Bertazi
> > escreveu:
> > > knowing the assertion triggered on wait_until_enabled() is not
> > > that
> > > useful without knowing what exactly caused the failure. It might
> > > be
> > > an
> > > user error, like too little stolen memory by the bios, or an
> > > actual
> > > issue in the kernel. So, let's make life easier, particularly
> > > for
> > > the
> > > CI, by printing the status before failing out.
> > >
> > > Case in point:
> > >
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101718
> > >
> > > Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
> > > ---
> > > tests/kms_fbcon_fbt.c | 24 ++++++++++++++++++++++--
> > > 1 file changed, 22 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/tests/kms_fbcon_fbt.c b/tests/kms_fbcon_fbt.c
> > > index d0090912694e..8371be5612f5 100644
> > > --- a/tests/kms_fbcon_fbt.c
> > > +++ b/tests/kms_fbcon_fbt.c
> > > @@ -95,6 +95,14 @@ static bool
> > > connector_can_fbc(drmModeConnectorPtr
> > > connector)
> > > return true;
> > > }
> > >
> > > +static void fbc_print_status(int fd)
> > > +{
> > > + static char buf[128];
> > > +
> > > + igt_debugfs_read(fd, "i915_fbc_status", buf);
> > > + igt_debug("FBC status: %s\n", buf);
> > > +}
> > > +
> > > static bool fbc_is_enabled(int fd)
> > > {
> > > char buf[128];
> > > @@ -105,7 +113,9 @@ static bool fbc_is_enabled(int fd)
> > >
> > > static bool fbc_wait_until_enabled(int fd)
> > > {
> > > - return igt_wait(fbc_is_enabled(fd), 5000, 1);
> > > + bool r = igt_wait(fbc_is_enabled(fd), 5000, 1);
> > > + fbc_print_status(fd);
> > > + return r;
> > > }
> > >
> > > typedef bool (*connector_possible_fn)(drmModeConnectorPtr
> > > connector);
> > > @@ -160,6 +170,14 @@ static bool
> > > connector_can_psr(drmModeConnectorPtr connector)
> > > return (connector->connector_type ==
> > > DRM_MODE_CONNECTOR_eDP);
> > > }
> > >
> > > +static void psr_print_status(int fd)
> > > +{
> > > + static char buf[256];
> > > +
> > > + igt_debugfs_read(fd, "i915_edp_psr_status", buf);
> > > + igt_debug("FBC status: %s\n", buf);
> >
> > s/FBC/PSR/
>
> Oops!
>
> >
> > With that fixed:
> > Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> Hi Paulo,
>
> Thanks for your review. Can you push the version below, then? I
> don't
> have commit rights on igt.
Pushed. Thanks for the patch!
>
> > 8
>
> Subject: [PATCH i-g-t] tests/kms_fbcon_fbt: Report fbc_status on
> error
>
> knowing the assertion triggered on wait_until_enabled() is not that
> useful without knowing what exactly caused the failure. It might be
> an
> user error, like too little stolen memory by the bios, or an actual
> issue in the kernel. So, let's make life easier, particularly for
> the
> CI, by printing the status before failing out.
>
> Case in point:
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101718
>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
> Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> ---
> tests/kms_fbcon_fbt.c | 24 ++++++++++++++++++++++--
> 1 file changed, 22 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_fbcon_fbt.c b/tests/kms_fbcon_fbt.c
> index d0090912694e..51f1172839ed 100644
> --- a/tests/kms_fbcon_fbt.c
> +++ b/tests/kms_fbcon_fbt.c
> @@ -95,6 +95,14 @@ static bool connector_can_fbc(drmModeConnectorPtr
> connector)
> return true;
> }
>
> +static void fbc_print_status(int fd)
> +{
> + static char buf[128];
> +
> + igt_debugfs_read(fd, "i915_fbc_status", buf);
> + igt_debug("FBC status: %s\n", buf);
> +}
> +
> static bool fbc_is_enabled(int fd)
> {
> char buf[128];
> @@ -105,7 +113,9 @@ static bool fbc_is_enabled(int fd)
>
> static bool fbc_wait_until_enabled(int fd)
> {
> - return igt_wait(fbc_is_enabled(fd), 5000, 1);
> + bool r = igt_wait(fbc_is_enabled(fd), 5000, 1);
> + fbc_print_status(fd);
> + return r;
> }
>
> typedef bool (*connector_possible_fn)(drmModeConnectorPtr
> connector);
> @@ -160,6 +170,14 @@ static bool
> connector_can_psr(drmModeConnectorPtr connector)
> return (connector->connector_type ==
> DRM_MODE_CONNECTOR_eDP);
> }
>
> +static void psr_print_status(int fd)
> +{
> + static char buf[256];
> +
> + igt_debugfs_read(fd, "i915_edp_psr_status", buf);
> + igt_debug("PSR status: %s\n", buf);
> +}
> +
> static bool psr_is_enabled(int fd)
> {
> char buf[256];
> @@ -170,7 +188,9 @@ static bool psr_is_enabled(int fd)
>
> static bool psr_wait_until_enabled(int fd)
> {
> - return igt_wait(psr_is_enabled(fd), 5000, 1);
> + bool r = igt_wait(psr_is_enabled(fd), 5000, 1);
> + psr_print_status(fd);
> + return r;
> }
>
> struct feature {
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-11-06 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 17:54 [PATCH i-g-t v2 RESEND] tests/kms_fbcon_fbt: Report fbc_status on error Gabriel Krisman Bertazi
2017-10-30 18:23 ` ✓ Fi.CI.BAT: success for tests/kms_fbcon_fbt: Report fbc_status on error (rev3) Patchwork
2017-10-30 19:15 ` ✓ Fi.CI.IGT: " Patchwork
2017-11-06 16:43 ` [PATCH i-g-t v2 RESEND] tests/kms_fbcon_fbt: Report fbc_status on error Paulo Zanoni
2017-11-06 18:16 ` Gabriel Krisman Bertazi
2017-11-06 20:00 ` Paulo Zanoni [this message]
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=1509998432.2586.19.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krisman@collabora.co.uk \
/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.