• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 1407 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DM368 IPNC kernel panic while mounting through nfs

Mayank Agarwal
Expert 2600 points


 

Hi,

 

I am trying to mount the file system  using nfs but after booting i am getting the following output.

 

DM368 IPNC :>boot

Loading from NAND 128MiB 3,3V 8-bit, offset 0x500000
   Image Name:   Linux-2.6.18_pro500-davinci_IPNC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1865336 Bytes =  1.8 MB
   Load Address: 80008000
   Entry Point:  80008000
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Linux-2.6.18_pro500-davinci_IPNC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1865336 Bytes =  1.8 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.18_pro500-davinci_IPNC_DM368_2.6.0 (mayank@mayank-laptop) (gcc version 4.2.0 (MontaVista 4.2.0-16.0.32.0801914 2008-08-30)) #1 PREEMPT Sun1
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: DaVinci DM368 IPNC
Memory policy: ECC disabled, Data cache writeback
DaVinci DM0365 variant 0x8
PLL0: fixedrate: 24000000, commonrate: 170000000, vpssrate: 340000000
PLL0: vencrate_sd: 75555555, ddrrate: 340000000 mmcsdrate: 48571428
PLL1: armrate: 432000000, voicerate: 20571428, vencrate_hd: 27000000
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists.  Total pages: 12288
Kernel command line: console=ttyS1,115200n8 noinitrd earlyprintk rw root=/dev/nfs nfsroot=10.17.8.125:/home/mayank/DM36x/ipnc/target/filesys,nolock mem=48M p
PID hash table entries: 256 (order: 8, 1024 bytes)
Clock event device timer0_0 configured with caps set: 07
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 48MB = 48MB total
Memory: 44580KB available (3193K code, 654K data, 184K init)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
DaVinci: 104 gpio irqs
MUX: initialized GPIO20
MUX: initialized I2C_SCL
Generic PHY: Registered new driver
ch0 default output "COMPOSITE", mode "NTSC"
VPBE Encoder Initialized
SCSI subsystem initialized
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered

 ***davinci_spi_board_init()!<6>
 ***davinci_spi_board_init_End(0)!<5>VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 3.1 (2006/08/19) Phillip Lougher
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
yaffs Sep  4 2011 17:00:04 Installing.
SGI XFS with no debug enabled
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
LTT : ltt-facilities init
LTT : ltt-facility-core init in kernel
DAVINCI-WDT: DaVinci Watchdog Timer: heartbeat 60 sec
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO map 0x1c20000 mem 0xfbc20000 (irq = 40) is a 16550A
serial8250.0: ttyS1 at MMIO map 0x1d06000 mem 0xfbd06000 (irq = 41) is a 16550A
RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
Davinci EMAC MII Bus: probed
MAC address is deadbeaf
TI DaVinci EMAC Linux version updated 4.0
netconsole: not configured, aborting
Linux video capture interface: v2.00
Trying to register davinci display video device.
layer=c0639000,layer->video_dev=c0639160
Trying to register davinci display video device.
layer=c04f0e00,layer->video_dev=c04f0f60
davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
i2c /dev entries driver
nand_davinci nand_davinci.0: Using 4-bit hardware ECC
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Creating 7 MTD partitions on "nand_davinci.0":
0x00000000-0x00300000 : "bootloader"
0x00300000-0x00500000 : "params"
0x00500000-0x00700000 : "kernel"
0x00700000-0x02700000 : "filesystem"
0x02700000-0x02900000 : "data1"
0x02900000-0x02d00000 : "Calibration"
0x02d00000-0x08000000 : "data2"
nand_davinci nand_davinci.0: hardware revision: 2.3
musb_hdrc: version 6.0, cppi-dma, peripheral, debug=0
musb_hdrc musb_hdrc: No DMA interrupt line
musb_hdrc: USB Peripheral mode controller at c3866000 using DMA, IRQ 12
rtc_davinci_dm365 rtc_davinci_dm365.0: rtc intf: proc
rtc_davinci_dm365 rtc_davinci_dm365.0: rtc intf: dev (254:0)
rtc_davinci_dm365 rtc_davinci_dm365.0: rtc core: registered rtc_davinci_dm365 as rtc0
davinci-mmc davinci-mmc.0: Supporting 4-bit mode
davinci-mmc davinci-mmc.0: Using DMA mode
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
ASoC version 0.13.1
CQ0093 Voice Codec 0.1
asoc: cq93vc <-> davinci-vcif mapping ok
ALSA device list:
  #0: On-chip voice codec (cq93vc)
