[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a781481a0706091156n773b5449n5d4a96134c3f9b66@mail.gmail.com>
Date: Sun, 10 Jun 2007 00:26:39 +0530
From: "Satyam Sharma" <satyam.sharma@...il.com>
To: "Jan Engelhardt" <jengelh@...putergmbh.de>
Cc: "Jon Masters" <jonathan@...masters.org>,
"Robert P. J. Day" <rpjday@...dspring.com>,
"Kyle McMartin" <kyle@...onical.com>,
"Christoph Pleger" <Christoph.Pleger@...uni-dortmund.de>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: Size of kernel modules
On 6/9/07, Jan Engelhardt <jengelh@...putergmbh.de> wrote:
>
> On Jun 9 2007 08:08, Jon Masters wrote:
> >
> >So I missed half of this conversation - you're saying that on a
> >CONFIG_DEBUG_KERNEL, you have such large .ko module files that depmod
> >segfaults? Can I get a core dump or any further information? :-)
>
> Just make sure your /lib/modules/<kernel> is like 300 megabytes or even
> more. Then depmod will clog up quite a lot memory already. (Taking a 256 mb ram
> machine for example, no swap or just very little.)
Yup, this would happen reproducibly on a machine with <= 256MB
RAM and swap disabled, when building a large enough modular kernel.
The depmod at end of modules_install would invariably invoke the OOM
killer, and get itself shot (taking down the shell with it, often) ...
Satyam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists