Bug 85358 - [BSW Regression]igt/gem_ctx_exec/reset-pin-leak causes *ERROR* Timed out: waiting for Render to ack
Summary: [BSW Regression]igt/gem_ctx_exec/reset-pin-leak causes *ERROR* Timed out: wai...
Status: CLOSED DUPLICATE of bug 85684
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-23 07:03 UTC by lu hua
Modified: 2017-10-06 14:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (64.74 KB, text/plain)
2014-10-23 07:03 UTC, lu hua 		no flags Details
View All

Description lu hua 2014-10-23 07:03:33 UTC 
Created attachment 108284 [details]
dmesg

==System Environment==
--------------------------
Regression: YES
good commit: bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9
bad commit:  03a3780b0c82183110dbea7c7037a61686685511

Non-working platforms: BSW

==kernel==
--------------------------
drm-intel-nightly/77683b77aa4da6e1788838dad2d2a15b0dfc290

==Bug detailed description==
-----------------------------
It happens on BSW with -fixes and -nightly kernel. It works well on -queued kernel.
Run ./gem_ctx_exec --run-subtest reset-pin-leak, reports [drm:__vlv_force_wake_get [i915]] *ERROR* Timed out: waiting for Render to ack.

output:
IGT-Version: 1.8-g303fe74 (x86_64) (Linux: 3.18.0-rc1_drm-intel-nightly_77683b_20141023+ x86_64)
Subtest reset-pin-leak: SUCCESS (81.771s)

==Reproduce steps==
---------------------------- 
1. ./gem_ctx_exec --run-subtest reset-pin-leak
Comment 1 lu hua 2014-10-23 08:11:52 UTC 
igt/gem_reset_stats/ban-vebox also has this issue.
Comment 2 Mika Kuoppala 2014-11-04 14:39:57 UTC 

*** This bug has been marked as a duplicate of bug 85684 ***
Comment 3 Elizabeth 2017-10-06 14:34:27 UTC 
Closing old verified.

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.