public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Egbert Eich <eich@suse.de>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	stable@vger.kernel.org, bitlord <bitlord0xff@gmail.com>
Subject: Re: [PATCH] drm/i915: Don't WARN nor handle unexpected hpd interrupts on gmch platforms
Date: Thu, 24 Apr 2014 13:43:51 +0300	[thread overview]
Message-ID: <87ppk7vwgo.fsf@intel.com> (raw)
In-Reply-To: <1398333797-28199-1-git-send-email-daniel.vetter@ffwll.ch>

On Thu, 24 Apr 2014, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> The status bits are unconditionally set, the control bits only enable
> the actual interrupt generation. Which means if we get some random
> other interrupts we'll bogusly complain about them.
>
> So restrict the WARN to platforms with a sane hotplug interrupt
> handling scheme. And even more important also don't attempt to process
> the hpd bit since we've detected a storm already. Instead just clear
> the bit silently.
>
> This WARN has been introduced in
>
> commit b8f102e8bf71cacf33326360fdf9dcfd1a63925b
> Author: Egbert Eich <eich@suse.de>
> Date:   Fri Jul 26 14:14:24 2013 +0200
>
>     drm/i915: Add messages useful for HPD storm detection debugging (v2)
>
> before that we silently handled the hpd event and so partially
> defeated the storm detection.
>
> v2: Pimp commit message (Jani)
>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Egbert Eich <eich@suse.de>
> Cc: bitlord <bitlord0xff@gmail.com>
> Reported-by: bitlord <bitlord0xff@gmail.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Pushed to -fixes, thanks for the patch.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center

      reply	other threads:[~2014-04-24 10:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-12 17:31 [PATCH] drm/i915: Don't WARN about unexpected hpd interrupts on gmch platforms Daniel Vetter
2014-04-12 18:12 ` Egbert Eich
2014-04-12 18:38   ` [Intel-gfx] " Daniel Vetter
2014-04-24  8:11     ` Jani Nikula
2014-04-24 10:03       ` [PATCH] drm/i915: Don't WARN nor handle " Daniel Vetter
2014-04-24 10:43         ` Jani Nikula [this message]

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=87ppk7vwgo.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=bitlord0xff@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=eich@suse.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    /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