PAE: Cannot fork
kraduk at gmail.com
Thu Apr 14 12:47:10 UTC 2011
On 14 April 2011 11:14, Dennis Nikiforov <dennis.nikiforov at gmail.com> wrote:
> 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:
> On 14 April 2011 08:05, Dennis Nikiforov <dennis.nikiforov at gmail.com>wrote:
>> 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.
>> basically the issue comes after PAE kernel has been compiled and
>> the system outputs all the time the following:
>> cannot fork kstack allocation failed or vm_thread_new: kstack
>> allocation failed
>> 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.
>> freebsd-questions at freebsd.org mailing list
>> To unsubscribe, send any mail to "
>> freebsd-questions-unsubscribe at freebsd.org"
> why not use 64 bit as the r210 should be capable
not even with lib32, also why not just not run pae. After all if its a 32bit
app it cant address all the ram anyhow
More information about the freebsd-questions