[Nouveau] CCACHE and VFETCH FAULTs causing lockups

[Lucas Stach]

Just adding a me too.

I updated from 3fdb729eb7de5597961eb3fbaf0bdfe6f4262307 and now I get
lockups from time to time (max. 60 mins) with normal 2D desktop usage.
No 3D involved here.

Logs only contain:
Mar  6 17:27:51 workstation kernel: [  341.970412] [drm] nouveau
0000:01:00.0: PGRAPH - TRAP_CCACHE FAULT
Mar  6 17:27:51 workstation kernel: [  341.970435] [drm] nouveau
0000:01:00.0: PGRAPH - TRAP_CCACHE 000e0080 00000000 00000000 00000000
00000000 00000004 00000000
Mar  6 17:27:51 workstation kernel: [  341.970444] [drm] nouveau
0000:01:00.0: PGRAPH - TRAP
Mar  6 17:27:51 workstation kernel: [  341.970456] [drm] nouveau
0000:01:00.0: PGRAPH - ch 2 (0x0000a38000) subc 5 class 0x8397 mthd
0x0f04 data 0x00000000

Tested chipset is my nvA8.

-- Lucas


Am Mittwoch, den 02.03.2011, 22:43 +0000 schrieb Maarten Maathuis:
> On Tue, Mar 1, 2011 at 9:51 PM, Ben Skeggs <bskeggs at redhat.com> wrote:
> > On Tue, 2011-03-01 at 21:08 +0000, Maarten Maathuis wrote:
> >
> >> Those come after 15-30 minutes of running warzone2100, i haven't
> >> played any games for a while, so no idea how long this has been going
> >> on.
> >> I also got a TRAP_CCACHE on channel 2 a little while ago, it takes
> >> much longer to trigger (a few hours). I'm using todays "nouveau
> >> kernel" git.
> > You're not the first person to have reported this fwiw, personally, I
> > haven't seen it yet..
> >
> >>
> >> I'm guessing something is being unmapped too early or without reason,
> >> or some cache is stale. But it isn't obvious what exactly it is.
> >>
> >> Because i don't remember having these lockups before I'm inclined to
> >> guess that this commit is involved
> >> http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=6330d8f5ecc4a19fd2ad3c7fa128b2f4c2ce3360
> >>
> >> Any ideas?
> > Not really.  If this commit *is* the cause, the problem is still
> > somewhere else.  That commit just makes sure PTEs are marked invalid, so
> > if it's causing your faults, then previously the GPU would still have
> > been reading/writing invalid data.
> 
> I reverted the commit today and things seem to be going be better,
> I'll give it a few more days before coming to a conclusion. I
> understand that the real issue is somewhere else.
> 
> >
> > Plus, I expect you should probably have seen a VM fault..
> >
> > Ben.
> >>
> >> Maarten.
> >>
> >
> >
> >
> 
> 
>