public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/i915: shut up gen8+ SDE irq dmesg noise
Date: Fri, 23 Oct 2015 11:23:12 +0200	[thread overview]
Message-ID: <20151023092312.GN16848@phenom.ffwll.local> (raw)
In-Reply-To: <87pp06uehq.fsf@intel.com>

On Fri, Oct 23, 2015 at 12:21:37PM +0300, Jani Nikula wrote:
> On Fri, 23 Oct 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > On Fri, Oct 23, 2015 at 10:56:12AM +0200, Daniel Vetter wrote:
> >> We get tons of cases where the master interrupt handler apparently set
> >> a bit, with the SDEIIR agreeing. No idea what's going on there, but
> >> it's consistent on gen8+, no one seems to care about it and it's
> >> making CI results flaky.
> >
> > Just delete the message and delete them all. There isn't anything we can
> > do and if anybody actually cared (which apparently they didn't in the
> > first place), they could just trace the mmio.
> 
> Except this one is a regression, introduced by a bisected commit, and
> suspiciously the errors pop up during aux transfers.

dp aux is a red herring very likely, since it's just the source of a _lot_
of sde interrupts.

> https://bugs.freedesktop.org/show_bug.cgi?id=92084

No one demonstrated any bad side-effects of this, let's shut it up (but
keep the breadcrumb in debug logs in case) and move on to other bugs. We
have enough.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-10-23  9:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23  8:56 [PATCH 1/2] drm/i915: Shut up GuC errors when it's disabled Daniel Vetter
2015-10-23  8:56 ` [PATCH 2/2] drm/i915: shut up gen8+ SDE irq dmesg noise Daniel Vetter
2015-10-23  9:03   ` Chris Wilson
2015-10-23  9:14     ` Daniel Vetter
2015-10-23 14:21       ` Dave Gordon
2015-10-23  9:21     ` Jani Nikula
2015-10-23  9:23       ` Daniel Vetter [this message]
2015-10-23 13:33         ` Ville Syrjälä
2015-10-23 13:40           ` Chris Wilson
2015-10-23 13:47             ` Ville Syrjälä
2015-10-23 14:42           ` Daniel Vetter
2015-10-23 15:22             ` Ville Syrjälä
2015-10-27  2:31               ` Daniel Vetter
2015-10-27  8:10                 ` Jani Nikula
2015-10-28  0:22                   ` Daniel Vetter
2015-10-23  9:00 ` [PATCH] drm/i915: Don't complain about lack of ACPI video bios Daniel Vetter
2015-10-23 11:46   ` Jani Nikula
2015-10-23  9:10 ` [PATCH] drm/i915: Shut up GuC errors when it's disabled Daniel Vetter
2015-10-23 10:56   ` Mika Kuoppala
2015-10-23 11:32     ` Daniel Vetter
2015-10-23  9:21 ` [PATCH 1/2] " kbuild test robot

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=20151023092312.GN16848@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.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