public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Donny Cooper" <dcooper@hstc.necsyl.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] malloc problems
Date: Thu, 26 Apr 2001 14:36:11 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005473@msgid-missing> (raw)

Hello,

3 SDV systems, we'll call them Tom, Dick, & Harry:
(2)BigSur
	Tom   (1 x B3, 1GB Mem)
	Dick  (2 x B3, 1GB Mem)
(1)Lion
	Harry (4 x B3, 4GB Mem)

Problem:
When running the exact same executable, Dick and Harry, consistently give
the same results and Tom consistently gives different results.


Systems have been verified to be the same in many aspects:
OS environment
Kernel
BIOS/Firmware
CMOS settings
Mem type and board locations
SCSI and settings

Below is a small sample of code and the results I get on each system:

dynamic_area = (unsigned char *) malloc ( membytes );
printf(" dyn_area = %x %lx, mem= %x \n",dynamic_area,dynamic_area,membytes);

Result from Tom: (1-way BigSur)
dyn_area = 40000010 40000010, mem= 2000018

Result from Dick & Harry:(2-way BigSur & 4-way Lion)
dyn_area = 10 2000000000000010, mem= 2000018

Is it a single-CPU thing?
Any ideas are appreciated.

Thanks.
***************************************************************************
Donny Cooper                     | Direct Phone : (281) 465-1506
NEC Systems, Inc.                | Houston Metro: (281) 296-0912 x 1506
High Performance Computing Center| Fax          : (281) 465-1599
4200 Research Forest Dr, #400    | E-mail       : dcooper@atcc.necsyl.com
The Woodlands, TX 77381          | URL          : http://www.necservers.com
***************************************************************************



             reply	other threads:[~2001-04-26 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 14:36 Donny Cooper [this message]
2001-04-26 17:00 ` [Linux-ia64] malloc problems Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590693005473@msgid-missing \
    --to=dcooper@hstc.necsyl.com \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox