Date: Mon, 8 Oct 2007 15:44:07 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org> Subject: Re: ZFS kmem_map too small. Message-ID: <20071008134407.GB67153@cicely12.cicely.de> In-Reply-To: <86bqb97mym.fsf@ds4.des.no> References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <86bqb97mym.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 08, 2007 at 03:30:41PM +0200, Dag-Erling Smørgrav wrote: > Pawel Jakub Dawidek <pjd@FreeBSD.org> writes: > > I'm not sure if it's not too late to ask re@ about increasing the > > default kmem size at least on amd64. ~300MB we have there is silly > > small. > > Speaking of which, I tried setting vm.kmem_size to 2G on a C2D system > with 4 GB RAM, but it simply panics: > > OK set vm.kmem_size=2G This sounds like there's a signed 32 bit limit somewhere. Wild guess: Maybe it is a loader parsing limitation and not one of the kernel. > OK boot -s > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2007 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 7.0-CURRENT #8: Tue Sep 25 13:31:41 CEST 2007 > des@ds4.des.no:/usr/obj/usr/src/sys/ds4 > kmem_suballoc: bad status return of 3. > panic: kmem_suballoc > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at kdb_enter+0x31: popq %rbp > db> where > Tracing pid 0 tid 0 td 0xffffffff805af4a0 > kdb_enter() at kdb_enter+0x31 > panic() at panic+0x166 > kmem_suballoc() at kmem_suballoc+0xc3 > kmeminit() at kmeminit+0x16e > mi_startup() at mi_startup+0x59 > btext() at btext+0x2c > db> reset > > with vm.kmem_size unset and vm.kmem_size_max=2G, it boots fine: What is the vakue for vm.kmem_size_max after booting? Maybe a errously parsed value on max isn't that critical. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071008134407.GB67153>