Re: things started getting ugly

    I have to retract a statement.  I successfully run dmx yesterday, 
but only ran an xterm and firefox on it.  Today I tried vmd and other 
OpenGL apps and dmx crashed with the malloc error. 
    My errors started appearing soon after I increased the resolution of 
each display from 1024x768 to 1600x1200, but not right off the bat.  I 
was running fine at the higher res for 3 or 4 days before the errors 
appeared.  I will try lowering the res and see what happens.
    I also went to NVIDIA 87.56 but couldn't get it to do 1600x1200, so 
I am back on 81.78.  Maybe I need to get on 87.56.



Samuel T. Liston <[email protected]>
-----------------------------------------
Systems Administrator - Visualization
-----------------------------------------
Univ. of Utah
 Center for High Performance Computing
  155 S. 1452 E. Room 405
  Salt Lake City, Utah 84112
  801.232.6932





Dale Southard wrote:

>We also went to NVIDIA 87.56 at the same time since that driver
>addresses the 4K limit in GL.  I mention this only because the crashes
>seemed to happen when we were doing large GL windows -- with multiple
>smaller GL windows, things seemed stable.
>
>Of course we also updated Quadrics drivers and other things, so it's
>good to hear someone else seeing the same malloc errors since it narrows
>down the possible causes a little.  :-)
>
>Sam Liston wrote:
>  
>
>>Yes, I can successfully run dmx ( xorg-x11-Xdmx-6.8.2-1.EL.13.25 ) and
>>cr by themselves, but together the crap out.  The interesting thing is
>>I've been running on RHEL4U3 for several week with no problem , then all
>>of a sudden...error
>>
>>    
>>
>>>As I mentioned on the DMX list, we started seeing this behavior after
>>>updating to RHEL4U3 without Cr in the picture.  It appears to be a
>>>DMX-RHEL4U3 problem, not a Cr problem.
>>>
>>>
>>>Sam Liston wrote:
>>> 
>>>
>>>      
>>>
>>>>I've been using for months chromium with dmx to run a 3x3 wall ( Dual
>>>>Opteron, Nvidia Quadrofx3000, GigE, RHEL4U3).  The main app we run on
>>>>top is VMD.  Out of the blue I started getting the following error:
>>>>
>>>>[stliston@skylinearch bin]# *** glibc detected *** malloc(): memory
>>>>corruption: 0x0000000000dedf20 ***
>>>>Window manager warning: Lost connection to the display ':1';
>>>>most likely the X server was shut down or you killed/destroyed
>>>>the window manager.
>>>>
>>>>I have no idea what I did to cause this.  I ran memtest86+ to make sure
>>>>the system memory was sane.  It was fine.
>>>>In an attempt to fix it I rebuild dmx and then rebuild chromium against
>>>>those new headers and libraries, but to no avail.
>>>>
>>>>Here's the series of events:
>>>>  dmx starts successfully,
>>>>  the mothership gets going,
>>>>  crservers are started on all the backend nodes,
>>>>  vmd starts up, but before the handshake between the mothership and
>>>>the backend crservers can take place dmx crashes and I get "the error".
>>>>I realize this post maybe more appropriate for the dmx mailing list.
>>>>But since Chromium is involve I thought I wouldn't hurt to get your
>>>>insight.  I will post it with dmx too.
>>>>        
>>>>
>
>
>
>  
>


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642