Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: linux@cthulhu.engr.sgi.com
Subject: cause of early indigo2 crash
Date: Wed, 5 Apr 2000 22:34:13 +0200	[thread overview]
Message-ID: <20000405223413.B996@paradigm.rfc822.org> (raw)

Hi,
i discovered that the prom of the indigo2 reports 2 MEMTYPE_FREE
segments - One at 08002000 and the other at 88000000 - The second one
at least 16 times larger - If i exclude the first segment from beeing
freed and thus used the kernel boots much further - This is what
i did in the arch/mips/arc/memory.c

        for (i = 0; pblocks[i].size; i++)
                if (pblocks[i].type == MEMTYPE_FREE &&
                                pblocks[i].base != 0x8002000)
                        free_bootmem(pblocks[i].base, pblocks[i].size);

Now i get a very different crash - After SCSI Detection i get

scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=96, scaling
scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=80, scaling
scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=64, scaling
scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=48, scaling
       WARNING, not enough memory, pool not expanded
Unable to handle kernel paging request at virtual address 00000000, epc == 880cc668, ra == 880cc5d8
[...]

Thats it - Might the first area be DMA bounce buffer only which have to
be initialized in the memory controller ?

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

             reply	other threads:[~2000-04-06  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-05 20:34 Florian Lohoff [this message]
2000-04-06  8:51 ` cause of early indigo2 crash Geert Uytterhoeven
2000-04-06 10:08   ` Florian Lohoff
2000-04-06 21:05   ` Florian Lohoff

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=20000405223413.B996@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --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