linux-kernel - Re: ODEBUG: Out of memory. ODEBUG disabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 9 Nov 2018 16:51:50 -0500
From:   Qian Cai <cai@....us>
To:     Yang Shi <yang.shi@...ux.alibaba.com>
Cc:     open list <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Waiman Long <longman@...hat.com>,
        Arnd Bergmann <arnd@...db.de>,
        "Joel Fernandes (Google)" <joel@...lfernandes.org>,
        Zhong Jiang <zhongjiang@...wei.com>
Subject: Re: ODEBUG: Out of memory. ODEBUG disabled



> On Nov 9, 2018, at 4:42 PM, Yang Shi <yang.shi@...ux.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/