Date: Mon, 6 Dec 2010 14:30:01 -0800 From: mdf@FreeBSD.org To: Marius Strobl <marius@alchemy.franken.de> Cc: src-committers@freebsd.org, Alan Cox <alc@rice.edu>, alc@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org, Max Khon <fjoe@samodelkin.net> Subject: Re: svn commit: r216016 - head/sys/sparc64/include Message-ID: <AANLkTinhyfHmdP4K5QVC5tv%2BGN%2BfzNpvU%2BV4JKF_cMHv@mail.gmail.com> In-Reply-To: <20101206220733.GG38282@alchemy.franken.de> References: <201011281926.oASJQKiE040689@svn.freebsd.org> <20101128194542.GF9966@alchemy.franken.de> <AANLkTinwkVO%2BRkr7coYGhuMdZ_UQQa3_18c3D6fBLucA@mail.gmail.com> <20101129192308.GX80343@alchemy.franken.de> <20101129192417.GA18893@alchemy.franken.de> <4CF691A5.8070608@rice.edu> <20101202164727.GB38282@alchemy.franken.de> <4CF7D711.9040505@rice.edu> <20101206220733.GG38282@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 6, 2010 at 2:07 PM, Marius Strobl <marius@alchemy.franken.de> w= rote: [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 > =A0 =A0 =A0 =A0The Regents of the University of California. All rights re= served. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.0-CURRENT #18 r215249:216120M: Mon Dec =A06 13:27:57 CET 2010 > =A0 =A0marius@v20z.zeist.de:/home/marius/co/build/head2/sparc64.sparc64/u= sr/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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinhyfHmdP4K5QVC5tv%2BGN%2BfzNpvU%2BV4JKF_cMHv>