Bug 111385 - [SKL] (recoverable) GPU hang in (multi-context) SynMark HDRBloom
Summary: [SKL] (recoverable) GPU hang in (multi-context) SynMark HDRBloom
Status: NEW
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: high major
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks: 111444
  Show dependency treegraph
 
Reported: 2019-08-12 14:25 UTC by Eero Tamminen
Modified: 2019-08-21 09:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
i915 error state for GPU hang (4.73 KB, text/plain)
2019-08-12 14:25 UTC, Eero Tamminen
Details
SKL GT4e (recoverable) GPU hang (46.77 KB, text/plain)
2019-08-19 10:40 UTC, Eero Tamminen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eero Tamminen 2019-08-12 14:25:18 UTC
Created attachment 145037 [details]
i915 error state for GPU hang

Setup:
- SKL i5 6600K
- Ubuntu 16.04
- drm-tip git kernel (0330b51e91)
- Mesa git (5ed4e31c08d)
- Unity desktop

Test-case:
- 3x fullscreen FullHD HDRBloom multi-context SynMark test-case:
  synmark2 OglHdrBloom

Actual outcome:
- Recoverable GPU hang, but all successive GL tests fail after that:
  i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0

Main difference from this test to most other tests is only few tests use multiple contexts.

I haven't seen such hangs with the i965 driver.

I wasn't able to reproduce the hang after reboot when re-running HDRBloom 10 times, so it may depend on previous tests, or is just very hard to reproduce.

I didn't see such hang when running similar test-sets month ago, so it can be a regression.

On BXT there was a hang in a different test-case.
Comment 1 Eero Tamminen 2019-08-12 16:09:57 UTC
(In reply to Eero Tamminen from comment #0)
> I wasn't able to reproduce the hang after reboot when re-running HDRBloom 10
> times, so it may depend on previous tests, or is just very hard to reproduce.

Was able to reproduce the GPU hang with Iris by running each SynMark test 3x in alphabetical order.  At HdrBloom there was again GPU hang.  This time tests after HdrBloom didn't fail.
Comment 2 Eero Tamminen 2019-08-19 08:21:00 UTC
Got a (non-recoverable) HdrBloom hang also with i965 when using latest Git gfx stack, on SKL GT4e (SkullCanyon), so this might not be Iris specific issue.
Comment 3 Eero Tamminen 2019-08-19 10:40:46 UTC
Created attachment 145096 [details]
SKL GT4e (recoverable) GPU hang

In the SKL GT4e / i965 case, recoverable GPU hang during HdrBloom run appears to be happening in the X server.

If same was true also of the SKL GT2 case (i915 error state didn't specify process), then that's also i965, as I was running only the benchmark itself with Iris on SKL GT2.
Comment 4 Eero Tamminen 2019-08-19 10:50:49 UTC
Last night HdrBloom test had a (non-recoverable) GPU hang (something had at least broken test automation network connection during that exact test).  Moving to i965, as Iris isn't yet enabled by default and this happens (also) with i965.


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.