From: Peter Antoine <peter.antoine@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: david.weinehall@intel.com, yex.tian@intel.com,
deepak.s@intel.com, thomas.daniel@intel.com,
daniel.vetter@ffwll.ch, Peter Antoine <peter.antoine@intel.com>,
stable@vger.kernel.org
Subject: [PATCH v5] drm/i915: Avoid GPU Hang when comming out of s3 or s4
Date: Mon, 11 May 2015 13:35:01 +0100 [thread overview]
Message-ID: <1431347701-8997-1-git-send-email-peter.antoine@intel.com> (raw)
In-Reply-To: <20150511103303.GZ15256@phenom.ffwll.local>
This patch fixed a timing issue that causes a GPU hang when a the system
comes out of power saving.
During pm_resume, We are submitting batchbuffers before enabling
Interrupts this is causing us to miss the context switch interrupt,
and in consequence intel_execlists_handle_ctx_events is not triggered.
This patch is based on a patch from Deepak S <deepak.s@intel.com>
from another platform.
The patch fixes an issue introduced by:
commit e7778be1eab918274f79603d7c17b3ec8be77386
drm/i915: Fix startup failure in LRC mode after recent init changes
The above patch added a call to init_context() to fix an issue introduced
by a previous patch. But, it then opened up a small timing window for the
batches being added by the init_context (basically setting up the context)
to complete before the interrupts have been turned on, thus hanging the
GPU.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89600
Cc: stable@vger.kernel.org
Signed-off-by: Peter Antoine <peter.antoine@intel.com>
---
drivers/gpu/drm/i915/i915_drv.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index 6bb6c47..748ab13 100644
--- a/drivers/gpu/drm/i915/i915_drv.c
+++ b/drivers/gpu/drm/i915/i915_drv.c
@@ -734,6 +734,13 @@ static int i915_drm_resume(struct drm_device *dev)
intel_init_pch_refclk(dev);
drm_mode_config_reset(dev);
+ /*
+ * Interrupts have to be enabled before any batches are run. If not the
+ * GPU will hang. The init_hw will initiate batches to update/restore
+ * the context.
+ */
+ intel_runtime_pm_enable_interrupts(dev_priv);
+
mutex_lock(&dev->struct_mutex);
if (i915_gem_init_hw(dev)) {
DRM_ERROR("failed to re-initialize GPU, declaring wedged!\n");
@@ -741,9 +748,7 @@ static int i915_drm_resume(struct drm_device *dev)
}
mutex_unlock(&dev->struct_mutex);
- /* We need working interrupts for modeset enabling ... */
- intel_runtime_pm_enable_interrupts(dev_priv);
-
+ /* This must follow the pm enable interrupts */
intel_modeset_init_hw(dev);
spin_lock_irq(&dev_priv->irq_lock);
--
1.9.1
next prev parent reply other threads:[~2015-05-11 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 7:50 [PATCH v3] drm/i915: Avoid GPU Hang when comming out of s3 or s4 Peter Antoine
2015-05-11 10:08 ` Dave Gordon
2015-05-11 10:33 ` Daniel Vetter
2015-05-11 11:05 ` [PATCH v4] " Peter Antoine
2015-05-11 12:22 ` Greg KH
2015-05-15 2:33 ` shuang.he
2015-05-11 12:35 ` Peter Antoine [this message]
2015-05-12 8:34 ` [PATCH v5] " Jani Nikula
2015-05-15 2:32 ` shuang.he
2015-05-11 11:55 ` [PATCH v3] " Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1431347701-8997-1-git-send-email-peter.antoine@intel.com \
--to=peter.antoine@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=david.weinehall@intel.com \
--cc=deepak.s@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=thomas.daniel@intel.com \
--cc=yex.tian@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox