Bug 73959 - [BYT/BDW]igt/many gem_reset_stats subcases causes <3>[ 542.526239] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!
Summary: [BYT/BDW]igt/many gem_reset_stats subcases causes <3>[ 542.526239] [drm:i915...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Mika Kuoppala
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-23 06:57 UTC by lu hua
Modified: 2017-10-06 14:40 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (110.00 KB, text/plain)
2014-01-23 06:57 UTC, lu hua 		no flags Details
/sys/class/drm/card0/error (2.76 MB, text/plain)
2014-01-23 06:58 UTC, lu hua 		no flags Details
View All

Description lu hua 2014-01-23 06:57:28 UTC 
Created attachment 92639 [details]
dmesg

System Environment:
--------------------------
Platform: Broadwell
Kernel(drm-intel-nightly)83ac01f486397fd8d319a3e31d1f95beb05037c5

Bug detailed description:
------------------------- 
Many gem_reset_stats subcases causes [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
These subcases are new cases.

run it on Broadwell wiht -nightly kernel.

run ./gem_reset_stats --run-subtest ban-ctx-render
output:
IGT-Version: 1.5-g1bbb607 (x86_64) (Linux: 3.13.0-rc8_drm-intel-nightly_83ac01_20140123+ x86_64)
Subtest ban-ctx-render: SUCCESS

dmesg -r | egrep "<[1-3]>" |grep drm
<3>[    2.004178] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
<3>[  536.559270] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
<3>[  536.572264] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
<3>[  536.581261] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
<3>[  536.590257] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
<3>[  542.526239] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!
<3>[  542.539123] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
<3>[  542.553117] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
<3>[  543.333157] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
<3>[  543.342834] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.

Reproduce steps:
-------------------------
1. ./gem_reset_stats --run-subtest ban-ctx-render
Comment 1 lu hua 2014-01-23 06:58:43 UTC 
Created attachment 92640 [details]
/sys/class/drm/card0/error
Comment 2 Mika Kuoppala 2014-02-05 14:46:03 UTC 
Fixed by

commit 3fac8978f5d353d350215d7d8dae977d65305f64
Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Date:   Thu Jan 30 16:05:48 2014 +0200

    drm/i915: Tune down debug output when context is banned


Forcewake warnings are related to hw init, which is triggered by hang recovery reset.
Comment 3 lu hua 2014-02-07 07:41:40 UTC 
<3>[  542.526239] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned! goes away.

<3>[    1.827367] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear. still exists.
Comment 4 lu hua 2014-02-11 03:11:18 UTC 
(In reply to comment #3)
> <3>[  542.526239] [drm:i915_context_is_banned] *ERROR* context hanging too
> fast, declaring banned! goes away.
> 

This error goes away, close this bug.

> <3>[    1.827367] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out
> waiting for forcewake old ack to clear. still exists.

This error reports after boot system. Track it via Bug 68575.
Comment 5 Elizabeth 2017-10-06 14:40:10 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.