[Nouveau] [Bug 16168] Quadro NVS 400 (NV17a) drm PGRAPH_ERROR

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=16168





--- Comment #7 from Pete Beardmore <elbeardmorez at msn.com>  2009-04-11 12:19:18 PST ---
hi.

i updated everything from git a couple of weeks ago.

i am still having the same problems with any kind of acceleration. kde (4 now)
sessions will just stop responding after up to a minute of usage. the gdb
outputs attached are hopefully helpful in showing the where the process is
hanging:

nouveau_fence_flush
nouveau_fence_wait

etc.

i tested X / KDE with less components each time. there are misleading??
messages generated in the xorg log about disabled components..

(WW) "glx" will not be loaded unless you've specified it to be loaded
elsewhere.
(WW) "dri" will not be loaded unless you've specified it to be loaded
elsewhere.
(II) "extmod" will be loaded. This was enabled by default and also specified in
the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in
the config file.
(II) "glx" will be loaded even though the default is to disable it.
(II) "dri" will be loaded even though the default is to disable it.
(II) "dri2" will be loaded by default.

..i explicitly checked that the various X modules weren't present in the
environment each time using xdpyinfo.

regardless, i think the stacks only look different because the hang occured
whilst doing different operations each time..

i've once again had to revert back to using ` Option "NoAccel" "true" ` to get
any type of stability.. ..on two monitors (see other issue
https://bugs.freedesktop.org/show_bug.cgi?id=16165)

is there anything I can do?

i tried using the 'isolateDevice' switch for the xserver thinking that maybe
the second gpu isn't helping, but since there's no mention of the other gpu
device in the log it was probably pointless - no change anyway.

cheers.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.