All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Sean Paul <seanpaul@chromium.org>,
	dri-devel@lists.freedesktop.org, airlied@linux.ie
Subject: Re: [PATCH] drm: Add locking to resume_force_mode to prevent multiple
Date: Thu, 22 Mar 2012 22:57:15 +0000	[thread overview]
Message-ID: <e39f63$48saoj@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1332455155-16385-1-git-send-email-seanpaul@chromium.org>

On Thu, 22 Mar 2012 18:25:55 -0400, Sean Paul <seanpaul@chromium.org> wrote:
> Add a mutex to protect resume_force_mode from being called multiple
> times. This fixes a bug observed on SNB where two wake sources call
> resume_force_mode and the FDI training fails as a result. The user
> facing result of this is complete screen corruption.

Looks like a bug in i915_drv.c for calling that function without holding
the mode_config.lock
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-03-22 22:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 22:25 [PATCH] drm: Add locking to resume_force_mode to prevent multiple Sean Paul
2012-03-22 22:57 ` Chris Wilson [this message]
2012-03-23 12:51   ` Sean Paul

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='e39f63$48saoj@fmsmga002.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=seanpaul@chromium.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 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.