All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Kai Ruhnau <kai@tragetaschen.dyndns.org>
Cc: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Nouveau] nouveau/ttm: BUG in ttm_bo_release_list
Date: Sat, 9 Oct 2010 15:58:41 +0200	[thread overview]
Message-ID: <20101009135841.GA3628@joi.lan> (raw)
In-Reply-To: <4CB073F6.4050407@tragetaschen.dyndns.org>

On Sat, Oct 09, 2010 at 03:53:58PM +0200, Kai Ruhnau wrote:
>  On 09/18/2010 01:18 PM, Marcin Slusarz wrote:
> > On Sat, Sep 18, 2010 at 09:39:21AM +1000, Ben Skeggs wrote:
> >> On Fri, 2010-09-17 at 19:43 +0200, Marcin Slusarz wrote:
> >>> Hi
> >>> Since upgrade from 2.6.35 to 2.6.36-rc3 (nouveau tree) I'm hitting this bug a couple of times a day:
> [oops]
> >>> this is BUG_ON(atomic_read(&bo->cpu_writers));
> >>>
> >>> I'm on b642f07208988270ac402d2548d42dab1d5fec92 "drm/nv50: fix 100c90 write on nva3".
> >>> If you have any patches / ideas how to debug this, let me know.
> >> I've actually seen this a couple of times.  It appears I was incorrectly
> >> blaming some patches I have in progress for it, the problem appeared to
> >> go away when I reverted them.  Perhaps it's more random.  I have no
> >> current ideas however.
> >>
> > Heh, Francisco provided the patch on IRC, which seem to fix this bug.
> >
> > http://annarchy.freedesktop.org/~currojerez/nouveau_cpu_prep_validate.patch
> >
> > I'm still testing it.
> >
> >
> 
> Hi
> 
> How is this fix working out?

The fix is in Linus' tree, commit 0fbecd400dd0a82d465b3086f209681e8c54cb0f:
"drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer"

Marcin

      reply	other threads:[~2010-10-09 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17 17:43 nouveau/ttm: BUG in ttm_bo_release_list Marcin Slusarz
2010-09-17 23:39 ` Ben Skeggs
2010-09-18 11:18   ` Marcin Slusarz
2010-10-09 13:53     ` [Nouveau] " Kai Ruhnau
2010-10-09 13:58       ` Marcin Slusarz [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=20101009135841.GA3628@joi.lan \
    --to=marcin.slusarz@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kai@tragetaschen.dyndns.org \
    --cc=nouveau@lists.freedesktop.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.