[Bug 82640] [CTG] GPU HANG: ecode -1:0x00000000, reason: Command parser error, iir 0x07fcc000, action: continue
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Aug 20 07:20:30 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=82640
--- Comment #2 from Vladimir Volovich <vvv at vsu.ru> ---
I'm using the package libgl1-mesa-dri version 10.2.5-1 from Debian sid. I
can try a different version if you'll let me know which one I should try.
I'm not sure at all what is the cause of this bug (whether it is related to
a kernel upgrade). I've been observing such problem for a several months
now. Usually it is triggered after opening many tabs in Google Chrome (i'm
using chrome unstable builds, such as 38.0.2125). When this was happening
on linux 3.14 and below, the problem was manifesting in having a segfault
in google chrome process, after which chrome was still running, but was
stuck (its windows became unresponsive). Restarting google chrome was not
possible, as it continued to be unresponsive. I needed a reboot to restore
things to normal operation. However after upgrading to linux 3.16, even
after receiving a segfault, chrome remained responsive, and I can still use
it (restarting it also works). I'm not at all sure where this GPU HANG
problem comes from.
On Tue, Aug 19, 2014 at 9:58 PM, <bugzilla-daemon at freedesktop.org> wrote:
> Jesse Barnes <jbarnes at virtuousgeek.org> changed bug 82640
> <https://bugs.freedesktop.org/show_bug.cgi?id=82640>
> What Removed Added Summary GPU HANG: ecode -1:0x00000000, reason:
> Command parser error, iir 0x07fcc000, action: continue [CTG] GPU HANG:
> ecode -1:0x00000000, reason: Command parser error, iir 0x07fcc000, action:
> continue
>
> *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=82640#c1> on
> bug 82640 <https://bugs.freedesktop.org/show_bug.cgi?id=82640> from Jesse
> Barnes <jbarnes at virtuousgeek.org> *
>
> Hm a command parser error on Cantiga... have you tried different versions of
> the i965 DRI driver in Mesa? Or are you sure it's related to a kernel upgrade?
> If so, a bisect would really help narrow things down.
>
> ------------------------------
> You are receiving this mail because:
>
> - You reported the bug.
>
>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140820/486c77ef/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list