IPv4 over IPv4 tunneling driver
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
rtc_davinci_dm365 rtc_davinci_dm365.0: setting the system clock to 2000-01-01 00:16:55 (946685815)
Time: timer0_1 clocksource has been installed.
Clock event device timer0_0 configured with caps set: 08
Switched to high resolution mode on CPU 0
Sending DHCP requests .., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.17.0.15
IP-Config: Complete:
      device=eth0, addr=10.17.0.15, mask=255.255.240.0, gw=255.255.255.255,
     host=10.17.0.15, domain=, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=10.17.8.125, rootpath=
Looking up port of RPC 100003/2 on 10.17.8.125
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 10.17.8.125
Root-NFS: Unable to get mountd port number from server, using default
mount: server 10.17.8.125 not responding, timed out
Root-NFS: Server returned error -5 while mounting /home/mayank/DM36x/ipnc/target/filesys
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
 and the output of printenv is as follows:

DM368 IPNC :>printenv
bootdelay=4
baudrate=115200
setboot=setenv bootargs $(bootargs)
bootamd=nboot 0x80700000 0 0x500000;bootm
bootfile=""
ethaddr=00:0C:0C:A0:FF:FA
rootpath=/home/mayank/DM36x/ipnc/target/filesys
nfshost=10.17.8.125
filesize=DCE000
fileaddr=82000000
ipaddr=10.17.8.131
eth=00:0C:0C:A0:07:Ea
bootcmd=nboot 0x80700000 0 0x500000;bootm
serverip=10.17.8.125
bootargs=console=ttyS1,115200n8 noinitrd earlyprintk rw root=/dev/nfs nfsroot=10.17.8.125:/home/mayank/DM36x/ipnc/target/filesys,nolock mem=48M ip=dhcp
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.3.4 (Dec  9 2010 - 17:44:14) DM368-IPNC-1.0.1

Please help me how can i get rid of this kernel panic error and boot the oard successfully through nfs.

 

REgards,

Mayank

 

  • 0
    TI__Intellectual 1195 points

    Mayank,

    It looks like the nfs server is not exporting that directory. Could you try mounting that directory from another linux system?

    Remember that you need to add the directory to /etc/exports and you need to restart nfs service after you modify /etc/exports.

    Regards,

    Carlos.

  • 0 in reply to Carlos Hernandez
    Expert 2600 points

     

     

    Hi,

     

    Thanks for your mail.Please find below the /etc/exports file:

    /home/mayank/DM36x/ipnc/target/filesys *(rw,insecure,no_root_squash,no_subtree_check)

    and also i am doing /etc/init.d/nfs-kernel-server restart also but still i am getting the kernel panic error.

    I think the boot process takes wrong ips.Following is the log from boot up process:

    IP-Config: Complete:                                                           
          device=eth0, addr=10.17.0.15, mask=255.255.240.0, gw=255.255.255.255,    
         host=10.17.0.15, domain=, nis-domain=(none),                              
         bootserver=0.0.0.0, rootserver=10.17.8.125, rootpath=

    My system(server) ip is 10.17.8.125 and the board(ipaddr) that i am setting is 10.17.8.131

    But i cannot understand from where it is taking 'addr=10.17.0.15'.I haven't specified this ip anywhere but still it is showing this ip.

    May be the kernel panic is because of this reason.

    Please guide me regarding the above observations.

     

    Thanks and Regards,

    Mayank

  • 0 in reply to Mayank Agarwal
    TI__Intellectual 1195 points

    Mayank.

    10.17.0.15 is the ip address being assigned to your dm36x board by the dhcp server as your bootargs have 'ip=dhcp', so that seems OK.

    Did you try mounting the same nfs directory on another PC to rule out nfs server issues? For example, try these on a linux pc

    sudo mkdir -p /mnt/quicktest

    sudo mount -t nfs 10.17.8.125:/home/mayank/DM36x/ipnc/target/filesys /mnt/quicktest

    Regards,

    Carlos.

     

     

     

     

  • 0 in reply to Mayank Agarwal
    TI__Mastermind 19985 points

    Mayank,

    How are your bootargs setup for ipaddress? Looking at your boot log, you are getting a new address from DHCP. What do you mean by setting up ip address if you are using DHCP as your mechanism of obtaining an IP Address?

    >>>IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.17.0.15

    The user guide explains the bootargs for static ip configuration. Please refer to it and let us know if you face any troubles. You can share your complete bootargs and we can help you accordingly.

    In all this discussion, i am assuming you have your NFS export and mounting verified on a separate system.

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.