Bug 76823 - [IVB]Calltrace after running drv_suspend/forcewake:WARNING: CPU: 1 PID: 4409 at drivers/gpu/drm/i915/intel_uncore.c:460 gen6_gt_force_wake_put+0xed/0x13c [i915]()
Summary: [IVB]Calltrace after running drv_suspend/forcewake:WARNING: CPU: 1 PID: 4409 ...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Paulo Zanoni
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-31 08:52 UTC by Guo Jinxian
Modified: 2017-10-06 14:38 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg about drv_suspend/forcewake (66.28 KB, text/plain)
2014-03-31 08:52 UTC, Guo Jinxian 		no flags Details
View All

Description Guo Jinxian 2014-03-31 08:52:13 UTC 
Created attachment 96643 [details]
dmesg about drv_suspend/forcewake

System Environment:
--------------------------
Platform: IVB
kernel:   (drm-intel-nightly)19f629e96704b796efdad3cf13b1e8fb387d8ca7

Bug detailed description:
---------------------------
After running drv_suspend/forcewake, Calltrace WARNING: CPU: 1 PID: 4409 at drivers/gpu/drm/i915/intel_uncore.c:460 gen6_gt_force_wake_put+0xed/0x13c [i915]() occurs.

This bug occurs on -nightly and -next-queued branch, bug passed on -fixes branch.

Test was blocked by bug 76580 before.

output on -nightly kernel:
./drv_suspend --run-subtest forcewake
IGT-Version: 1.6-g4fdca96 (x86_64) (Linux: 3.14.0-rc8_drm-intel-nightly_19f629_20140331_debug+ x86_64)
rtcwake: wakeup from "mem" using /dev/rtc0 at Mon Mar 31 21:34:30 2014
Subtest forcewake: SUCCESS


Reproduce steps:
---------------------------- 
1. ./drv_suspend --run-subtest forcewake
Comment 1 Paulo Zanoni 2014-04-02 14:22:54 UTC 
Hi

I believe "drm/i915: don't schedule force_wake_timer at gen6_read" (which is now on -fixes) may have fixed this bug. Can you please test?

Thanks,
Paulo
Comment 2 Guo Jinxian 2014-04-03 07:46:13 UTC 
(In reply to comment #1)
> Hi
> 
> I believe "drm/i915: don't schedule force_wake_timer at gen6_read" (which is
> now on -fixes) may have fixed this bug. Can you please test?
> 
> Thanks,
> Paulo

Yes, It's passed on latest -fixes(bc104d1f10eb6001f1b1003a5a92066a1b03f080). Thanks.
Comment 3 Paulo Zanoni 2014-04-03 16:53:47 UTC 
(In reply to comment #2)
> (In reply to comment #1)
> > Hi
> > 
> > I believe "drm/i915: don't schedule force_wake_timer at gen6_read" (which is
> > now on -fixes) may have fixed this bug. Can you please test?
> > 
> > Thanks,
> > Paulo
> 
> Yes, It's passed on latest -fixes(bc104d1f10eb6001f1b1003a5a92066a1b03f080).
> Thanks.

Closing as fixed then. Please reopen if needed.
Comment 4 Guo Jinxian 2014-04-10 07:17:05 UTC 
Checked the on latest -nightly(35dc7c8af75a3e5ae52a5469786602ce083a6368), this bug had fixed, thanks.

 ./drv_suspend --run-subtest forcewake
IGT-Version: 1.6-g9eec5b0 (x86_64) (Linux: 3.14.0_drm-intel-nightly_8490f3_20140409_debug+ x86_64)
rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Apr 10 20:15:11 2014
Subtest forcewake: SUCCESS
Comment 5 Elizabeth 2017-10-06 14:38:53 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.