From: Egbert Eich <eich@suse.com>
To: Jan Niggemann <jn@hz6.de>
Cc: Egbert Eich <eich@suse.com>, intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: i915 irq storm mitigation in 3.10
Date: Tue, 23 Jul 2013 13:26:30 +0200 [thread overview]
Message-ID: <20974.26726.659962.223064@linux-qknr.site> (raw)
In-Reply-To: jn@hz6.de wrote on Monday, 22 July 2013 at 21:28:33 +0200
Hi Jan -
Jan Niggemann writes:
>
> As to the log: I messed up the kernel parameters this morning... was
> out of coffee this morning and my 1,5y daughter played around me :-)
>
> Here's my kernel log with drm.debug and printk.time enabled:
> Uncompressed (22M): http://files.hz6.de/kern_20130722.log
> bzip2'd (some 600 KB): http://files.hz6.de/kern_20130722.log.bz2
I've looked at the logs a bit more. Here's a patch adding some more
debug information. Would you please apply this to your 3.10 kernel
and generate a log file the same way as you did before.
The driver will be even more chatty - but I don't expect any problems
from this.
Cheers,
Egbert.
diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index e43d809..46bb77c 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -919,6 +919,11 @@ static inline void intel_hpd_irq_handler(struct drm_device *dev,
spin_lock(&dev_priv->irq_lock);
for (i = 1; i < HPD_NUM_PINS; i++) {
+ if (IS_G4X(dev) && (hpd[i] & hotplug_trigger) &&
+ dev_priv->hpd_stats[i].hpd_mark != HPD_ENABLED)
+ DRM_DEBUG_KMS("Received HPD intterupt although disabled\n",
+ I915_READ(PORT_HOTPLUG_EN));
+
if (!(hpd[i] & hotplug_trigger) ||
dev_priv->hpd_stats[i].hpd_mark != HPD_ENABLED)
continue;
@@ -929,6 +934,8 @@ static inline void intel_hpd_irq_handler(struct drm_device *dev,
+ msecs_to_jiffies(HPD_STORM_DETECT_PERIOD))) {
dev_priv->hpd_stats[i].hpd_last_jiffies = jiffies;
dev_priv->hpd_stats[i].hpd_cnt = 0;
+ DRM_DEBUG_KMS("Received HPD interrupt on PIN %d - jiffies: %d\n", i,
+ dev_priv->hpd_stats[i].hpd_last_jiffies);
} else if (dev_priv->hpd_stats[i].hpd_cnt > HPD_STORM_THRESHOLD) {
dev_priv->hpd_stats[i].hpd_mark = HPD_MARK_DISABLED;
dev_priv->hpd_event_bits &= ~(1 << i);
@@ -936,6 +943,8 @@ static inline void intel_hpd_irq_handler(struct drm_device *dev,
storm_detected = true;
} else {
dev_priv->hpd_stats[i].hpd_cnt++;
+ DRM_DEBUG_KMS("Received HPD interrupt on PIN %d - cnt: %d\n", i,
+ dev_priv->hpd_stats[i].hpd_cnt);
}
}
next prev parent reply other threads:[~2013-07-23 11:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 21:41 i915 irq storm mitigation in 3.10 Jan Niggemann
2013-07-08 20:03 ` Daniel Vetter
2013-07-21 20:23 ` Jan Niggemann
2013-07-21 20:43 ` Daniel Vetter
2013-07-22 6:14 ` Jan Niggemann
2013-07-22 6:26 ` Daniel Vetter
2013-07-22 8:04 ` Egbert Eich
2013-07-22 19:28 ` Jan Niggemann
2013-07-22 20:36 ` Egbert Eich
2013-07-23 8:17 ` Daniel Vetter
2013-07-23 11:26 ` Egbert Eich [this message]
2013-07-24 20:52 ` Jan Niggemann
2013-07-25 7:50 ` Egbert Eich
2013-07-25 9:58 ` Daniel Vetter
2013-07-25 11:18 ` Egbert Eich
2013-07-25 21:23 ` Jan Niggemann
2013-07-26 5:11 ` Egbert Eich
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=20974.26726.659962.223064@linux-qknr.site \
--to=eich@suse.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jn@hz6.de \
/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