From: Dave Gordon <david.s.gordon@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 2/2] drm/i915: shut up gen8+ SDE irq dmesg noise
Date: Fri, 23 Oct 2015 15:21:42 +0100 [thread overview]
Message-ID: <562A4276.2080509@intel.com> (raw)
In-Reply-To: <20151023091441.GM16848@phenom.ffwll.local>
On 23/10/15 10:14, Daniel Vetter wrote:
> On Fri, Oct 23, 2015 at 10:03:50AM +0100, Chris Wilson 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.
>
> The non-SDE ones don't fire and I think are useful. And in case we have
> another report from users that gmbus is not reliably working with their
> touchpad (this is how we discovered the original pch irq issues) I think
> finding some breadcrumbs in dmesg would be useful. The SDE one happens
> rarely enough that I don't think it should be a performance issue, ever.
>
> Hence why I decided to keep them.
> -Daniel
I used to get the "master interrupt lied" message quite frequently.
Since it was not clear whether it really meant that the master had an
extra bit set or that one (any) of the detail registers was missing an
interrupt bit, I tried servicing the interrupt anyway. But it didn't
help with any of the issues I was seeing at the time, and the message no
longer occurs (on SKL) with more recent kernels.
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-23 14:21 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 [this message]
2015-10-23 9:21 ` Jani Nikula
2015-10-23 9:23 ` Daniel Vetter
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=562A4276.2080509@intel.com \
--to=david.s.gordon@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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