public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Intel Haswell kernel warning (3.11.2)
Date: Sun, 29 Sep 2013 13:13:43 -0400	[thread overview]
Message-ID: <20130929171343.GA20148@animx.eu.org> (raw)
In-Reply-To: <20130929150502.GG744@nuc-i3427.alporthouse.com>

 Please keep me in CC.

CCing Borislav Petkov <bp@alien8.de>, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org as they were on another part of this thread.

Chris Wilson wrote:
> > > I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869.  This
> > > happens when I'm on a console, the screen has gone into power save and I
> > > press a key to wake it up.
> > > 
> > > Kernel is Vanilla 3.11.2.
> 
> Try,
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index bd3e115..dacde4e 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -4043,8 +4043,6 @@ static void intel_connector_check_state(struct intel_connector *connector)
>   * consider. */
>  void intel_connector_dpms(struct drm_connector *connector, int mode)
>  {
> -       struct intel_encoder *encoder = intel_attached_encoder(connector);
> -
>         /* All the simple cases only support two dpms states. */
>         if (mode != DRM_MODE_DPMS_ON)
>                 mode = DRM_MODE_DPMS_OFF;
> @@ -4055,10 +4053,8 @@ void intel_connector_dpms(struct drm_connector *connector, int mode)
>         connector->dpms = mode;
>  
>         /* Only need to change hw state when actually enabled */
> -       if (encoder->base.crtc)
> -               intel_encoder_dpms(encoder, mode);
> -       else
> -               WARN_ON(encoder->connectors_active != false);
> +       if (connector->encoder)
> +               intel_encoder_dpms(to_intel_encoder(connector->encoder), mode);
>  
>         intel_modeset_check_state(connector->dev);
>  }

Manually appied to 3.11.2.  It doesn't give me a warning now and I can go
back to the VT where X is running (I forgot to mention that detail in the
original message I think).

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.

      reply	other threads:[~2013-09-29 17:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 18:50 Intel Haswell kernel warning (3.11.2) Wakko Warner
2013-09-29 14:17 ` Wakko Warner
2013-09-29 14:58   ` Borislav Petkov
2013-09-29 15:12     ` Daniel Vetter
2013-10-24  6:09       ` Reto Glauser
2013-09-29 15:05   ` Chris Wilson
2013-09-29 17:13     ` Wakko Warner [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=20130929171343.GA20148@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=bp@alien8.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@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