Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS

srinivasanshanm — Fri, 13 Sep 2013 19:24:35 GMT

Dear All,

Am unable to mount the roots using NFS I verified, NFS server from linux pc is getting started & running, this is straining me so much, I am trying to set statically, dont want to do it dynamically, am stcuk in this from 3 days.. could any body pls let me know hw to get rid of this problem once for all :smileysad:, I followed the I.mx28 BSP UG, u-boot_mx28, step by step user guide, but still am facing the same issue, kindly do the needful as soon as possible with fully detailed procedure to get rid of this problem

Awaiting for replies

Many Many Thanks in advance

U-Boot 2009.08 (Sep 12 2013 - 17:05:40)

Freescale i.MX28 family

CPU: 454 MHz

BUS: 151 MHz

EMI: 205 MHz

GPMI: 24 MHz

DRAM: 128 MB

MMC: IMX_SSP_MMC: 0, IMX_SSP_MMC: 1

In: serial

Out: serial

Err: serial

Net: got MAC address from IIM: 00:04:9f:02:b5:66

FEC0

Warning: FEC0 MAC addresses don't match:

Address in SROM is 00:04:9f:02:b5:66

Address in environment is 00:04:9f:00:ea:d7

Hit any key to stop autoboot: 0

MX28 U-Boot >

MX28 U-Boot > printenv

bootargs=console=ttyAM0,115200n8

bootcmd=run bootcmd_net

bootdelay=3

baudrate=115200

netmask=255.255.255.0

bootfile="uImage"

loadaddr=0x42000000

bootcmd_net=run bootargs_nfs; dhcp; bootm

bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p3 rw rootwait ip=dhcp fec_mac=${ethaddr}

bootcmd_mmc=run bootargs_mmc; mmc read 0 ${loadaddr} 100 3000; bootm

ethact=FEC0

setenv=nfsroot /tools/rootfs

serverip=10.7.240.37

ipaddr=10.9.68.47

ethaddr=00:04:9F:00:EA:D7

bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=10.9.68.47 nfsroot=${serverip}:${nfsroot} fec_mac=00:04:9F:00:EA:D7 gpmi

nfsroot=/tools/rootfs

gatewayip=10.7.240.1

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 2009.08 (Sep 12 2013 - 17:05:40)

Environment size: 722/130044 bytes

MX28 U-Boot > setenv ipaddr 10.7.240.39

MX28 U-Boot > saveenv

Saving Environment to MMC...

Writing to MMC(0)... done

MX28 U-Boot > setenv bootargs_nfs 'setenv bootargs ${bootargs} root=/dev/nfs ip=10.7.240.39 nfsroot=${serverip}:${nfsroot} fec_mac=00:04:9F:00:EA:D7 gpmi'

MX28 U-Boot > saveenv

Saving Environment to MMC...

Writing to MMC(0)... done

MX28 U-Boot > printenv

bootargs=console=ttyAM0,115200n8

bootcmd=run bootcmd_net

bootdelay=3

baudrate=115200

netmask=255.255.255.0

bootfile="uImage"

loadaddr=0x42000000

bootcmd_net=run bootargs_nfs; dhcp; bootm

bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p3 rw rootwait ip=dhcp fec_mac=${ethaddr}

bootcmd_mmc=run bootargs_mmc; mmc read 0 ${loadaddr} 100 3000; bootm

ethact=FEC0

setenv=nfsroot /tools/rootfs

serverip=10.7.240.37

ethaddr=00:04:9F:00:EA:D7

nfsroot=/tools/rootfs

gatewayip=10.7.240.1

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 2009.08 (Sep 12 2013 - 17:05:40)

ipaddr=10.7.240.39

bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=10.7.240.39 nfsroot=${serverip}:${nfsroot} fec_mac=00:04:9F:00:EA:D7 gpmi

Environment size: 724/130044 bytes

MX28 U-Boot > boot

BOOTP broadcast 1

FEC: Link is down 7809

BOOTP broadcast 2

BOOTP broadcast 3

DHCP client bound to address 10.9.67.58

Using FEC0 device

TFTP from server 10.7.240.37; our IP address is 10.9.67.58; sending through gateway 10.9.67.1

Filename 'uImage'.

Load address: 0x42000000

Loading: #################################################################

#################################################################

###################################################

done

Bytes transferred = 1590284 (18440c hex)

## Booting kernel from Legacy Image at 42000000 ...

Image Name: Linux-2.6.35.3-571-gcca29a0

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1590220 Bytes = 1.5 MB

Load Address: 40008000

Entry Point: 40008000

Verifying Checksum ... OK

Loading Kernel Image ... OK

Starting kernel ...

Deepak Uncompressing Linux... done, booting the kernel.

Linux version 2.6.35.3-571-gcca29a0 (root@ubuntu-desktop) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #5 Tue Sep 10 16:02:02 IST 2013

Kernel command line: console=ttyAM0,115200n8 root=/dev/nfs ip=10.7.240.39 nfsroot=10.7.240.37:/tools/rootfs fec_mac=00:04:9F:00:EA:D7 gpmi

PID hash table entries: 512 (order: -1, 2048 bytes)

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 128MB = 128MB total

Memory: 126448k/126448k available, 4624k reserved, 0K highmem

Virtual kernel memory layout:

vector : 0xffff0000 - 0xffff1000 ( 4 kB)

fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

DMA : 0xfde00000 - 0xffe00000 ( 32 MB)

vmalloc : 0xc8800000 - 0xf0000000 ( 632 MB)

lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)

