linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikola Pajkovsky <npajkovs@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: WARNING: at drivers/gpu/drm/i915/i915_gem.c:3437 i915_gem_object_pin+0x151/0x1a0()
Date: Tue, 11 Dec 2012 16:31:09 +0100	[thread overview]
Message-ID: <87r4mwvc5e.fsf@redhat.com> (raw)
In-Reply-To: <CAKMK7uHQFsrXX3FKoVA_AiA1iwo_-NRf_CqaqWXy9rNUg+tonQ@mail.gmail.com> (Daniel Vetter's message of "Tue, 11 Dec 2012 16:08:26 +0100")

Daniel Vetter <daniel.vetter@ffwll.ch> writes:

> On Tue, Dec 11, 2012 at 1:31 PM, Nikola Pajkovsky <npajkovs@redhat.com> wrote:
>> looks like we still have some oops in i915. i915 maintainers do you have
>> any ideas what's going on? I will try to trigger that oops later today
>> and provide more information.
>
> The infamous pin leak. Should be fixed with
>
> commit b4a98e57fc27854b5938fc8b08b68e5e68b91e1f
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Thu Nov 1 09:26:26 2012 +0000
>
>     drm/i915: Flush outstanding unpin tasks before pageflipping
>
> available from the drm-next (or linux-next) trees. If it holds up once
> merged, we'll backport it.

Thanks for the info, I will merge it into my local tree and give it try.

-- 
Nikola

      reply	other threads:[~2012-12-11 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 12:31 WARNING: at drivers/gpu/drm/i915/i915_gem.c:3437 i915_gem_object_pin+0x151/0x1a0() Nikola Pajkovsky
2012-12-11 15:08 ` Daniel Vetter
2012-12-11 15:31   ` Nikola Pajkovsky [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=87r4mwvc5e.fsf@redhat.com \
    --to=npajkovs@redhat.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).