9755 driver crashes on GeForce 5200 when using Java 1.6 OpenGL pipeline

[netllama]

quintesse,
Please generate and provide an nvidia-bug-report.log along with details on how to reproduce the crash.

Thanks,
Lonni

[quintesse]

Originally Posted by netllama

quintesse,
Please generate and provide an nvidia-bug-report.log along with details on how to reproduce the crash.

Bug report attached.

The way to reproduce is exactly the same as reported by "ashisdeeds":

javaws http://www.java.net/download/javadesktop/blogs/campbell/2006.10.12/PhotoCube-OGL.jnlp

[zbiggy]

Originally Posted by quintesse

javaws http://www.java.net/download/javadesktop/blogs/campbell/2006.10.12/PhotoCube-OGL.jnlp

The start is very slow and skips but after a while cube rotates. It means it rotates for 1-2seconds then freezes waits for 11seconds and then again rotates for 1-2s and freezes again.
Security dialogs have to be moved to show it's content otherwise they are empty and gray. Switches and buttons after clicking needs dialog window move too see if it were clicked.
Just dialog content is not redraw after showing/change.
All these slowdowns/skipping/freezing/not redrawing are because of composite enabled.
Disabling composite solves all these things.

How do you think, this composite slowness/redraw problem is because of weak hardware or slow composite technology?

Works ok on Geforce 6150, XOrg 1.3.0.0 :
NVRM version: NVIDIA UNIX x86 Kernel Module 100.14.06 Thu May 3 15:45:47 PDT 2007
GCC version: gcc version 3.4.6

Java 1.6.0_01-b06

I thought Nvidia may need to analyze working configuration to find what's different on non working configuration.

[byhisdeeds]

It seems that Fedora Core X is the culprit. People on other platforms seem to have it working. Can anyone tell me how I can go about tracking down the real culprit. Maybe it has something to do with a gcc version used to compile the kernel or libGL.

[netllama]

I'm not sure that this is an FC6 issue. My testing here was on FC6, and I could not reproduce this crash.

It might be best to report this bug to SUN, as they may be able to assist in isolating or debugging it further.