From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Patchwork <patchwork@emeril.freedesktop.org>,
intel-gfx@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Simplify GuC communication handling
Date: Wed, 11 Dec 2019 11:52:56 +0000 [thread overview]
Message-ID: <157606517644.17013.8313937200366061802@skylake-alporthouse-com> (raw)
In-Reply-To: <157606401531.30694.17711325934199183765@emeril.freedesktop.org>
Quoting Patchwork (2019-12-11 11:33:35)
> #### Possible regressions ####
>
> * igt@gem_exec_parallel@rcs0-contexts:
> - shard-iclb: [PASS][1] -> [CRASH][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7534/shard-iclb4/igt@gem_exec_parallel@rcs0-contexts.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15681/shard-iclb7/igt@gem_exec_parallel@rcs0-contexts.html
Where did __gem_execbuf() == -25 [ENOTTY] come from?
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-12-11 11:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 21:09 [Intel-gfx] [PATCH 0/5] Simplify GuC communication handling Daniele Ceraolo Spurio
2019-12-10 21:09 ` [Intel-gfx] [PATCH 1/5] drm/i915/guc: Merge communication_stop and communication_disable Daniele Ceraolo Spurio
2019-12-11 13:12 ` Michal Wajdeczko
2019-12-10 21:09 ` [Intel-gfx] [PATCH 2/5] drm/i915/guc/ct: stop expecting multiple CT channels Daniele Ceraolo Spurio
2019-12-11 13:43 ` Michal Wajdeczko
2019-12-11 17:47 ` Daniele Ceraolo Spurio
2019-12-10 21:09 ` [Intel-gfx] [PATCH 3/5] drm/i915/guc: remove function pointers for send/receive calls Daniele Ceraolo Spurio
2019-12-11 14:04 ` Michal Wajdeczko
2019-12-11 18:01 ` Daniele Ceraolo Spurio
2019-12-10 21:09 ` [Intel-gfx] [PATCH 4/5] drm/i915/guc: unify notify() functions Daniele Ceraolo Spurio
2019-12-11 14:26 ` Michal Wajdeczko
2019-12-10 21:09 ` [Intel-gfx] [PATCH 5/5] HAX: force enable_guc=2 and WA i915#571 Daniele Ceraolo Spurio
2019-12-11 5:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Simplify GuC communication handling Patchwork
2019-12-11 5:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-11 11:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2019-12-11 11:52 ` 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=157606517644.17013.8313937200366061802@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=daniele.ceraolospurio@intel.com \
--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.