modules : 0xbf000000 - 0xc0000000 ( 16 MB)

.init : 0xc0008000 - 0xc0027000 ( 124 kB)

.text : 0xc0027000 - 0xc0305000 (2936 kB)

.data : 0xc0306000 - 0xc0324d20 ( 124 kB)

SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Hierarchical RCU implementation.

RCU-based detection of stalled CPUs is disabled.

Verbose stalled-CPUs detection is disabled.

NR_IRQS:288

console [ttyAM0] enabled

Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)

pid_max: default: 32768 minimum: 301

CPU: Testing write buffer coherency: ok

regulator: core version 0.5

NET: Registered protocol family 16

regulator: vddd: 800 <--> 1575 mV at 1500 mV fast normal

regulator: vdddbo: 800 <--> 1575 mV fast normal

regulator: vdda: 1500 <--> 2275 mV at 1800 mV fast normal

vddio = 3380000, val=10

regulator: vddio: 2880 <--> 3680 mV at 3380 mV fast normal

regulator: overall_current: fast normal

regulator: vbus5v:

regulator: mxs-duart-1: fast normal

regulator: mxs-bl-1: fast normal

regulator: mxs-i2c-1: fast normal

regulator: mmc_ssp-1: fast normal

regulator: mmc_ssp-2: fast normal

regulator: charger-1: fast normal

regulator: power-test-1: fast normal

regulator: cpufreq-1: fast normal

i.MX IRAM pool: 124 KB@0xc8820000

Initializing GPMI pins

usb DR wakeup device is registered

IMX usb wakeup probe

audit: cannot initialize inotify handle

SCSI subsystem initialized

Switching to clocksource mxs clock source

Bus freq driver module loaded

mxs_cpu_init: Entering .........

mxs_cpu_init: harish cpu_clk=c030bb28

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_cpu_init: cpufreq init finished

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish freq_KHz=454736

audit: initializing netlink socket (disabled)

type=2000 audit(0.460:1): initialized

msgmni has been set to 246

Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)

io scheduler noop registered (default)

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=64000

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs-duart.0: ttyAM0 at MMIO 0x80074000 (irq = 47) is a DebugUART

mxs-auart.0: ttySP0 at MMIO 0x8006a000 (irq = 112) is a mxs-auart.0

Found APPUART 3.1.0

mxs-auart.1: ttySP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1

Found APPUART 3.1.0

mxs-auart.2: ttySP2 at MMIO 0x8006e000 (irq = 114) is a mxs-auart.2

Found APPUART 3.1.0

mxs-auart.3: ttySP3 at MMIO 0x80070000 (irq = 115) is a mxs-auart.3

Found APPUART 3.1.0

brd: module loaded

loop: module loaded

Loading iSCSI transport class v2.0-870.

i.MX GPMI NFC

NFC: Version 1, 8-chip GPMI and BCH

Boot ROM: Version 1, Single-chip boot area, block mark swapping supported

Scanning for NAND Flash chips...

******************* DEEPAK Scanning for NAND Flash chips...

DEEPAK says No NAND device found.

gpmi-nfc gpmi-nfc.0: Chip scan failed

ARC USBOTG Device Controller driver (1 August 2005)

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

check_parameters:UTP settings are in place now, overriding defaults

g_file_storage gadget: File-backed Storage Gadget, version: 20 November 2008

g_file_storage gadget: Number of LUNs=1

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish target_freq=454736

set_freq_table: harish policy->cur=454736

set_freq_table: harish policy->governor=c0322dec

set_freq_table: harish policy->min=261818

set_freq_table: harish policy->max=454736

mxs_target: harish ..... exiting from mxs_target

fsl-usb2-udc: bind to driver g_file_storage

mice: PS/2 mouse device common for all mice

input: mxs-kbd as /devices/platform/mxs-kbd.0/input/input0

input: MXS touchscreen as /devices/virtual/input/input1

MXS RTC driver v1.0 hardware v2.3.0

mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0

mxs_getspeed: harish cpu=0

mxs_verify_speed: harish cpu_clk=(null)

mxs_target: harish freq_KHz=454736

mxs-mmc: MXS SSP Controller MMC Interface driver

mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96

mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:41:44 UTC (2504)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255)

Backtrace:

[<c002b6e4>] (dump_backtrace+0x0/0x114) from [<c027d5d0>] (dump_stack+0x18/0x1c)

r7:c0021a14 r6:00008000 r5:c7c14000 r4:c0325c18

[<c027d5b8>] (dump_stack+0x0/0x1c) from [<c027d634>] (panic+0x60/0xdc)

[<c027d5d4>] (panic+0x0/0xdc) from [<c0008f9c>] (mount_block_root+0x25c/0x2ac)

r3:00000000 r2:00000000 r1:c7c27f60 r0:c02cbaa5

[<c0008d40>] (mount_block_root+0x0/0x2ac) from [<c0009040>] (mount_root+0x54/0x6c)

[<c0008fec>] (mount_root+0x0/0x6c) from [<c00091c4>] (prepare_namespace+0x16c/0x1c4)

r5:c0021a29 r4:c0324fe0

[<c0009058>] (prepare_namespace+0x0/0x1c4) from [<c00084e8>] (kernel_init+0x118/0x158)

r5:c00208dc r4:c0324da0

[<c00083d0>] (kernel_init+0x0/0x158) from [<c0044b68>] (do_exit+0x0/0x5f0)

r5:c00083d0 r4:00000000

i.MX ProcessorsのトピックRe: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS

Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS

Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS

Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS

Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS

Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS

Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block, in i.mx28 EVK using NFS