Date: Tue, 23 Dec 2008 14:41:18 -0600 From: Richard Todd <rmtodd@ichotolot.servalan.com> To: Alan Cox <alan.l.cox@gmail.com> Cc: freebsd-current@freebsd.org, rnoland@freebsd.org Subject: Re: Getting 'vm_thread_new: kstack allocation failed' errors after latest drm updates. Message-ID: <20081223204118.GA4507@ichotolot.servalan.com> In-Reply-To: <ca3526250812231004r49084460q56799f1f0344bcb1@mail.gmail.com> References: <x7wsdsk3nz.fsf@ichotolot.servalan.com> <ca3526250812221327y26339f12pbdc03704262c88a7@mail.gmail.com> <20081223011032.GA3228@ichotolot.servalan.com> <ca3526250812231004r49084460q56799f1f0344bcb1@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 23, 2008 at 12:04:49PM -0600, Alan Cox wrote: > Roughly speaking, vm.kvm_* pertain to the kernel's address space and > vm.kmem_* pertain to the kernel's heap within its address space. Your > settings of vm.kmem_* have made the heap so large that there is little or no > free space left in the address space for other things. These other things, > e.g., the buffer cache, are non-trivial in size. > > So, the short answer is that you need to reduce vm.kmem_size. > > Alan Ah, so there's stuff the kernel allocates that's not inside the region controlled by kmem_size. Interesting. Anyway, knocking vm.kmem_size down by 128M seems to fix things. Thanks! Richard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081223204118.GA4507>