From: devzero@web.de
To: jcm@jonmasters.org, Jan Engelhardt <jengelh@computergmbh.de>
Cc: dl9pf@gmx.de, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kbuild: modules_install regression ? - depmod
Date: Sat, 29 Dec 2007 14:30:03 +0100 [thread overview]
Message-ID: <75140323@web.de> (raw)
> [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.
>
oh yes, that`s it!
apparently CONFIG_DEBUG_KERNEL, CONFIG_DEBUG_BUGVERBOSE and CONFIG_DEBUG_INFO defaults to "y" on my distro`s kernel, and i just copied config from /proc/config.gz and did a "make oldconfig".
after disabling those, all is fine now !
thanks for the hint!
> Though I'd say depmod should ignore the debug sections.
so depmod is acting sort of "stupid" here ?
regards
roland
>
> >
> >
> >Subject: kbuild: modules_install regression ? - depmod
> >From: Jan-Simon =?utf-8?q?M=C3=B6ller?= <dl9pf () gmx ! de>
> >Date: 2007-11-01 4:14:34
> >Message-ID: 200711010514.34469.dl9pf () gmx ! de
> >[Download message RAW]
> >
> >Hi!
> >
> >I compiled kernel 2.6.24-rc1 (latest git as of today) on a Box with 256MB Ram.
> >During "make modules_install" I got these errors:
> >
> > DEPMOD 2.6.24-rc1-default
> >WARNING: Can't read
> >module /lib/modules/2.6.24-rc1-default/kernel/net/bridge/bridge.ko: Cannot
> >allocate memory
> >WARNING: Can't read
> >module /lib/modules/2.6.24-rc1-default/kernel/net/bridge/netfilter/ebt_redirect.ko:
> >Cannot allocate memory
> >[...]
> >FATAL: Memory allocation failure depmod.c line 158: realloc(mod->deps,
> >sizeof(mod->deps[0])*(mod->num_deps+1)).
> >make: *** [_modinst_post] Fehler 1
> >
> >
> >Depmod used too much memory and exits. Tried a 2nd time and checked with top.
> >
> >IMHO this is a regression.
> >
> >best regards
> >jan-simon
> >
> >__________________________________________________________________________
> >Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!
> >Mehr Infos unter http://produkte.web.de/club/?mc=021131
> >
> >--
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
> >
>
>
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!
Mehr Infos unter http://produkte.web.de/club/?mc=021131
next reply other threads:[~2007-12-29 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 13:30 devzero [this message]
2007-12-29 13:46 ` kbuild: modules_install regression ? - depmod Jon Masters
2007-12-29 14:07 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2007-12-29 15:51 devzero
2007-12-29 16:01 ` Jan Engelhardt
2007-12-28 15:08 devzero
2007-12-29 0:01 ` Jan-Simon Möller
2007-12-29 1:42 ` Jan Engelhardt
2007-12-29 9:48 ` Jon Masters
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=75140323@web.de \
--to=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