Bug 109549 - [ICL] piglit.spec.arb_compute_shader.render-and-compute GPU hang under load
Summary: [ICL] piglit.spec.arb_compute_shader.render-and-compute GPU hang under load
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Anuj Phogat
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2019-02-05 00:25 UTC by Mark Janes
Modified: 2019-09-25 20:31 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Mark Janes 2019-02-05 00:25:26 UTC
This test passes reliably by itself.

However, if you run the test while the piglit suite is running, it will quickly generate a gpu hang.

To reproduce:  in one window, execute the test in a loop:

  $ for ((;;)) do arb_compute_shader-render-and-compute -auto -fbo; done

Run `dmesg -w` to watch for gpu hangs

In a second window, run piglit.  GPU Hang will be produced within a few tests.
Comment 1 Mark Janes 2019-02-05 01:46:51 UTC
This gpu hang does not reproduce when testing Ken's pcx-3 branch, which reimplements all pipe control rules.
Comment 2 Anuj Phogat 2019-02-06 19:51:58 UTC
I followed the above steps on two different stepping Icelake systems but I couldn't reproduce it.
Comment 3 Mark Janes 2019-02-08 19:33:27 UTC
I can reproduce on ICL-01, ICL-02, and ICL-06 (C stepping).
Comment 4 Anuj Phogat 2019-02-13 18:06:04 UTC
I was finally able to reproduce the hang with longer run time on ICL systems. A recent finding is that disabling preemption in kernel fixes this hang. I didn't get a hang with preemption disabled and the test running overnight with piglit.
Comment 5 Anuj Phogat 2019-02-13 21:37:12 UTC
I also didn't get the hang on some of the older installed kernels on my ICL systems.
Comment 6 GitLab Migration User 2019-09-25 20:31:53 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1788.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.