nv problems on FreeBSD 6.1-RELEASE for AMD64
Chris Radlinski
radlinskic at acm.org
Wed Jan 17 20:43:39 PST 2007
Thanks for the reply.
I am able to get a stack trace. The call to NVSync() that locks the
system comes from somewhere in libxaa.so. The particular function
varies but it's always from XAA. I'm willing to do whatever I can to
help fix this bug. I can reliably reproduce it; I just don't know how
to fix it.
I do have a workaround. If I set "Options ShadowFB" in xorg.conf, I can
run the nv driver at reasonable speeds and without problems. I don't
know what I'm giving up by doing that but it seems to work OK.
Please let me know what I can do to help fix this.
Chris
On Wed, 2007-01-17 at 11:25, Matthias Hopf wrote:
> On Jan 11, 07 16:42:21 -0600, Chris Radlinski wrote:
> > I'm not sure what that means. Do I have a bad card?
>
> Possibly. Often cards hang here if they are broken.
>
> > I'm going to add another condition to the while loop so it doesn't loop
> > indefinitely and see what happens.
>
> Won't help. The gfx engine is stalled, and won't wake up again.
>
> The only thing to debug would be to trace the commands, and find out
> which one was the last the gfx engine was able to process. Don't know
> how to do that correctly, though.
>
> Matthias
>
> --
> Matthias Hopf <mhopf at suse.de> __ __ __
> Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat at mshopf.de
> Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20070117/d2e99acb/attachment.html>
More information about the xorg
mailing list