All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>,
	Eric Anholt <eric@anholt.net>, Dave Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sf.net,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: drm: gem_object_free without struct_mutex
Date: Sat, 2 Jan 2010 16:46:07 +0200	[thread overview]
Message-ID: <20100102144607.GA10094@bicker> (raw)
In-Reply-To: <200912302317.48530.rjw@sisk.pl>

On Wed, Dec 30, 2009 at 11:17:48PM +0100, Rafael J. Wysocki wrote:
> [CC to Jesse.]
> 
> On Wednesday 30 December 2009, Hugh Dickins wrote:
> > I've changed BUG_ON to WARN_ON in drm_gem.c (patch at bottom) to
> > get this dmesg when I resume after suspend, instead of crashing.
> > 
> > Perhaps it's a patch that should go in, perhaps not, but obviously
> > the real problem lies elsewhere.  Happens with 2.6.33-rc1 and -rc2.
> > 
> > No surprise if I'm stupidly misconfigured to get the "pin power context"
> > error in the first place (.config on demand), but I don't deserve to BUG!
> > 

The problem is dev_priv->mm.suspended which was set in i915_suspend().

In i915_resume()

   107          i915_restore_state(dev);

The i915_restore_state() fails because i915_gem_object_bind_to_gtt()
does this:

        if (dev_priv->mm.suspended)
                return -EBUSY;

   108  
   109          intel_opregion_init(dev, 1);
   110  
   111          /* KMS EnterVT equivalent */
   112          if (drm_core_check_feature(dev, DRIVER_MODESET)) {
   113                  mutex_lock(&dev->struct_mutex);
   114                  dev_priv->mm.suspended = 0;

We do set the dev_priv->mm.suspended here but it's too late.

Not sure the fix though...

regards,
dan carpenter


  reply	other threads:[~2010-01-02 14:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 19:45 drm: gem_object_free without struct_mutex Hugh Dickins
2009-12-30 22:17 ` Rafael J. Wysocki
2010-01-02 14:46   ` Dan Carpenter [this message]
2010-01-04 23:18     ` Jesse Barnes
2010-01-04 23:18     ` Jesse Barnes
2010-01-02 14:46   ` Dan Carpenter

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=20100102144607.GA10094@bicker \
    --to=error27@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sf.net \
    --cc=eric@anholt.net \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.