* kernel hang indigo2 current cvs more specific
@ 2000-04-03 23:54 Florian Lohoff
2000-04-04 8:22 ` Florian Lohoff
0 siblings, 1 reply; 6+ messages in thread
From: Florian Lohoff @ 2000-04-03 23:54 UTC (permalink / raw)
To: linux
Ok,
i debugged a bit arround and found that the current CVS kernel
hang at "alloc_page.c" (For SGI_IP22)
lmem_map = (struct page *) alloc_bootmem_node(nid, map_size);
I had a small look into the function alloc_bootmem_node/core but didnt
understand a word.
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."
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: kernel hang indigo2 current cvs more specific
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
0 siblings, 1 reply; 6+ messages in thread
From: Florian Lohoff @ 2000-04-04 8:22 UTC (permalink / raw)
To: linux
On Tue, Apr 04, 2000 at 01:54:30AM +0200, Florian Lohoff wrote:
> Ok,
> i debugged a bit arround and found that the current CVS kernel
> hang at "alloc_page.c" (For SGI_IP22)
>
> lmem_map = (struct page *) alloc_bootmem_node(nid, map_size);
>
> I had a small look into the function alloc_bootmem_node/core but didnt
> understand a word.
Reduced it even more - At the end of alloc_bootmem_core the memset is
the fault - It seems to overwrite something and/or does not return.
My suspicion is that the memory map(s) are not correct and initializing
existing memory causes this fault.
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."
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: kernel hang indigo2 current cvs more specific
2000-04-04 8:22 ` Florian Lohoff
@ 2000-04-04 8:59 ` Geert Uytterhoeven
2000-04-04 19:02 ` Florian Lohoff
2000-04-04 20:34 ` Florian Lohoff
0 siblings, 2 replies; 6+ messages in thread
From: Geert Uytterhoeven @ 2000-04-04 8:59 UTC (permalink / raw)
To: Florian Lohoff; +Cc: linux
On Tue, 4 Apr 2000, Florian Lohoff wrote:
> On Tue, Apr 04, 2000 at 01:54:30AM +0200, Florian Lohoff wrote:
> > i debugged a bit arround and found that the current CVS kernel
> > hang at "alloc_page.c" (For SGI_IP22)
> >
> > lmem_map = (struct page *) alloc_bootmem_node(nid, map_size);
> >
> > I had a small look into the function alloc_bootmem_node/core but didnt
> > understand a word.
>
> Reduced it even more - At the end of alloc_bootmem_core the memset is
> the fault - It seems to overwrite something and/or does not return.
>
> 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.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven ------------- Sony Software Development Center Europe (SDCE)
Geert.Uytterhoeven@sonycom.com ------------------- Sint-Stevens-Woluwestraat 55
Voice +32-2-7248638 Fax +32-2-7262686 ---------------- B-1130 Brussels, Belgium
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: kernel hang indigo2 current cvs more specific
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
1 sibling, 1 reply; 6+ messages in thread
From: Florian Lohoff @ 2000-04-04 19:02 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: linux
On Tue, Apr 04, 2000 at 10:59:43AM +0200, Geert Uytterhoeven wrote:
>
> 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.
Do you or anyone else have a clue why i cant find anything like this
bootmap_size = init_bootmem(start_pfn, mem_size >> PAGE_SHIFT);
/* Free the entire available memory after the _end symbol. */
free_start += bootmap_size;
free_bootmem(free_start, free_end-free_start);
in the arch/mips/sgi/kernel/ directory ? Could it be that this structure
is new and has never been implemented for the IP22 ?
Yep - Thats it - In 2.3.21 this init_bootmem thing doesnt exists - And though
dec hasnt got it - In 2.3.99pre3 the dec has it - But not the sgi *grrrrr*
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."
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: kernel hang indigo2 current cvs more specific
2000-04-04 19:02 ` Florian Lohoff
@ 2000-04-04 19:11 ` Florian Lohoff
0 siblings, 0 replies; 6+ messages in thread
From: Florian Lohoff @ 2000-04-04 19:11 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: linux
On Tue, Apr 04, 2000 at 09:02:57PM +0200, Florian Lohoff wrote:
> in the arch/mips/sgi/kernel/ directory ? Could it be that this structure
> is new and has never been implemented for the IP22 ?
>
> Yep - Thats it - In 2.3.21 this init_bootmem thing doesnt exists - And though
> dec hasnt got it - In 2.3.99pre3 the dec has it - But not the sgi *grrrrr*
Ops - Better look around before writing mails - arc ...
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."
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: kernel hang indigo2 current cvs more specific
2000-04-04 8:59 ` Geert Uytterhoeven
2000-04-04 19:02 ` Florian Lohoff
@ 2000-04-04 20:34 ` Florian Lohoff
1 sibling, 0 replies; 6+ messages in thread
From: Florian Lohoff @ 2000-04-04 20:34 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: linux
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."
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2000-04-04 20:57 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox