Re: Error inserting lockd: Cannot allocate memory In alt.os.linux.gentoo Arthur Hagen <art@broomstick.com> wrote:
> I assume you have CONFIG_DEBUG_BUGVERBOSE=y in .config?
No I didn't because I never thought I would be having a problem like
this. My systems have always been pretty reliable until now.
I notice that the kernel has been updated, since I downloaded my version
two months ago, and I think NFS is being aggressively developed, so
maybe there are some updates.
I possibly just chose a bad time to go for a build. I'll probably end up
trying again at a later date with a newer kernel.
I've stuck a note out to the NFS developer mailing list, so we shall see
if I get any responses there.
> Other than that, "rmmod lockd; modprobe -v lockd" might give /slightly/ more
> info.
Nahh, it just tells me that the error is occuring after running insmod,
which I had already established.
Mark.
--
Mark Hobley,
393 Quinton Road West,
Quinton, BIRMINGHAM.
B32 1QE. |