Nouveau - Dec 2010 - nv50 channel takedown

I am seeing problems on 2.6.36-rc7 based kernels.

The error always happens during a channel destruction (always gallium
on channel 3 in my tests), and always looks like this :
<3>[  612.115977] [drm] nouveau 0000:01:00.0: AIII, invalid/inactive
channel id 128
<6>[  612.115987] [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - Ch
-1/3 Class 0x5039 Mthd 0x0184 Data 0x00000000:0x00000e02
<6>[  612.115990] [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR -
INVALID_OBJECT

This is associated with screen corruptions, mostly all fonts/icons disappearing.

The oldest commit where I could see the error during a full piglit run :

commit ea645107d204ebb9c6da494b8fc82e03d74e4513
Author: Ben Skeggs <bskeggs at redhat.com>
Date:   Tue Oct 12 08:01:59 2010 +1000

    drm/nouveau: fix thinko in channel locking in semaphore path

But I might have seen troubles with older commits (still 2.6.36-rc7 based).
And I still don't know if the issue is always triggered by the same
piglit tests or not.

But with a later commit, the issue became much more frequent,
triggered by many piglit tests, so I could easily isolate one
(fdo10370) which reproduces the issue almost every time :

commit 36a7ebda99e904a66188c7304d033e81780455e2
Author: Francisco Jerez <currojerez at riseup.net>
Date:   Mon Oct 18 03:53:39 2010 +0200

    drm/nouveau: Refactor context destruction to avoid a lock ordering issue.

Reversing pfifo and pgraph destruction order as before, and the issue
becomes less frequent again.

I would love to know if anyone at all ever managed to reproduce this.

For some reason this
(http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=114432fd006141fa74fb67b2256b2d1dac617d9f)
comes to mind, not that it matches the error exactly, but still,
consider trying a kernel that includes this commit.

Maarten.

On Sun, Dec 12, 2010 at 11:56 AM, Xavier Chantry
<chantry.xavier at gmail.com> wrote:
> I am seeing problems on 2.6.36-rc7 based kernels.
>
> The error always happens during a channel destruction (always gallium
> on channel 3 in my tests), and always looks like this :
> <3>[ ?612.115977] [drm] nouveau 0000:01:00.0: AIII, invalid/inactive
> channel id 128
> <6>[ ?612.115987] [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - Ch
> -1/3 Class 0x5039 Mthd 0x0184 Data 0x00000000:0x00000e02
> <6>[ ?612.115990] [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR -
INVALID_OBJECT
>
> This is associated with screen corruptions, mostly all fonts/icons
disappearing.
>
> The oldest commit where I could see the error during a full piglit run :
>
> commit ea645107d204ebb9c6da494b8fc82e03d74e4513
> Author: Ben Skeggs <bskeggs at redhat.com>
> Date: ? Tue Oct 12 08:01:59 2010 +1000
>
> ? ?drm/nouveau: fix thinko in channel locking in semaphore path
>
> But I might have seen troubles with older commits (still 2.6.36-rc7 based).
> And I still don't know if the issue is always triggered by the same
> piglit tests or not.
>
> But with a later commit, the issue became much more frequent,
> triggered by many piglit tests, so I could easily isolate one
> (fdo10370) which reproduces the issue almost every time :
>
> commit 36a7ebda99e904a66188c7304d033e81780455e2
> Author: Francisco Jerez <currojerez at riseup.net>
> Date: ? Mon Oct 18 03:53:39 2010 +0200
>
> ? ?drm/nouveau: Refactor context destruction to avoid a lock ordering
issue.
>
> Reversing pfifo and pgraph destruction order as before, and the issue
> becomes less frequent again.
>
> I would love to know if anyone at all ever managed to reproduce this.
> _______________________________________________
> Nouveau mailing list
> Nouveau at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
>


-- 
Far away from the primal instinct, the song seems to fade away, the
river get wider between your thoughts and the things we do and say.

On Sun, Dec 12, 2010 at 2:28 PM, Maarten Maathuis <madman2003 at
gmail.com> wrote:
> For some reason this
>
(http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=114432fd006141fa74fb67b2256b2d1dac617d9f)
> comes to mind, not that it matches the error exactly, but still,
> consider trying a kernel that includes this commit.
>
There were many changes after the commits I mentioned, but latest git
has the same problem. Very easy to trigger the issue.

If no one else has the problem, I am wondering if it could be some
hardware issue. It is a laptop with a standard nv84, which never had
any exotic behavior before.