Stephen Clark wrote:
Artem Kuchin wrote:
Claus Guttesen wrote:
Why would there be no space when I have 24GB of memory?
1. Any process, including the kernel can only allocate up to 4 GB
of memory on a 32-bit system (since a 32-bit integer can only
hold that many values)
2. The kernel is fu
On Thu, 2007-10-04 at 09:19 -0400, Stephen Clark wrote:
> Ivan Voras wrote:
>
> >Stephen Clark wrote:
> >
> >
> >
> >>looking at kmem_suballoc which calls vm_map_find which returns
> >>KERN_NO_SPACE
> >>which is defined as 3.
> >>
> >>Why would there be no space when I have 24GB of memory?
> >>
Claus Guttesen wrote:
Why would there be no space when I have 24GB of memory?
1. Any process, including the kernel can only allocate up to 4 GB of
memory on a 32-bit system (since a 32-bit integer can only hold that
many values)
2. The kernel is further constrained so the user programs can get
On Thu, Oct 04, 2007 at 03:25:42PM +0200, Claus Guttesen wrote:
> > >>Why would there be no space when I have 24GB of memory?
> > >
> > >1. Any process, including the kernel can only allocate up to 4 GB of
> > >memory on a 32-bit system (since a 32-bit integer can only hold that
> > >many values)
>
> >>Why would there be no space when I have 24GB of memory?
> >
> >1. Any process, including the kernel can only allocate up to 4 GB of
> >memory on a 32-bit system (since a 32-bit integer can only hold that
> >many values)
> >2. The kernel is further constrained so the user programs can get enough
Ivan Voras wrote:
Stephen Clark wrote:
looking at kmem_suballoc which calls vm_map_find which returns
KERN_NO_SPACE
which is defined as 3.
Why would there be no space when I have 24GB of memory?
1. Any process, including the kernel can only allocate up to 4 GB of
memory on a 32-bit
Stephen Clark wrote:
> looking at kmem_suballoc which calls vm_map_find which returns
> KERN_NO_SPACE
> which is defined as 3.
>
> Why would there be no space when I have 24GB of memory?
1. Any process, including the kernel can only allocate up to 4 GB of
memory on a 32-bit system (since a 32-bi
Chuck Swiger wrote:
Stephen Clark wrote:
Chuck Swiger wrote:
[ ... ]
Oops, I should have said 24GB.
Real Memory = 25769803776 (24576 MB)
...which matches your dmesg, right. No harm double-checking. :-)
Hmm-- I haven't put more than 3 GB into a machine which didn't have a
Hi--
Stephen Clark wrote:
I have a Dell PE 4600 with 24MB of memory that I am trying to run
6.2-RELEASE-p7 compiled with the standard PAE config file.
Just double-checking, here: your machine only has 24MB of memory?
PAE is only really useful on 32-bit systems which have 4+GB of RAM...
--
-
Stephen Clark wrote:
Chuck Swiger wrote:
[ ... ]
Oops, I should have said 24GB.
Real Memory = 25769803776 (24576 MB)
...which matches your dmesg, right. No harm double-checking. :-)
Hmm-- I haven't put more than 3 GB into a machine which didn't have a 64-bit
processor, but getting a dump
Chuck Swiger wrote:
Hi--
Stephen Clark wrote:
I have a Dell PE 4600 with 24MB of memory that I am trying to run
6.2-RELEASE-p7 compiled with the standard PAE config file.
Just double-checking, here: your machine only has 24MB of memory?
PAE is only really useful on 32-bit systems w
Hello List,
I have a Dell PE 4600 with 24MB of memory that I am trying to run
6.2-RELEASE-p7 compiled with the standard PAE config file.
I get the following at boot: (hand copied)
6.2-RELEASE-p7
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/PAE
acpi_alloc_wakeup_handler can't alloc wake memory
AC
12 matches
Mail list logo
