From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
"intel-gfx@lists.freedesktop.org >> intel-gfx"
<intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: 3.17.0-rc1: WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/i915/i915_irq.c:139 ironlake_enable_display_irq+0x7f/0x90()
Date: Tue, 26 Aug 2014 14:09:09 +0300 [thread overview]
Message-ID: <20140826110909.GJ4193@intel.com> (raw)
In-Reply-To: <20140825153615.48bd1e3f@jbarnes-desktop>
On Mon, Aug 25, 2014 at 03:36:15PM -0700, Jesse Barnes wrote:
> On Mon, 25 Aug 2014 20:29:27 +0200
> Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>
> > Hi Jesse,
> >
> > since the i915 stuff for 3.17 was merged I always get this
> > warning on my core i7 with internal Intel HD graphics.
> >
> > Intel(R) Core(TM) i7 CPU M 640 @ 2.80GHz
> >
> > As this warning is triggered by the code which was changed
> > by you and obviously the latest drm-fixes did not solve the
> > issue, it's now time to post it :-)
> >
> > My kernel is the latest pull from Linus' mainline tree.
> >
> > Any idea?
> >
> > My .config is attached.
>
> I just dug out my ILK to see if I can reproduce this... must be
> related to the irq warning changes we moved around; maybe I missed an
> init path on the ILK side.
It's the PCU irq enable. I think I have a patch somewhere for it. Just
forgot to send it out.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-08-26 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 18:29 3.17.0-rc1: WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/i915/i915_irq.c:139 ironlake_enable_display_irq+0x7f/0x90() Oliver Hartkopp
2014-08-25 22:36 ` Jesse Barnes
2014-08-26 11:09 ` Ville Syrjälä [this message]
2014-08-26 18:31 ` Oliver Hartkopp
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=20140826110909.GJ4193@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=socketcan@hartkopp.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.