On Mon, 27 Sep 2004, Matt Porter wrote:
> Since you are failing in ocp_add_one_device() and you have a
> processor which doesn't have a chip definition in 2.6, the
> problem is probably somewhere there. Doublecheck your
> arch/ppc/platforms/4xx/ibm405cr.c (you do have one, right?)
> against a known good one in arch/ppc/platforms/4xx/ibm405gp.c
Because I use ibm405cr.c which works good with 2.4.23 I think that's not
the problem. Remember the call stack?
setup_arch() - arch/ppc/kernel/setup.c
-> ocp_early_init() - arch/ppc/syslib/ocp.c
-> ocp_add_one_device() - arch/ppc/syslib/ocp.c
-> alloc_bootmem MACRO calling __alloc_bootmem_core() -
mm/bootmem.c
When I comment line calling ocp_early_init() I fail in:
setup_arch() - arch/ppc/kernel/setup.c
-> paging_init() - arch/ppc/mm/init.c
-> free_area_init() - arch/ppc/mm/page_alloc.c
-> free_area_init_node() - arch/ppc/mm/page_alloc.c
-> alloc_bootmem_node() MACRO calling __alloc_bootmem_node -
mm/bootmem.c
-> __alloc_bootmem_core() - mm/bootmem.c
As you can see again __alloc_bootmem_core. So maybe there's some
problem with memory?
Forgive me if I ask stupid questions, but this the first time I have
something to do with the kernel (not counting compiling for my home PC).
