From: Chris Wilson <chris@chris-wilson.co.uk>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for lib: Ask the kernel to quiescent the GPU (rev2)
Date: Wed, 04 Oct 2017 10:34:29 +0100 [thread overview]
Message-ID: <150710966910.15255.8715362063502592398@mail.alporthouse.com> (raw)
In-Reply-To: <150706319131.15255.14583839442097763820@mail.alporthouse.com>
Quoting Chris Wilson (2017-10-03 21:39:51)
> Quoting Patchwork (2017-10-03 17:07:51)
> > == Series Details ==
> >
> > Series: lib: Ask the kernel to quiescent the GPU (rev2)
> > URL : https://patchwork.freedesktop.org/series/30890/
> > State : failure
> >
> > == Summary ==
> >
> > IGT patchset tested on top of latest successful build
> > 0045085c632a1cf5b4e9272304ee0e61ff9a7e6f lib: Report the error from __gem_create()
> >
> > with latest DRM-Tip kernel build CI_DRM_3167
> > 5a0359bf59aa drm-tip: 2017y-10m-03d-13h-34m-56s UTC integration manifest
> >
> > No testlist changes.
> >
> > Test chamelium:
> > Subgroup dp-crc-fast:
> > pass -> FAIL (fi-kbl-7500u) fdo#102514
> > Test gem_sync:
> > Subgroup basic-all:
> > pass -> DMESG-FAIL (fi-blb-e6850)
> > pass -> FAIL (fi-pnv-d510)
>
> Still all clean on my own pnv n570. Both of those are desktop, whereas
> mine is a mobile part, but that shouldn't make any difference...
5,000 iterations later, still no missed breadcrumb or GPU hang. Most
peculiar.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-10-04 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 13:46 [CI igt] lib: Ask the kernel to quiescent the GPU Chris Wilson
2017-10-03 16:07 ` ✗ Fi.CI.BAT: failure for lib: Ask the kernel to quiescent the GPU (rev2) Patchwork
2017-10-03 20:39 ` Chris Wilson
2017-10-04 9:34 ` Chris Wilson [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=150710966910.15255.8715362063502592398@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
/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.