Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 2 Nov 2002 11:37:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 2 Nov 2002 11:37:01 -0500 Received: from ip68-13-110-204.om.om.cox.net ([68.13.110.204]:14208 "EHLO dad.molina") by vger.kernel.org with ESMTP id ; Sat, 2 Nov 2002 11:37:01 -0500 Date: Sat, 2 Nov 2002 10:42:45 -0600 (CST) From: Thomas Molina X-X-Sender: tmolina@dad.molina To: Gerd Knorr cc: Alexander Viro , Linus Torvalds , Kernel List Subject: Re: [PATCH] Re: 2.5.45: initrd broken? In-Reply-To: <20021101224327.GA3303@bytesex.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1100 Lines: 27 On Fri, 1 Nov 2002, Gerd Knorr wrote: > > Patch below fixes these. It also changes order of blkdev_put()/del_gendisk() > > in initrd_release() - better safe than sorry. > > > > It got initrd working on my boxen... > > [ patch snipped ] > > Initrd works now, thanks. > > The box still doesn't boot through, the initrd fails to load the ext3 > module due to unresolved symbols (mb_cache_*). That issue looks like a > kbuild problem to me: I have ACL's enabled (which builds the mbcache.o > module). I also have the nfs server with v4 support enabled (which > doesn't build currently). Running "make -k modules_install" does _not_ > install the mbcache.o in /lib/modules/2.5.45. I suspect this happens > due to the build error in the nfsd subdirectory. So do I mark my problem report for initrd broken as closed, or wait until it appears in bk? - 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/