We investigated the problem and found out that there is some config issue.
The config option was the problem:-
Symbol: NFSD_V4 [=n]
Prompt: NFS server support for NFS version 4 (EXPERIMENTAL)
Defined at fs/nfsd/Kconfig:67
Depends on: NETWORK_FILESYSTEMS [=y] && NFSD [=n] && PROC_FS
[=y] && EXPERIMENTAL [=y]
-> File systems
-> Network File Systems (NETWORK_FILESYSTEMS [=y])
-> NFS server support (NFSD [=n])
Selects: NFSD_V3 [=n] && FS_POSIX_ACL [=y] && RPCSEC_GSS_KRB5 [=y]
On Tue, Feb 22, 2011 at 9:22 AM, naveen yadav <email@example.com> wrote:
> Hi ,
> Thanks for your answer,
> Yes I am sure it is from same kernel and sams GCC version,
> The same module if put in Initiramfs, works fine. only issue occur
> when I build kernel with rootfs mounted from NFS.
> On Mon, Feb 21, 2011 at 11:03 PM, Mulyadi Santosa
> <firstname.lastname@example.org> wrote:
>> Hi :)
>> On Mon, Feb 21, 2011 at 20:07, naveen yadav <email@example.com> wrote:
>>> Hi All,
>>> When I am trying to insert some modules on 18.104.22.168, I am getting some
>>> random crash's.
>>> There are 2 scenarios:-
>>> 1) When my rootfs is NFS mounted.
>>> In this case, when I insmod modules some get inserted and some gives crash.
>>> I have tried with following modules :-
>>> a) ext2.ko ; size 93K ; status - successfully inserted
>>> b) ext3.ko ; size 188K ; status - insertion failed
>>> c) xfs.ko ; size 823K ; status - insertion failed
>>> d) usbcore.ko ; size 243K ; status - insertion failed
>>> 2) When I created kernel Image using Initramfs, hence making all
>>> modules part of ramfs image
>>> all insertions are successfull
>> Hm, easiest thing first to check: are you sure you are inserting
>> modules that belongs to the currently running kernel's version? and
>> they were compiled with the same gcc options?
>> And furthermore, if they use symbol versioning, are they belong to the
>> same symbol version?
>> Mulyadi Santosa
>> Freelance Linux trainer and consultant
>> blog: the-hydra.blogspot.com
>> training: mulyaditraining.blogspot.com