| linux 64 [message #45655] |
Mon, 26 September 2005 23:51  |
R.Bauer
Messages: 1424
Registered: November 1998
|
Senior Member |
|
|
Dear all
that's more a system diagnostics question. Probably someone else has
solved the same and could give hints.
We have a bunch of AMD 64 bit linux machines and in 64 bit idl they all
work .
One of the machine shows a memory fault if the 32 bit version with idl
-32 is called. There are some hints that it could depend on something
missing in glibc because if on this machine many times netCDF files are
readed we got a Bus error message or
*** glibc detected *** malloc(): memory corruption: 0x0000000000b39180
*** too.
I thinks it's a problem on the machine and not an idl one. But where to
start?
cheers
Reimar
--
Reimar Bauer
Institut fuer Stratosphaerische Chemie (ICG-I)
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
------------------------------------------------------------ -------
a IDL library at ForschungsZentrum Juelich
http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_lib_intro. html
============================================================ =======
|
|
|
|
|
|
| Re: linux 64 [message #45766 is a reply to message #45655] |
Wed, 05 October 2005 10:35  |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
On Mon, 03 Oct 2005 21:08:10 -0700, Karl wrote:
> I still need to try to install the vendor h/w accel support if ATI has
> drivers out for this distro, but my point is that you might try getting
> the latest FC4 update if you have not already.
Just a quick follow-up. I found a RPM for the ATI driver and
installed that instead of using the fglrx driver from ATI. This RPM
worked perfectly after I installed it. glxgears runs at 7000+ fps and IDL
looks really nice. (ATI Radeon X800, IDL 6.2, Fedora Core 4).
The driver is mentioned at http://www.fedorafaq.org/#radeon.
All I had to do is add the livna.org repository to yum and then install it
with yum.
Karl
|
|
|
|
| Re: linux 64 [message #45787 is a reply to message #45699] |
Mon, 03 October 2005 21:08 |
Karl[1]
Messages: 79
Registered: October 2005
|
Member |
|
|
Regarding IDL on FC4: I just tried IDL 6.2 on FC 4. I installed FC 4
on a 32-bit machine and used yum to update everything. I noticed that
there were a lot of updates for Xorg and GL support as well as a kernel
update. I didn't try IDL before the update, so I don't know if it
would have failed before the update.
I also installed the compat-libstdc++-33 rpm so that the C++-based libs
would load.
Object Graphics seems to be OK, but slow, as expected. That is because
I have not yet made any attempt to install vendor drivers for the
Radeon 800 card. The Xorg server is using the fallback software
renderer.
This can be seen by running glxinfo:
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
(Note that IDL uses Mesa on the client side for software rendering
while Xorg uses it for both client-side GLX support and server-side
rendering.)
I still need to try to install the vendor h/w accel support if ATI has
drivers out for this distro, but my point is that you might try getting
the latest FC4 update if you have not already.
Also, I think that some of the newer Xorg releases are now starting to
include hardware drivers for some of the more common chipsets with the
intent of giving you h/w accel out of the box. It could be that
updating FC4 may address the problem you are seeing.
Karl
|
|
|
|
| Re: linux 64 [message #45788 is a reply to message #45655] |
Mon, 03 October 2005 14:54 |
Rick Towler
Messages: 821
Registered: August 1998
|
Senior Member |
|
|
Hi Reimar,
this smells like a hardware issue and I'll venture a guess that it is
RAM. The embedded memory controller in the Opteron/Athlon64 chips are
very sensitive to RAM issues and I have run into a number of weird and
difficult to diagnose problems that end up being RAM.
As with any suspected RAM problem I would start by running MemTest86 but
I have learned that you can run this for days on an Athlon64/Opteron
machine with a "bad" stick of RAM and it will not necessarily find a fault.
I would swap the RAM from a known working A64/OPT machine and test it.
I'll wager a pint it solves your problems :) And if that does solve
your problem and if that bad stick of RAM is not under warranty I would
stick it in an Intel machine. Chances are it will work fine.
-Rick
Reimar Bauer wrote:
> Dear all
>
> that's more a system diagnostics question. Probably someone else has
> solved the same and could give hints.
>
>
> We have a bunch of AMD 64 bit linux machines and in 64 bit idl they all
> work .
>
> One of the machine shows a memory fault if the 32 bit version with idl
> -32 is called. There are some hints that it could depend on something
> missing in glibc because if on this machine many times netCDF files are
> readed we got a Bus error message or
> *** glibc detected *** malloc(): memory corruption: 0x0000000000b39180
> *** too.
> I thinks it's a problem on the machine and not an idl one. But where to
> start?
>
>
>
> cheers
> Reimar
>
>
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
