there's a (superficially) similar problem in MS SQL Server/Windows Server. You can fix that by setting "lock pages in memory"