Date: Thu, 14 Apr 2011 13:14:37 +0300 From: Dennis Nikiforov <dennis.nikiforov@gmail.com> To: krad <kraduk@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: PAE: Cannot fork Message-ID: <209FDCEC-0335-4C1D-9974-ACB2BCFDEC28@gmail.com> In-Reply-To: <BANLkTin4GvZAMZBUOjWniHUj=SR6dbiYNw@mail.gmail.com> References: <DA71C51E-0652-41C9-AB0B-4F069121D3C6@gmail.com> <BANLkTin4GvZAMZBUOjWniHUj=SR6dbiYNw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
There is a legacy piece of custom software that runs only on 32 bit = systems, so going to 64 bit is not possible. On Apr 14, 2011, at 12:08 PM, krad wrote: >=20 >=20 > On 14 April 2011 08:05, Dennis Nikiforov <dennis.nikiforov@gmail.com> = wrote: > Hello, >=20 > I have a problem with FreeBSD 7.x 32bit running the standard = PAE kernel on a dell R210 server with 16GB of RAM. All servers spec'ed = like this have the same identical problem and it is not a hardware issue = because all memory tests have been negative. >=20 > basically the issue comes after PAE kernel has been compiled = and the system outputs all the time the following: >=20 > cannot fork kstack allocation failed or vm_thread_new: kstack = allocation failed >=20 > Since, this is a dell server there is basically nothing that I = can disable in BIOS, so perhaps someone knows what loader options do I = need to tweak the kernel and stop this from happening. >=20 > Thanks, > Dennis_______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org" >=20 >=20 > why not use 64 bit as the r210 should be capable
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?209FDCEC-0335-4C1D-9974-ACB2BCFDEC28>