Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: kernel hang indigo2 current cvs more specific
Date: Tue, 4 Apr 2000 22:34:15 +0200	[thread overview]
Message-ID: <20000404223415.D1517@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10004041057310.24463-100000@dandelion.sonytel.be>; from Geert Uytterhoeven on Tue, Apr 04, 2000 at 10:59:43AM +0200

On Tue, Apr 04, 2000 at 10:59:43AM +0200, Geert Uytterhoeven wrote:
> > My suspicion is that the memory map(s) are not correct and initializing
> > existing memory causes this fault.
> 
> Perhaps this helps: the bootmem stuff in arch/mips/ddb5074/prom.c works fine.
> The DDB5074 has 64 MB of fixed non-upgradable memory at physical 0x00000000
> virtual 0x80000000.

IIRC the Virtual/Physical mapping is on the Mips cpus 1:1 on bootup right ?
So what would one pass to init_bootmem and co ?

At the moment i see start 0x8800 and size 0xff85 

Then - A bit later - the bitmap gets allocated (Free all - allocate/reserve
back - Changed that - Not the fault) ~0x1ff4 bytes ~2 Pages - I tried
to increase this (bootmap_size*4) but still in the mm/bootmem.c
the machine crashes in the memset as it trys to memset to 0
from 88002000 and ~4MB ... The most interesting thing is that even
if i increase the bootmap_size (*4) the memset begins at the same address - 
It seems that it doesnt care on allocation.

I had a look at the end of mm/bootmem.c:__alloc_bootmem_core
and saw that it trys to memset from 0x88002000.

So currently i think i lost the overview and something very obvious goes
on ...

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."

      parent reply	other threads:[~2000-04-04 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-03 23:54 kernel hang indigo2 current cvs more specific Florian Lohoff
2000-04-04  8:22 ` Florian Lohoff
2000-04-04  8:59   ` Geert Uytterhoeven
2000-04-04 19:02     ` Florian Lohoff
2000-04-04 19:11       ` Florian Lohoff
2000-04-04 20:34     ` Florian Lohoff [this message]

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=20000404223415.D1517@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linux@cthulhu.engr.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox