From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104284] [IGT] some gem_exec_fence Failed assertion: __gem_execbuf(fd, execbuf) == 0
Date: Wed, 21 Feb 2018 11:24:08 +0000 [thread overview]
Message-ID: <bug-104284-502-ccGifI2HdW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104284-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1052 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104284
Chris Wilson <chris@chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
QA Contact|intel-gfx-bugs@lists.freede |
|sktop.org |
Component|DRM/Intel |IGT
Resolution|--- |FIXED
Assignee|intel-gfx-bugs@lists.freede |dri-devel@lists.freedesktop
|sktop.org |.org
Status|NEW |RESOLVED
--- Comment #17 from Chris Wilson <chris@chris-wilson.co.uk> ---
commit 960e55a87d7b7d7385063e37cc9f281df2be8037 (upstream/master,
origin/master, origin/HEAD)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Tue Oct 24 12:05:23 2017 +0100
igt/gem_ctx_isolation: Check isolation of registers between contexts
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3042 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next parent reply other threads:[~2018-02-21 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-104284-502@http.bugs.freedesktop.org/>
2018-02-21 11:24 ` bugzilla-daemon [this message]
2018-08-23 19:13 ` [Bug 104284] [IGT] some gem_exec_fence Failed assertion: __gem_execbuf(fd, execbuf) == 0 bugzilla-daemon
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=bug-104284-502-ccGifI2HdW@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).