All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107377] [CI][DRMTIP] igt@gem_gpgpu_fill - fail - Test assertion failure function gen7_render_flush, Failed assertion: ret == 0, Last errno: 5, Input/output error
Date: Wed, 25 Jul 2018 15:24:29 +0000	[thread overview]
Message-ID: <bug-107377-502-OnMwy4tR3O@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107377-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1424 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107377

Chris Wilson <chris@chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         QA Contact|intel-gfx-bugs@lists.freede |
                   |sktop.org                   |
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
          Component|DRM/Intel                   |IGT
           Assignee|intel-gfx-bugs@lists.freede |dri-devel@lists.freedesktop
                   |sktop.org                   |.org

--- Comment #1 from Chris Wilson <chris@chris-wilson.co.uk> ---
The gpu was never the same after the hang in kms_draw_crc, and it ended up
being declared wedged when a reset failed shortly after in perf.

commit 3806547319038879f1c7939671b9e35937f0cae6
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Jul 12 16:22:51 2018 +0100

    igt/gem_gpgpu_fill: Check for GEM before use

    As we need GEM and the GPU to do a GPGPU fill, we should check that it
    is operable before using -- skipping rather than failing when the device
    is wedged.

    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3784 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

       reply	other threads:[~2018-07-25 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-107377-502@http.bugs.freedesktop.org/>
2018-07-25 15:24 ` bugzilla-daemon [this message]
2018-08-24  5:51 ` [Bug 107377] [CI][DRMTIP] igt@gem_gpgpu_fill - fail - Test assertion failure function gen7_render_flush, Failed assertion: ret == 0, Last errno: 5, Input/output error bugzilla-daemon
2018-08-28  6:31 ` bugzilla-daemon
2018-08-30 12:34 ` 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-107377-502-OnMwy4tR3O@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 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.