Home »
Public Forums »
archive »
linux 64
| 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
>
>
|
|
|
|
Current Time: Wed Oct 15 02:03:34 PDT 2025
Total time taken to generate the page: 0.11621 seconds
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
