All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@pacbell.net>
To: Matthew Dharm <mdharm@momenco.com>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: RE: More data: I've made a CVS build that doesn't crash!
Date: 30 Jan 2002 17:35:08 -0800	[thread overview]
Message-ID: <1012440909.1442.0.camel@zeus> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAIEECOCFAA.mdharm@momenco.com>

On Wed, 2002-01-30 at 17:23, Matthew Dharm wrote:
> Well, I'm closer... and more confused.
> 
> I've managed to make a 2.4.3 build which does not exhibit any of the
> instability or crashing... but I did it by disabling half of the
> memory!
> 
> In linux/arch/mips/gt64120/momenco_ocelot/setup.c is some code to read
> a PLD and add a memory region.  64MByte is already added much earlier,
> and now we're adding the rest.  The board I'm testing on is 128MByte,
> so it tries to add another 64MByte region which is physically
> contiguous to the first region.
> 
> As far as I can tell, all of my memory works perfectly.  I'm going to
> do some more tests, but both vxWorks and OpenBSD run on this board
> without any problems.
> 
> So, can anyone think of some likely culprits for what is wrong here?
> Some piece of code which only works with addresses under 64MByte,
> perhaps?

And 2.4.2 works with all of the memory?

Pete

  reply	other threads:[~2002-01-31  2:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 23:02 More data: I've made a CVS build that doesn't crash! Matthew Dharm
2002-01-31  1:23 ` Matthew Dharm
2002-01-31  1:35   ` Pete Popov [this message]
2002-01-31  1:56     ` Matthew Dharm
2002-01-31  2:40     ` Matthew Dharm
2002-01-31  2:45     ` Matthew Dharm
2002-01-31  2:55       ` Pete Popov
2002-01-31  9:30         ` Matthew Dharm
2002-01-31 17:53           ` Pete Popov

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=1012440909.1442.0.camel@zeus \
    --to=ppopov@pacbell.net \
    --cc=linux-mips@oss.sgi.com \
    --cc=mdharm@momenco.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.