From: Waiman Long <longman@redhat.com>
To: Qian Cai <cai@gmx.us>, Yang Shi <yang.shi@linux.alibaba.com>
Cc: open list <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Arnd Bergmann <arnd@arndb.de>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
Zhong Jiang <zhongjiang@huawei.com>
Subject: Re: ODEBUG: Out of memory. ODEBUG disabled
Date: Fri, 9 Nov 2018 17:08:32 -0500 [thread overview]
Message-ID: <6698422e-c593-547b-b1c6-1e2649fa49f3@redhat.com> (raw)
In-Reply-To: <9762E093-FCDD-4DAA-8FCE-9D6B953B6F17@gmx.us>
On 11/09/2018 04:51 PM, Qian Cai wrote:
>
>> On Nov 9, 2018, at 4:42 PM, Yang Shi <yang.shi@linux.alibaba.com> wrote:
>>
>>
>>
>> On 11/9/18 1:36 PM, Qian Cai wrote:
>>> It is a bit annoying on this aarch64 server with 64 CPUs that is
>>> booting the latest mainline (3541833fd1f2) causes object debugging
>>> always running out of memory.
>> May you please paste the detail failure log?
> I assume you mean dmesg.
>
> Here is the dmesg for 64 CPUs,
> https://paste.ubuntu.com/p/BnhvXXhn7k/
>>> I have to boot the kernel with only 16 CPUs instead (nr_cpus=16)
>>> to make it work. Is it expected that object debugging is not going
>>> to work with large machines?
>> I don't think so. I'm supposed it works well with large CPU number on x86.
> Here is the one with nr_cpus workaround,
> https://paste.ubuntu.com/p/qMpd2CCPSV/
The debugobjects code have a set of 1024 statically allocated debug
objects that can be used in early boot before the slab memory allocator
is initialized. Apparently, the system may have used up all the
statically allocated objects. Try double ODEBUG_POOL_SIZE to see if it
helps.
There are also quite a number of warnings in your console log. So there
is certainly something wrong with your kernel or config options.
Cheers,
Longman
next prev parent reply other threads:[~2018-11-09 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 21:36 ODEBUG: Out of memory. ODEBUG disabled Qian Cai
2018-11-09 21:42 ` Yang Shi
2018-11-09 21:51 ` Qian Cai
2018-11-09 22:01 ` Yang Shi
2018-11-09 22:08 ` Waiman Long [this message]
2018-11-10 1:45 Qian Cai
2018-11-10 13:59 ` Waiman Long
2018-11-10 14:11 ` Qian Cai
2018-11-13 4:33 ` Qian Cai
2018-11-14 0:55 ` Qian Cai
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=6698422e-c593-547b-b1c6-1e2649fa49f3@redhat.com \
--to=longman@redhat.com \
--cc=arnd@arndb.de \
--cc=cai@gmx.us \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yang.shi@linux.alibaba.com \
--cc=zhongjiang@huawei.com \
/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).