archive mirror
 help / color / mirror / Atom feed
From: Josh Poimboeuf <>
To: Randy Dunlap <>
Cc: LKML <>,
	Peter Zijlstra <>
Subject: Re: linux-next: objtool hang/loop?
Date: Wed, 4 Aug 2021 11:34:19 -0700	[thread overview]
Message-ID: <20210804183419.k7p3tvqerwgzxpuz@treble> (raw)
In-Reply-To: <>

On Wed, Jul 28, 2021 at 07:25:21PM -0700, Randy Dunlap wrote:
> Hi Josh & Peter,
> Yesterday (2021-07-27), one of my x86_64 randconfig build ran for
> over 2 hours (it's a slow core i5 laptop and spinning rust media).
> I killed it and reran the .config file today on linux-next-20210728.
> I killed this one after 30 minutes on its last message:
>   OBJTOOL vmlinux.o
> This is a .config with # CONFIG_MODULES is not set.
> vmlinux.o is 253 MB in size.
> I see that using verbose make (V=1) won't help me any here.
> The problematic (if it is a problem: maybe I didn't wait long
> enough?) .config file is attached.  The gzipped vmlinux.o file is at:
> If there is a problem, I can test any patches...

Hi Randy,

I'm guessing your laptop doesn't have a lot of RAM.  I ran

  /usr/bin/time -v tools/objtool/objtool check --noinstr --vmlinux --no-fp --uaccess vmlinux.o

It showed a max RSS of 6.5GB.

Can you try this patch from Peter?  It halves the memory usage.


  reply	other threads:[~2021-08-04 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  2:25 Randy Dunlap
2021-08-04 18:34 ` Josh Poimboeuf [this message]
2021-08-04 20:47   ` Randy Dunlap
2021-08-05 11:05   ` Peter Zijlstra

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:

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

  git send-email \
    --in-reply-to=20210804183419.k7p3tvqerwgzxpuz@treble \ \ \ \ \
    --subject='Re: linux-next: objtool hang/loop?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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