public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: devzero@web.de, jcm@jonmasters.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dl9pf@gmx.de
Subject: Re: kbuild: modules_install regression ? - depmod
Date: Sat, 29 Dec 2007 04:48:46 -0500	[thread overview]
Message-ID: <1198921726.9453.13.camel@perihelion> (raw)
In-Reply-To: <Pine.LNX.4.64.0712290239020.29013@fbirervta.pbzchgretzou.qr>


On Sat, 2007-12-29 at 02:42 +0100, Jan Engelhardt wrote:
> [Adding jcm to Cc]
> 
> On Dec 28 2007 16:08, devzero@web.de wrote:
> >
> >i have the same issue, but with 2.6.24-rc6 on a box with 512MB RAM
> >
> >System is openSUSE 10.3
> >
> >on "make modules_install" , depmod reproduceably dies with out of memory error when it is ~800MB VSZ and ~350MB RSS
> >this happens on different hardware.
> >
> >any clue what`s going wrong?
> >how much memory should i expect being needed with "make modules_install" , e.g. with allmodconfig ?
> 
> 
> If you enable CONFIG_DEBUG_INFO, don't be surprised.
> 
> Though I'd say depmod should ignore the debug sections.

Thanks for the head's up. I'll look at that, and adding the module
ordering stuff over the weekend - been unplugged for the holidays.

Jon.



  reply	other threads:[~2007-12-29  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 15:08 kbuild: modules_install regression ? - depmod devzero
2007-12-29  0:01 ` Jan-Simon Möller
2007-12-29  1:42 ` Jan Engelhardt
2007-12-29  9:48   ` Jon Masters [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-29 15:51 devzero
2007-12-29 16:01 ` Jan Engelhardt
2007-12-29 13:30 devzero
2007-12-29 13:46 ` Jon Masters
2007-12-29 14:07 ` Jan Engelhardt
2007-11-01  4:14 Jan-Simon Möller

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=1198921726.9453.13.camel@perihelion \
    --to=jonathan@jonmasters.org \
    --cc=devzero@web.de \
    --cc=dl9pf@gmx.de \
    --cc=jcm@jonmasters.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox