linux-mips
[Top] [All Lists]

cause of early indigo2 crash

To: linux@cthulhu.engr.sgi.com
Subject: cause of early indigo2 crash
From: Florian Lohoff <flo@rfc822.org>
Date: Wed, 5 Apr 2000 22:34:13 +0200
Organization: rfc822 - pure communication
Sender: owner-linuxmips@oss.sgi.com
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."


<Prev in Thread] Current Thread [Next in Thread>