Bug 71725 - [IVB Regression]boot system has <3>[ 0.753474] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
Summary: [IVB Regression]boot system has <3>[ 0.753474] [drm:__gen6_gt_force_wake_m...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Daniel Vetter
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-18 07:42 UTC by lu hua
Modified: 2017-10-06 14:42 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (85.39 KB, text/plain)
2013-11-18 07:42 UTC, lu hua 		no flags Details
View All

Description lu hua 2013-11-18 07:42:35 UTC 
Created attachment 89386 [details]
dmesg

System Environment:
--------------------------
Platform:  Ivybridge
Kernel: (drm-intel-fixes)29c78f609e661e663a239a37923adb1d61f6386c

Bug detailed description:
-----------------------------
Boot system, <3>[    0.753474] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear. appears in mdesg.
It happens on ivybridge with -nightly and -fixes kernel. It doesn't happen on -queued kernel.

The latest known good commit:1fbc0d789d12fec313c91912fc11733fdfbab863
The latest known bad commit:29c78f609e661e663a239a37923adb1d61f6386c

Reproduce steps:
----------------------------
1. clear boot system
2. dmesg -r | egrep "<[1-3]>" |grep drm
Comment 1 Daniel Vetter 2013-11-18 08:08:12 UTC 
Good chance this is fixed with

commit ef46e0d247da0a7a408573aa15870e231bbd4af2
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Sat Nov 16 16:00:09 2013 +0100

    drm/i915: restore the early forcewake cleanup
Comment 2 lu hua 2013-11-20 07:11:50 UTC 
Verified.Fixed.
Comment 3 Gordon Jin 2014-01-03 01:51:14 UTC 
(give the credit to Daniel)
Comment 4 Elizabeth 2017-10-06 14:42:03 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.