From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98667] [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4)
Date: Wed, 09 Nov 2016 21:15:20 +0000 [thread overview]
Message-ID: <bug-98667-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1009 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98667
Bug ID: 98667
Summary: [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta
0.8.4)
Product: Mesa
Version: 11.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/i915
Assignee: dri-devel@lists.freedesktop.org
Reporter: xavier.l@magnax.ca
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 127882
--> https://bugs.freedesktop.org/attachment.cgi?id=127882&action=edit
GPU crash dump
GPU Hangs when running Redie Beta (https://rueckertbroductions.itch.io/redie).
The game crashes with the following error message:
> intel_do_flush_locked failed: Input/output error
I am running Ubuntu 16.04.1 (kernel 4.4.0-47-generic).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2576 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 reply other threads:[~2016-11-09 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 21:15 bugzilla-daemon [this message]
2016-11-09 21:16 ` [Bug 98667] [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4) bugzilla-daemon
2016-11-09 21:29 ` bugzilla-daemon
2016-11-09 21:31 ` bugzilla-daemon
2016-11-09 21:34 ` bugzilla-daemon
2019-09-18 19:40 ` 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-98667-502@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.