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 11:23:09 +0000 [thread overview]
Message-ID: <56D57B9D.7020604@arm.com> (raw)
In-Reply-To: <BY1PR0701MB159496D44DB36F8C3699D3A5E1BB0@BY1PR0701MB1594.namprd07.prod.outlook.com>
On 01/03/16 10:48, Jaggi, Manish wrote:
>
>>> From: linux-arm-kernel <linux-arm-kernel-bounces@lists.infradead.org> on behalf of Jaggi, Manish <Manish.Jaggi@caviumnetworks.com>
>>> Sent: Monday, February 29, 2016 5:56 PM
>>> To: linux-arm-kernel at lists.infradead.org
>>> Subject: for-next/pgtable branch: OOM error with 16K page size
>>>
>>> Hi All,
>>>
>>> I am trying to use the for-next/pgtable branch with the top commit,
>
> The same issue is observed with for-next/core branch
>
>>> Observations:
>>> a) During linux boot I see some oom messages
>>> http://pastebin.com/8jSMFhqf
>>>
>>> b) cat /proc/meminfo
>>>
>>> MemTotal: 66613760 kB
>>> MemFree: 307328 kB
>>> MemAvailable: 22416 kB
>>>
Could you please provide the complete o/p of the following
with 16K ?
1) /proc/meminfo
2) /proc/buddyinfo
3) /proc/slabinfo
Thanks
Suzuki
next prev parent reply other threads:[~2016-03-01 11:23 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 [this message]
2016-03-01 12:03 ` Jaggi, Manish
2016-03-01 12:17 ` Suzuki K. Poulose
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=56D57B9D.7020604@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.