[Bug 94924] [GEN8+] Ungine Valley fails to run due to "intel_do_flush_locked failed: Input/output error"
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Apr 13 16:33:38 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=94924
Bug ID: 94924
Summary: [GEN8+] Ungine Valley fails to run due to
"intel_do_flush_locked failed: Input/output error"
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/i965
Assignee: idr at freedesktop.org
Reporter: eero.t.tamminen at intel.com
QA Contact: intel-3d-bugs at lists.freedesktop.org
Ungine Valley fails to run due to "intel_do_flush_locked failed: Input/output
error" with latest Mesa.
This started to happen on BDW/BSW/SKL ~31st of March, but it doesn't happen on
IVB/HSW/BYT,
Automated bisecting on BDW & SKL gave the same commit as trigger to this:
---------------------------------------------------------
commit b4e223cfbf4d46e2ca4c7313f4ebd52798d21551
Author: Matt Turner <mattst88 at gmail.com>
Date: Mon Feb 15 10:43:39 2016 -0800
i965: Remove NOP insertion kludge in scheduler.
Instead of removing every instruction in add_insts_from_block(), just
move the instruction to its scheduled location. This is a step towards
doing both bottom-up and top-down scheduling without conflicts.
Note that this patch changes cycle counts for programs because it begins
including control flow instructions in the estimates.
Reviewed-by: Francisco Jerez <currojerez at riseup.net>
---------------------------------------------------------
This happens both on:
- Ubuntu 15.10 with DRI3 + latest 4.6-rc kernel & latest X, and
- Ubuntu 16.04 with DRI2 + Ubuntu kernel (i.e. 4.4 + 4.6 i915 forklift) & X
(There have been similar issues with SynMark Multithread test, but those aren't
100% reproducible like this.)
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160413/f7f483fc/attachment.html>
More information about the intel-3d-bugs
mailing list