From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id E6685DDE20 for ; Mon, 26 Feb 2007 11:44:40 +1100 (EST) Subject: Re: Make sure we populate the initroot filesystem late enough From: David Woodhouse To: Linus Torvalds In-Reply-To: References: <200612112059.kBBKx1j7022473@hera.kernel.org> <1172448057.3971.9.camel@shinybook.infradead.org> Content-Type: text/plain Date: Sun, 25 Feb 2007 19:45:04 -0500 Message-Id: <1172450704.3971.30.camel@shinybook.infradead.org> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, Linux Kernel Mailing List , john stultz List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, 2007-02-25 at 16:24 -0800, Linus Torvalds wrote: > Hmm. No, I don't think that should be a problem. free_initmem() only > happens at the very, after do_basic_setup() has been run, which includes > all the initcall stuff. > However, it's an interesting observation. How sure are you that it's this > commit that triggers it. You say "This seems to be what's triggering ..", > I'm wondering how firm that is.. I found it with git-bisect. The Fedora kernel has been broken on this particular 512MiB Mac Mini for a while, and now I've reverted the patch it seems to be fine again. So I'm fairly sure. I'll be surer in a few minutes once the full RPM build has finished with the patch reverted. Of course, it could easily be an entirely separate bug which by some bizarre coincidence is just triggered by this. -- dwmw2