public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: intel-gfx@lists.freedesktop.org,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: CI igt-all on drm-intel-next-fixes gem_exec_* and other gem_*
Date: Wed, 31 Jan 2018 22:10:20 -0800	[thread overview]
Message-ID: <20180201061019.vdfd67zhohfrartc@intel.com> (raw)

Hi guys,

As we run more rounds of CI on drm-intel-next-fixes
a standard gets visible there.

This round of dinf started with CI_DINF_90.

Specially gem_exec_* but also other gem_* tests fails randomly
on gen9 platforms:

https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/shards.html
(last 5 columns of gen9 platforms)

while it is pure clean green on drm-tip:

https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html

From the logs I looked it seems that it is always during hibernation
and most of the times some strange page faults and also not
only i915:

<6>[   36.647941] PM: Image saving progress:  70%
<3>[   36.707234] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:

Do you know what could justify this difference?

Is there anything we could we be missing on our side?

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

             reply	other threads:[~2018-02-01  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01  6:10 Rodrigo Vivi [this message]
2018-02-01 21:00 ` CI igt-all on drm-intel-next-fixes gem_exec_* and other gem_* Rodrigo Vivi
2018-02-01 21:22   ` Chris Wilson

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=20180201061019.vdfd67zhohfrartc@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=joonas.lahtinen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox