This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Problems Mounting Root File System on EVM6678

Other Parts Discussed in Thread: SYSBIOS

Hello, 

   After compiling and flashing the Linux + SYSBIOS w/Syslink demo onto my EVM6678L demo board my system will not mount the root file system.  I get the following printout at the serial console:

 

 

Designed for the EVMC6678 board, Texas Instruments.

CPU0: C66x rev 0x0, 1.2 volts, 1000MHz

Initializing kernel

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048

Kernel command line: console=ttyS0,115200 initrd=0x80400000,0x1700000 ip=dhcp rw

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

Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

Memory available: 492256k/520316k RAM, 0k/0k ROM (788k kernel code, 202k data)

SLUB: Genslabs=7, HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Hierarchical RCU implementation.

RCU-based detection of stalled CPUs is enabled.

NR_IRQS:288

Console: colour dummy device 80x25

Calibrating delay loop... 999.42 BogoMIPS (lpj=1998848)

Mount-cache hash table entries: 512

C64x: 9 gpio irqs

NET: Registered protocol family 16

SGMII init complete

bio: create slab <bio-0> at 0

Switching to clocksource TSC64

NET: Registered protocol family 2

IP route cache hash table entries: 4096 (order: 2, 16384 bytes)

TCP established hash table entries: 16384 (order: 5, 131072 bytes)

TCP bind hash table entries: 16384 (order: 4, 65536 bytes)

TCP: Hash tables configured (established 16384 bind 16384)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

Trying to unpack rootfs image as initramfs...

rootfs image is not initramfs (junk in compressed archive); looks like an initrd

Freeing initrd memory: 23552k freed

JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.

ROMFS MTD (C) 2007 Red Hat, Inc.

msgmni has been set to 1007

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

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled

serial8250.0: ttyS0 at MMIO 0x2540000 (irq = 276) is a 16550A

console [ttyS0] enabled

brd: module loaded

loop: module loaded

at24 1-0050: 131072 byte 24c1024 EEPROM (writable)

uclinux[mtd]: RAM probe address=0x803e0760 size=0x0

Creating 1 MTD partitions on "RAM":

0x000000000000-0x000000000000 : "ROMfs"

mtd: partition "ROMfs" is out of reach -- disabled

Generic platform RAM MTD, (c) 2004 Simtec Electronics

NAND device: Manufacturer ID: 0x20, Chip ID: 0x36 (ST Micro NAND 64MiB 1,8V 8-b)

Scanning device for bad blocks

Creating 3 MTD partitions on "davinci_nand.0":

0x000000000000-0x000000004000 : "bootconfig"

0x000000004000-0x000001000000 : "kernel"

0x000001000000-0x000004000000 : "filesystem"

davinci_nand davinci_nand.0: controller rev. 2.5

m25p80 spi0.0: n25q128 (16384 Kbytes)

Creating 1 MTD partitions on "spi_flash":

0x000000000000-0x000001000000 : "test"

spi_davinci spi_davinci.0: Controller at 0x20bf0000 

spi_davinci spi_davinci.0: Operating in interrupt mode using IRQ 182

keystone_netcp keystone_netcp.0: firmware: using built-in firmware keystone-pdsw

keystone_netcp keystone_netcp.0: firmware: using built-in firmware keystone-pdsw

pktgen 2.72: Packet Generator for packet performance testing.

TCP cubic registered

NET: Registered protocol family 17

Sending DHCP requests .., OK

IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.107

IP-Config: Complete:

     device=eth0, addr=192.168.1.107, mask=255.255.255.0, gw=192.168.1.1,

     host=192.168.1.107, domain=hsd1.ca.comcast.net., nis-domain=(none),

     bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=

RAMDISK: gzip image found at block 0

RAMDISK: incomplete write (28179 != 32768)

write error

Looking up port of RPC 100003/2 on 192.168.1.1

rpcbind: server 192.168.1.1 not responding, timed out

Root-NFS: Unable to get nfsd port number from server, using default

Looking up port of RPC 100005/1 on 192.168.1.1

rpcbind: server 192.168.1.1 not responding, timed out

Root-NFS: Unable to get mountd port number from server, using default

Root-NFS: Server returned error -110 while mounting /tftpboot/192.168.1.107

VFS: Unable to mount root fs via NFS, trying floppy.

VFS: Cannot open root device "(null)" or unknown-block(2,0)

Please append a correct "root=" boot option; here are the available partitions:

1f01              16 mtdblock1 (driver?)

1f02           16368 mtdblock2 (driver?)

1f03           49152 mtdblock3 (driver?)

1f04           16384 mtdblock4 (driver?)

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

Stack from 9e017f2c:

        803130a4 803130a8 80339efb 803c53e8 00000000 9e00a012 9e00a000 803a0134

        80337faf 9e017f60 9e017f60 00000000 73020002 6e6b6e75 2d6e776f 636f6c62

        2c32286b 00002930 00000000 00000000 8031317c 00000080 00000000 00000000

        803a0648 803c3240 803bfd48 00000000 00000000 00000000 00000000 00000000

        00000000 00000000 00000000 00000000 803c1ba4 803c1ba4 00000000 803c1ba4

        803c1ba4 8039fb48 00000000 00000000 00000000 00000000 00000000 80001e6c

Call trace: [<803130a4>] panic+0x64/0x120

 [<803130a8>] panic+0x68/0x120

 [<803a0134>] mount_block_root+0x2e8/0x30c

 [<8031317c>] printk+0x1c/0x40

 [<803a0648>] prepare_namespace+0x234/0x28c

 [<8039fb48>] kernel_init+0x1c4/0x1fc

 [<80001e6c>] kernel_thread_helper+0x18/0x1c

 

INFO: RCU detected CPU 0 stall (t=2500 jiffies)

INFO: RCU detected CPU 0 stall (t=10000 jiffies)

INFO: RCU detected CPU 0 stall (t=17500 jiffies)

INFO: RCU detected CPU 0 stall (t=25000 jiffies)

INFO: RCU detected CPU 0 stall (t=32500 jiffies)

I feel like this has to be one of those really simple, obvious mistakes. Again guys, any ideas?
-Brant

  • I meet this problem too and I'm looking for the solution to solve this problem. Does someone have any ideas? thanks.

  • Hi,

    Could you provide your kernel command line and how is your nfs server set up? The logs show that it does not find the nfs mount point and it could be one of the following reasons.

    1. The nfs filesystem directory does not exist or is not created from the cpio file from the same build.

    2. The nfs mount location is not specified in /etc/exports file on the server

    3. The nfs service is not running on the server

    4. The nfs server IP address in kernel command line does not match that of the nfs server.

    Could you check if all these are met?