On Mon, Oct 08, 2007 at 03:30:41PM +0200, Dag-Erling Smrgrav 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.
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
> 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
firstname.lastname@example.org email@example.com firstname.lastname@example.org