Dear Simon,
> So if he config sparse memory, the issue can be solved I think.
In my config file I have:
CONFIG_HAVE_SPARSE_IRQ=y
CONFIG_SPARSE_IRQ=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_SPARSEMEM_STATIC=y
# CONFIG_INPUT_SPARSEKMAP is not set
# CONFIG_SPARSE_
On 01/14/2013 11:00 PM, Dave Hansen wrote:
On 01/11/2013 07:31 PM, paul.sz...@sydney.edu.au wrote:
Seems that any i386 PAE machine will go OOM just by running a few
processes. To reproduce:
sh -c 'n=0; while [ $n -lt 1 ]; do sleep 600 & ((n=n+1)); done'
My machine has 64GB RAM. With previ
Dear Pavel and Dave,
> The assertion was that 4GB with no PAE passed a forkbomb test (ooming)
> while 4GB of RAM with PAE hung, thus _PAE_ is broken.
Yes, PAE is broken. Still, maybe the above needs slight correction:
non-PAE HIGHMEM4G passed the "sleep test": no OOM, nothing unexpected;
whereas
On 01/30/2013 04:51 AM, Pavel Machek wrote:
> Are you saying that HIGHMEM configuration with 4GB ram is not expected
> to work?
Not really.
The assertion was that 4GB with no PAE passed a forkbomb test (ooming)
while 4GB of RAM with PAE hung, thus _PAE_ is broken.
--
To unsubscribe from this lis
Hi!
> > I understand that more RAM leaves less lowmem. What is unacceptable is
> > that PAE crashes or freezes with OOM: it should gracefully handle the
> > issue. Noting that (for a machine with 4GB or under) PAE fails where the
> > HIGHMEM4G kernel succeeds and survives.
>
> You have found a de
On 01/17/2013 01:04 PM, paul.sz...@sydney.edu.au wrote:
>>> On my large machine, 'free' fails to show about 2GB memory ...
>> You probably have a memory hole. ...
>> The e820 map (during early boot in dmesg) or /proc/iomem will let you
>> locate your memory holes.
>
> Now that my machine is runnin
Dear Dave,
>> On my large machine, 'free' fails to show about 2GB memory ...
> You probably have a memory hole. ...
> The e820 map (during early boot in dmesg) or /proc/iomem will let you
> locate your memory holes.
Now that my machine is running an amd64 kernel, 'free' shows total Mem
65854128 (
Dear Dave,
>> ... What is unacceptable is that PAE crashes or freezes with OOM:
>> it should gracefully handle the issue. Noting that (for a machine
>> with 4GB or under) PAE fails where the HIGHMEM4G kernel succeeds ...
>
> You have found a delta, but you're not really making apples-to-apples
> c
On 01/14/2013 12:36 PM, paul.sz...@sydney.edu.au wrote:
> I understand that more RAM leaves less lowmem. What is unacceptable is
> that PAE crashes or freezes with OOM: it should gracefully handle the
> issue. Noting that (for a machine with 4GB or under) PAE fails where the
> HIGHMEM4G kernel succ
Dear Dave,
>> Seems that any i386 PAE machine will go OOM just by running a few
>> processes. To reproduce:
>> sh -c 'n=0; while [ $n -lt 1 ]; do sleep 600 & ((n=n+1)); done'
>> ...
> I think what you're seeing here is that, as the amount of total memory
> increases, the amount of lowmem ava
On 01/11/2013 07:31 PM, paul.sz...@sydney.edu.au wrote:
> Seems that any i386 PAE machine will go OOM just by running a few
> processes. To reproduce:
> sh -c 'n=0; while [ $n -lt 1 ]; do sleep 600 & ((n=n+1)); done'
> My machine has 64GB RAM. With previous OOM episodes, it seemed that
> runn
The issue is a regression with PAE, reproduced and verified on Ubuntu,
on my home PC with 3GB RAM.
My PC was running kernel linux-image-3.2.0-35-generic so it showed:
psz@DellE520:~$ uname -a
Linux DellE520 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:45:18 UTC 2012
i686 i686 i386 GNU/Linux
12 matches
Mail list logo
