[amd64/8.2-RELEASE/GTX 295] artefacts and hangers hangers while playing flash videos

[rickgl]

First some information:

OS: FreeBSD 8.2-RELEASE-p1 amd64
Current Driver: 275.09.07
X-Env: xorg-7.5.1, GLX Enabled, xfce 4.8

GFX Card: GeForce GTX 295

My card is recognized as:

nvidia0: <GeForce GTX 295> on vgapci0
vgapci0: child nvidia0 requested pci_enable_busmaster
vgapci0: child nvidia0 requested pci_enable_io
vgapci0: child nvidia0 requested pci_enable_io
nvidia0: [ITHREAD]
nvidia1: <GeForce GTX 295> on vgapci1
vgapci1: child nvidia1 requested pci_enable_busmaster
vgapci1: child nvidia1 requested pci_enable_io
vgapci1: child nvidia1 requested pci_enable_io
nvidia1: [ITHREAD]

If I play youtube flash videos in a firefox browser with linux-f10-flashplugin-10.3r181.26 trough nspluginwrapper-1.4.2 (linux emulation) the video plays as expected. As soon as I switch to another workspace I can see sometimes the the video, sometimes a black window at the place where the video is positioned. When switching back to the workspace with the actual video the video becomes a grey field while the audio is still playing. Switching back to the workspace with the video is also accompanied by a 2 second hanger.

256.53 was the last version I didn't have this problem. It happened sometime after 256.53.

Rick

[rickgl]

I'm now able to pinpoint the problem to the exact driver version when it started:

256.53 was all OK then with 260.19.12 the problem mentioned in the first post started. Another interesting fact:

Unloading the kernel module 'nvidia.ko' after such a hanger from the console after shutting down Xorg:

260.19.12 and higher: MEMORY LEAKS!!!

$ kldunload nvidia
nvidia0: detached
nvidia1: detached
Warning: memory type nvidia leaked memory on destroy (3 allocations, 192 bytes leaked).

256.53: no memory leak

$ kldunload nvidia
nvidia0: detached
nvidia1: detached

Here is another Kernel Message I only saw so far with 275.09.07

NVRM: Xid (0000:04:00): 30, Ch 00000006 M 0000001c D 00000001 intr 00100000

[rhurlin]

I can confirm this crude behaviour of the newer drivers, concerning damaged workspaces and memory leaks when unloading the kernel module.

It seems, that only non white colors are 'transmitted' in other windows. For me, most times all is ok again after closing the browser windows which contains the flash contents.

This is with a GeForce GTS450 on FreeBSD 9.0-CURRENT (amd64), nvidia-driver-270.41.19 from the ports, 'windowmaker' as window manager and linux-f10-flashplugin-10.3r181.26.

Rainer

[rickgl]

BTW: this is unchanged in the current release (280.13).

[rhurlin]

Originally Posted by rhurlin

I can confirm this crude behaviour of the newer drivers, concerning damaged workspaces and memory leaks when unloading the kernel module.

It seems, that only non white colors are 'transmitted' in other windows. For me, most times all is ok again after closing the browser windows which contains the flash contents.

This is with a GeForce GTS450 on FreeBSD 9.0-CURRENT (amd64), nvidia-driver-270.41.19 from the ports, 'windowmaker' as window manager and linux-f10-flashplugin-10.3r181.26.

Rainer

After changing from www/linux-f10-flashplugin10 to www/linux-f10-flashplugin11 there is nothing like the described artifacts and damaged workspaces anymore. Sorry for suspecting the NVidia driver for this.

Actually working with a GeForce GTS450 on FreeBSD 10.0-CURRENT (amd64), nvidia-driver-285.05.09 from the ports and linux-f10-flashplugin-11.0r1.152.

Rainer

[uOpt]

Thanks for debugging this!