svn commit: r216016 - head/sys/sparc64/include

[mdf at FreeBSD.org]

On Mon, Dec 6, 2010 at 2:07 PM, Marius Strobl <marius at alchemy.franken.de> wrote:
[lots of snip]

> With that one the kernel now survies memguard_init() but then panics
> right afterwards when kmeminit() calls kmem_suballoc():
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> Copyright (c) 1992-2010 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>        The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.0-CURRENT #18 r215249:216120M: Mon Dec  6 13:27:57 CET 2010
>    marius at v20z.zeist.de:/home/marius/co/build/head2/sparc64.sparc64/usr/home/m4
> WARNING: WITNESS option enabled, expect reduced performance.
> panic: kmem_suballoc: bad status return of 3

[more snip]

Shooting in the dark a little...

The bad status of 3 is presumably KERN_NO_SPACE because we attempted
to allocate too much space from the kernel_map.  What are the actual
values of vm_kmem_size, kernel_map->min_offset, kernel_map->max_offset
at panic time?  How much virtual space does sparc64 support (since
earlier it was reported it's computed based on hardware capability,
for this specific machine?)

Thanks,
matthew