linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <yang.shi@linux.alibaba.com>
To: Qian Cai <cai@gmx.us>, open list <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Waiman Long <longman@redhat.com>, 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 13:42:24 -0800	[thread overview]
Message-ID: <5c3b1cf4-1d83-c0a5-4243-28fde66b5cd9@linux.alibaba.com> (raw)
In-Reply-To: <54B1AA39-2C58-4B0C-B8A8-9F85EBA7C963@gmx.us>



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 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.

Thanks,
Yang



  reply	other threads:[~2018-11-09 21:42 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 [this message]
2018-11-09 21:51   ` Qian Cai
2018-11-09 22:01     ` Yang Shi
2018-11-09 22:08     ` Waiman Long
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=5c3b1cf4-1d83-c0a5-4243-28fde66b5cd9@linux.alibaba.com \
    --to=yang.shi@linux.alibaba.com \
    --cc=arnd@arndb.de \
    --cc=cai@gmx.us \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=tglx@linutronix.de \
    --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).