[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: panic: pmap_map_chunk: no L2 table for VA 0xc0400000
First I would like to thank you for the excellent explanation about
how to put NetBSD on NSLU2.
I have followed your instructions to the letter.
One thing that I was missing was the building of the tools I have
done this with "./build.sh -u -m evbarm -a armeb tools"
But after a days work which I enjoyed I got nothing but a error
about L2 ?
I don't know what this means do you have any idea what went wrong or
even better do you have the solution?
RedBoot(tm) bootstrap and debug environment
Red Hat certified release, version 1.92 - built 15:16:07, Feb 3
Platform: IXDP425 Development Platform
Copyright (C) 2000, 2001, 2002, Red Hat,
RAM: 0x00000000-0x02000000, 0x000723a0-0x01ff3000
FLASH: 0x50000000 - 0x50800000, 64 blocks of 0x00020000 bytes
== Executing boot script in 2.000 seconds - enter ^C to
RedBoot> ip_address -l 172.16.1.117 -h
IP: 172.16.1.117/255.255.255.0, Gateway:
Default server: 172.16.1.1, DNS server IP:
RedBoot> load -r -b 0x200000
Using default protocol
Raw file loaded 0x00200000-0x007bba03, assumed entry at
panic: pmap_map_chunk: no L2 table for VA 0xc0400000
Rene van der Meer
$ grep -r pmap_map_chunk * | grep "L2 table"
arch/arm/arm32/pmap.c: * of the kernel L2 tables during bootstrap, so
that pmap_map_chunk() can
arch/arm/arm32/pmap.c: panic("pmap_map_chunk: no L2
table for VA 0x%08lx", va);
arch/arm/arm32/pmap.c: panic("pmap_map_chunk: can't
find L2 table for VA"
pmap_chunk:arch/arm/arm32/pmap.c: * of the kernel L2 tables during
bootstrap, so that pmap_map_chunk() can
panic("pmap_map_chunk: no L2 table for VA 0x%08lx", va);
panic("pmap_map_chunk: can't find L2 table for VA"
So it's probably in the above file that the failing call is made. It
seems unlikely that there is something wrong with the kernel file, so
the most likely problem is that something didn't get built right. I
don't think you should be using the -u switch when building tools, but
whether that is the problem remains to be seen.
I'm not sure which instructions you were following, but the process that
seems to work best can be found at:
If you have a serial port installed, you can ignore the telnet stuff and
just use your serial port to login. Skip down to the bottom if you want
to use the installer rather than go the NFS route. Try the above link
and let me know. If you were already using that procedure, try it again
(you may want to consider starting from scratch), then let me know.
I recommend that in the future you address your questions/comments to
the NetBSD arm mailing list, which I've included on this email. I'll
get a copy either way, but if you go through the mailing list, you'll
likely get an answer from somebody that knows better than me why you're
having this problem.
Main Index |
Thread Index |