U-Boot 2010.06-00002-g9ba65ce-dirty (Dec 04 2010 - 15:22:03)
SV-RRNVR

SoC: Kirkwood 88F6281_A0
DRAM: 512 MiB
NAND: 1024 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Net: egiga1
No such device: egiga0
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x100000, size 0x300000
3145728 bytes read: OK
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
## Booting kernel from Legacy Image at 06400000 ...
Image Name: Linux-2.6.32.9-00009-g18e8c23-di
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2444772 Bytes = 2.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux...This is svrrnvr ...




.................................................................................................... ........................................................

At the above I have written snippet of what I am getting after booting linux from u-boot...

Machine IDs are same so no issue with that...

Can you please provide further details ???

Bootags parameters are :-

x_bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0x000000(uboot),0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw ubi.mtd=2,2048

No, we can't provide any details at all, because you haven't asked a clear question. A snippet? I see one warning and one error in what you posted...have you dealt with those? You mention machine ID's being the same...same as WHAT? Do you have this working on identical hardware elsewhere? Has this EVER worked?

Ya uboot and kernel have worked before I made some changes to that.

By the way machine ID is 2882

Ok...now how about providing some actual, useful information, like WHAT changes you made?? If it was working, and now it's not, chances are very good the problem has to do with whatever changes you made. So, undo them, or document them here, along with DETAILS about what you're trying to accomplish, and maybe we can help.

And machine ID of 2882 tells us nothing about your hardware.

Hi, I got my problem solved... There was a software bug in modified kernel...