[Top] [All Lists]

Re: mkinitrd, ramdisk failure?

To: "D. Stimits" <stimits@xxxxxxxxxx>
Subject: Re: mkinitrd, ramdisk failure?
From: Sebastian Dransfeld <sebastid@xxxxxxxxxxxx>
Date: Thu, 14 Jun 2001 02:57:08 +0200 (MET DST)
Cc: "XFS: linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <3B280776.2A753E89@xxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Wed, 13 Jun 2001, D. Stimits wrote:

> Chris Pascoe wrote:
> >
> > > This fails, though it succeeds all the way up until root filesystem
> > > mount is attempted. I'm a bit frustrated by the lack of good debug
> > > information when a root filesystem mount fails :( For example, I wish it
> > > would say which modules were loaded at the time of failure.
> >
> > If you've got KDB support built in, can you hit the break key to enter it,
> > and do an "lsmod" at this point?  It should tell you what modules are
> > loaded?  Keith, correct me if I am wrong..
> >
> > Chris
> I have not used KDB yet, it looks like I'll need to. But, say for the
> moment I do have KDB. "lsmod" is on the root partition, and uses libc
> which is also on the root partition. Would enabling KDB help to run
> lsmod, or would it be another catch-22?

Compile a static version of lsmod.


<Prev in Thread] Current Thread [Next in Thread>