linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki.Poulose@arm.com (Suzuki K. Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: for-next/pgtable branch: OOM error with 16K page size
Date: Tue, 1 Mar 2016 12:17:54 +0000	[thread overview]
Message-ID: <56D58872.2010506@arm.com> (raw)
In-Reply-To: <BY1PR0701MB1594A21349ED87C30F900102E1BB0@BY1PR0701MB1594.namprd07.prod.outlook.com>

On 01/03/16 12:03, Jaggi, Manish wrote:
>>> From: Suzuki K. Poulose <Suzuki.Poulose@arm.com>
>>> Sent: Tuesday, March 1, 2016 4:53 PM
>>> To: Jaggi, Manish
>>> Cc: linux-arm-kernel at lists.infradead.org; mark.rutland at arm.com
>>> Subject: Re: for-next/pgtable branch: OOM error with 16K page size
>>>

>>> Could you please provide the complete o/p of the following
>>> with 16K ?
>>>
>>> 1) /proc/meminfo

> http://pastebin.com/Eszwp1cS

> HugePages_Total:    2019
> HugePages_Free:     2019
> HugePages_Rsvd:        0
> HugePages_Surp:        0
> Hugepagesize:      32768 kB

That clearly tells you whats wrong. You have 2019x32M in hugepages.
Could you try releasing them and see if it solves the memory issue ?

$ echo 0 > /sys/kernel/mm/hugepages/hugepages-32768kB/nr_hugepages


btw, whats your root file system(to be more precise, the init) ?

Cheers
Suzuki

  reply	other threads:[~2016-03-01 12:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 12:26 for-next/pgtable branch: OOM error with 16K page size Jaggi, Manish
2016-03-01 10:48 ` Jaggi, Manish
2016-03-01 11:23   ` Suzuki K. Poulose
2016-03-01 12:03     ` Jaggi, Manish
2016-03-01 12:17       ` Suzuki K. Poulose [this message]
2016-03-01 12:51         ` Suzuki K. Poulose
2016-03-01 11:32   ` Mark Rutland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56D58872.2010506@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).