Bug 504902

Summary: gfx plotting glitches
Product: [Fedora] Fedora Reporter: William A. Mahaffey III <wam>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 11CC: ajax, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-12 23:33:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
incomplete plot of mesh around NACA 0012 airfoil ....
none
updated plot (w/o dialog box obscuring relevant detail :-/ ....)
none
dmesg file from this machine ....
none
xorg.conf for this box ....
none
xorg.*.log for this machine ....
none
Xorg.0.log for FC6 (remote) box ....
none
dmesg file from remote FC6 box ....
none
xorg.conf for remote FC6 box .... none

Description William A. Mahaffey III 2009-06-10 01:34:50 UTC
Created attachment 347124 [details]
incomplete plot of mesh around NACA 0012 airfoil ....

Description of problem:I get glitches plotting fields of triangles using OpenGL under gnome desktop in my in-house CAD/FEA/mesh-generator program. Everything worked AOK until I upgraded about 4 weeks ago. plots are incomplete (only about 1/2 (~8000-10000) of the tris plot, all are present in model by inspection of tabular printout).


Version-Release number of selected component (if applicable): FC9 64-bit fully patched up as of Sunday (6/7/09).


How reproducible: difficult, try to plot array of tris yourself :-/ ....


Steps to Reproduce:
1.
2.
3.
  
Actual results: incomplete mesh plotted, only about ~9000 tris out of about 21,000 plot, apparently in order of generation, gets part way through plot & stops plotting them after about 9000-10000 plotted ....


Expected results: plot 'em all ....


Additional info:

Comment 1 William A. Mahaffey III 2009-06-10 02:11:41 UTC
Created attachment 347128 [details]
updated plot (w/o dialog box obscuring relevant detail :-/ ....)

let's try that plot again :-/ ....

Comment 2 William A. Mahaffey III 2009-06-13 22:04:08 UTC
I just upgraded to FC11 64-bit via preupgrade this A.M. & this is still a problem ....

Comment 3 William A. Mahaffey III 2009-06-14 16:45:16 UTC
Eeeeeeeek !!!! A clarification: This plot happens when I execute my code on another machine (tried both an FC6 box & an FC7 box, both 64-bit & both terminally patched up) & display on this (FC11) box. The code is invoked from CLI under rxvt, SSH'ed over to the other machines, which are both servers, running in runlevel 3. When I run the code on this box (invoked from CLI under rxvt/TCSH) & display on this box, the plot comes out AOK. Looks like a problem w/ FC6 & FC7 (both), 64-bit .... This all worked up until a few weeks ago when I did my last patch-ups for those machines ....

Comment 4 Matěj Cepl 2009-09-13 22:50:26 UTC
This is a strange bug. I wonder whether it is a hardware dependent. Probably the easiest way how to find a lot of information about your hardware would be if you attach to this bug your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 5 Matěj Cepl 2009-09-13 22:52:13 UTC
And also, could you please provide steps to reproduce which I can follow (names of the packages to install, what data to use, what I need to do ... consider also I have no experience with this kind of programs)?

Thank you

Comment 6 William A. Mahaffey III 2009-09-18 13:05:20 UTC
Created attachment 361647 [details]
dmesg file from this machine ....

Comment 7 William A. Mahaffey III 2009-09-18 13:06:23 UTC
Created attachment 361648 [details]
xorg.conf for this box ....

Comment 8 William A. Mahaffey III 2009-09-18 13:07:34 UTC
Created attachment 361649 [details]
xorg.*.log for this machine ....

Comment 9 William A. Mahaffey III 2009-09-18 13:11:31 UTC
Created attachment 361652 [details]
Xorg.0.log for FC6 (remote) box ....

Comment 10 William A. Mahaffey III 2009-09-18 13:12:02 UTC
Created attachment 361653 [details]
dmesg file from remote FC6 box ....

Comment 11 William A. Mahaffey III 2009-09-18 13:12:34 UTC
Created attachment 361654 [details]
xorg.conf for remote FC6 box ....

Comment 12 William A. Mahaffey III 2009-09-18 13:14:13 UTC
I will (try to) generate a small program to duplicate this behavior by modifying 1 of the small OpenGL example programs, please be patient on this one :-) ....

Comment 13 William A. Mahaffey III 2009-09-20 15:13:46 UTC
Well .... after some messing around w/ writing the small test app, it appears that the problem is in the OpenGL V1.1 libraries in FC6 & FC7, specifically something in either the glVertexPointer routine or the glDrawElements routine (probably the latter, IMHO). When I plot tri's using the old-fashioned ((3-glVertex3d's-per-tri)-in-a-loop-over-all-tris) method, everything plots AOK. When I use the newer routines mentioned above, I get bad plots (in my sample code & in my other CAD code). Sooooooo .... I guess this is .... NOTABUG after all (unless the possibility of bad code from FC6 also being in RHEL5 is a problem).

Comment 14 Matěj Cepl 2009-10-12 23:33:14 UTC
Thanks for exhaustive analysis. Closing as NOTABUG then.