2010-08-10 14:09:11 nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92294
I followed the instructions in docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:nfs&s[]=nfs and read through the NFS_HOWTO to configure nfs in host and BF537 stamp board, however, still get Kernel panic with error -13 (permission denied). One thing I noticed is that Kernel command line is not shown in the log. After I modifed the bootargs as
setenv bootargs 'earlyprintk=serial,uart0,57600 console=ttyBF0,57600 root=/dev/nfs rw nfsroot=158.218.109.31:/data/dsplinux/uClinux-dist/romfs ip=158.218.109.199:158.218.109.31:158.218.109.2:255.255.255.0:bf537-stamp:eth0:off'
still cannot mount fs via nfs. The kernel version is: Linux-2.6.28.10-ADI-2009R1.1. Please help check the config, thanks!
-Garrett
-------------------------
bfin> printenv
bootargs=root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,5760
0
bootdelay=5
baudrate=57600
loads_echo=1
autoload=no
netmask=255.255.255.0
hostname=bf537-stamp
loadaddr=0x1000000
ubootfile=u-boot.bin
update=tftp $(loadaddr) $(ubootfile);protect off 0x20000000 0x2003FFFF;erase 0x20000000 0x2003FFFF;c
p.b $(loadaddr) 0x20000000 $(filesize)
addip=set bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off
ramargs=set bootargs root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console
=ttyBF0,57600
flashboot=bootm 0x20100000
ethact=Blackfin EMAC
ethaddr=00:E0:22:FE:60:B2
ramboot=tftp $(loadaddr) uImage_my;run ramargs;run addip;bootm
gatewayip=158.218.109.2
serverip=158.218.109.31
ipaddr=158.218.109.199
nfsboot=tftp $(loadaddr) vmImage_my;run nfsargs;run addip;bootm
rootpath=/data/dsplinux/uClinux-dist/romfs
nfsargs=set bootargs root=/dev/nfs rw
nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3,rsize=1024,wsize=1024
bootcmd=run nfsboot
stdin=serial
stdout=serial
stderr=serial
Environment size: 1073/8188 bytes
-----------------------------
bfin> run nfsboot
Using Blackfin EMAC device
TFTP from server 158.218.109.31; our IP address is 158.218.109.199
Filename 'vmImage_my'.
Load address: 0x1000000
Loading: #################################################################
#####
done
Bytes transferred = 1020849 (f93b1 hex)
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-2.6.28.10-ADI-2009R1.1
Created: 2010-08-09 21:27:53 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 1020785 Bytes = 996.9 kB
Load Address: 00001000
Entry Point: 001c9938
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 001c9938
console [ttyBF0] enabled, bootconsole disabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory available: 54868k/65536k RAM, (132k init code, 1219k kernel code, 549k data, 1024k dma, 7744k
reserved)
Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)
Security Framework initialized
Mount-cache hash table entries: 512
Blackfin Scratchpad data SRAM: 4 KB
Blackfin L1 Data A SRAM: 16 KB (15 KB free)
Blackfin L1 Data B SRAM: 16 KB (16 KB free)
Blackfin L1 Instruction SRAM: 48 KB (36 KB free)
net_namespace: 288 bytes
NET: Registered protocol family 16
Blackfin DMA Controller
stamp_init(): registering device resources
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
msgmni has been set to 107
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART
brd: module loaded
bfin_mii_bus: probed
bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc
_div=24)@sclk=125MHz)
bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1
bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma ch
annel@7
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
bfin-wdt: initialized: timeout=20 sec (nowayout=0)
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-bfin rtc-bfin: setting system clock to 2006-05-12 19:58:25 UTC (1147463905)
IP-Config: Complete:
device=eth0, addr=158.218.109.199, mask=255.255.255.0, gw=158.218.109.2,
host=bf537-stamp, domain=, nis-domain=(none),
bootserver=158.218.109.31, rootserver=158.218.109.31, rootpath=
Looking up port of RPC 100003/2 on 158.218.109.31
PHY: 0:01 - Link is Up - 100/Full
Looking up port of RPC 100005/1 on 158.218.109.31
Root-NFS: Server returned error -13 while mounting /tftpboot/bf537-stamp
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
============================================================================
cat /etc/exports
/data/dsplinux/uClinux-dist/romfs *(rw,no_root_squash,no_all_squash,sync)
---------------
$ /usr/sbin/rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 855 status
100024 1 tcp 858 status
100007 2 udp 716 ypbind
100007 1 udp 716 ypbind
100007 2 tcp 719 ypbind
100007 1 tcp 719 ypbind
100021 1 udp 47162 nlockmgr
100021 3 udp 47162 nlockmgr
100021 4 udp 47162 nlockmgr
100021 1 tcp 32783 nlockmgr
100021 3 tcp 32783 nlockmgr
100021 4 tcp 32783 nlockmgr
100011 1 udp 664 rquotad
100011 2 udp 664 rquotad
100011 1 tcp 679 rquotad
100011 2 tcp 679 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 675 mountd
100005 1 tcp 688 mountd
100005 2 udp 675 mountd
100005 2 tcp 688 mountd
100005 3 udp 675 mountd
100005 3 tcp 688 mountd
$ /sbin/chkconfig --list nfs
nfs 0:off 1:off 2:on 3:on 4:on 5:on 6:off
$ /sbin/chkconfig --list portmap
portmap 0:off 1:off 2:off 3:on 4:on 5:on 6:off
QuoteReplyEditDelete
2010-08-10 14:50:55 Re: nfs failure in BF537 stamp with kernel 2009R1.1
Mike Frysinger (UNITED STATES)
Message: 92295
look at the nfsboot command:
nfsboot=tftp $(loadaddr) vmImage_my;run nfsargs;run addip;bootm
and then look at nfsargs:
nfsargs=set bootargs root=/dev/nfs rw
so the value of bootargs before doing 'run nfsboot' is irrelevant as it'll simply be clobbered
QuoteReplyEditDelete
2010-08-10 18:35:03 Re: nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92297
After I modified the bootargs, I didn’t run nfsboot, but manually tftp $(loadaddr) vmImage_my, and then bootm .
With the config listed here, why the nfsargs is not passed to kernel command line? Is this the reason of nfs failure? But the config is same as shown in docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:nfs&s[]=nfs,
The ‘trobleshooting’ in the link says error -13 is ‘Permission denied from the server means your server is misconfigured.’
What’s the root cause of the problem? Thanks…
QuoteReplyEditDelete
2010-08-10 18:49:28 Re: nfs failure in BF537 stamp with kernel 2009R1.1
Mike Frysinger (UNITED STATES)
Message: 92298
that isnt what you said. your posting: "After I modifed the bootargs as" ... "bfin> run nfsboot". nowhere did you say you ran any command by hand.
the documentation does show the args being correctly passed:
Kernel command line: root=/dev/nfs rw nfsroot=192.168.0.17:/usr/local/src/blackfin/svn/uclinux-dist/trunk/romfs,tcp,nfsvers=3 ip=192.168.0.15:192.168.0.17:192.168.0.1:255.255.255.0:1:eth0:off
that was expanded from doing 'run nfsargs' and 'run addip'
the assumption on the troubleshooting section is that your kernel command line is correct. if it's wrong (like yours is), then it doesnt apply.
QuoteReplyEditDelete
2010-08-10 21:38:24 Re: nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92299
Thanks for your prompt response. Mike, let’s forget the modified bootarg, do you see any mistake from above ‘printenv’? It’s understood that the args was correctly passed in that document, but why the same configure is not working in my board?
QuoteReplyEditDelete
2010-08-10 23:34:10 Re: nfs failure in BF537 stamp with kernel 2009R1.1
Mike Frysinger (UNITED STATES)
Message: 92300
you need to add earlyprintk to your nfsargs to see the full boot log:
set nfsargs $(nfsargs) earlyprintk=serial,uart0,57600 console=ttyBF0,57600
save
run nfsboot
then post the updated kernel boot output
QuoteReplyEditDelete
2010-08-11 08:35:13 Re: nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92321
With earlyprintk, I can see the kernel command line now. It seems the nfsargs was actually run previously but not displayed. The kernel is still panic…
-------------------------------------
bfin> printenv
bootdelay=5
baudrate=57600
loads_echo=1
autoload=no
hostname=bf537-stamp
loadaddr=0x1000000
ubootfile=u-boot.bin
update=tftp $(loadaddr) $(ubootfile);protect off 0x20000000 0x2003FFFF;erase 0x20000000 0x2003FFFF;c
p.b $(loadaddr) 0x20000000 $(filesize)
addip=set bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off
ramargs=set bootargs root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console
=ttyBF0,57600
flashboot=bootm 0x20100000
ethact=Blackfin EMAC
ethaddr=00:E0:22:FE:60:B2
ramboot=tftp $(loadaddr) uImage_my;run ramargs;run addip;bootm
nfsboot=tftp $(loadaddr) vmImage_my;run nfsargs;run addip;bootm
rootpath=/data/dsplinux/uClinux-dist/romfs
nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3,rsize=1024,wsize=1024
filesize=F93B1
fileaddr=1000000
gatewayip=158.218.109.2
netmask=255.255.255.0
ipaddr=158.218.109.199
serverip=158.218.109.31
bootargs=root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,5760
0
bootcmd=run ramboot
stdin=serial
stdout=serial
stderr=serial
nfsargs=set bootargs root=/dev/nfs rw earlyprintk=serial,uart0,57600 console=ttyBF0,57600
Environment size: 1157/8188 bytes
bfin> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
. done
Protected 1 sectors
bfin> run nfsboot
Using Blackfin EMAC device
TFTP from server 158.218.109.31; our IP address is 158.218.109.199
Filename 'vmImage_my'.
Load address: 0x1000000
Loading: #################################################################
################
done
Bytes transferred = 1183234 (120e02 hex)
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-2.6.28.10-ADI-2009R1.1
Created: 2010-08-10 17:12:43 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 1183170 Bytes = 1.1 MB
Load Address: 00001000
Entry Point: 0021b938
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 0021b938
Linux version 2.6.28.10-ADI-2009R1.1 (a0132884@gt9fq2701.gt.design.ti.com) (gcc version 4.1.2 (ADI s
vn)) #35 Tue Aug 10 13:12:11 EDT 2010
bootconsole [early_shadow0] enabled
bootconsole [early_BFuart0] enabled
early printk enabled on early_BFuart0
Warning: limiting memory to 56MB due to hardware anomaly 05000263
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
fixedcode = 0x00000400-0x00000490
text = 0x00001000-0x00161170
rodata = 0x00161170-0x001d2f48
bss = 0x001d3000-0x001f1438
data = 0x001f1438-0x0020c000
stack = 0x0020a000-0x0020c000
init = 0x0020d000-0x0022f000
available = 0x0022f000-0x037ff000
DMA Zone = 0x03f00000-0x04000000
Hardware Trace Active and Enabled
Boot Mode: 0
Blackfin support (C) 2004-2009 Analog Devices, Inc.
Compiled for ADSP-BF537 Rev 0.2
Warning: Compiled for Rev 2, but running on Rev 3
Blackfin Linux support by blackfin.uclinux.org/
Processor Speed: 500 MHz core clock and 125 MHz System Clock
NOMPU: setting up cplb tables
Instruction Cache Enabled for CPU0
Data Cache Enabled for CPU0 (write-back)
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 14223
Kernel command line: root=/dev/nfs rw earlyprintk=serial,uart0,57600 console=ttyBF0,57600 ip=158.218
.109.199:158.218.109.31:158.218.109.2:255.255.255.0:bf537-stamp:eth0:off
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
console [ttyBF0] enabled, bootconsole disabled
console [ttyBF0] enabled, bootconsole disabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory available: 54536k/65536k RAM, (136k init code, 1408k kernel code, 688k data, 1024k dma, 7744k
reserved)
Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)
Security Framework initialized
Mount-cache hash table entries: 512
Blackfin Scratchpad data SRAM: 4 KB
Blackfin L1 Data A SRAM: 16 KB (15 KB free)
Blackfin L1 Data B SRAM: 16 KB (16 KB free)
Blackfin L1 Instruction SRAM: 48 KB (36 KB free)
net_namespace: 288 bytes
NET: Registered protocol family 16
Blackfin DMA Controller
stamp_init(): registering device resources
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
msgmni has been set to 106
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART
brd: module loaded
bfin_mii_bus: probed
bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc
_div=24)@sclk=125MHz)
bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1
bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma ch
annel@7
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
bfin-wdt: initialized: timeout=20 sec (nowayout=0)
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-bfin rtc-bfin: setting system clock to 2006-05-13 16:32:03 UTC (1147537923)
IP-Config: Complete:
device=eth0, addr=158.218.109.199, mask=255.255.255.0, gw=158.218.109.2,
host=bf537-stamp, domain=, nis-domain=(none),
bootserver=158.218.109.31, rootserver=158.218.109.31, rootpath=
Looking up port of RPC 100003/2 on 158.218.109.31
PHY: 0:01 - Link is Up - 100/Full
Looking up port of RPC 100005/1 on 158.218.109.31
Root-NFS: Server returned error -13 while mounting /tftpboot/bf537-stamp
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
QuoteReplyEditDelete
2010-08-11 09:07:02 Re: nfs failure in BF537 stamp with kernel2009R1.1
Michael Hennerich (GERMANY)
Message: 92322 Did you follow the docs here:
docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:nfs#nfs_root
> Kernel command line: root=/dev/nfs rw earlyprintk=serial,uart0,57600
> console=ttyBF0,57600 ip=158.218
>
> .109.199:158.218.109.31:158.218.109.2:255.255.255.0:bf537-
> stamp:eth0:off
Your kernel command line is incomplete
QuoteReplyEditDelete
2010-08-11 09:09:04 Re: nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92323
Update: add nfsroot in nfsargs,
nfsargs=set bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3,rsize=1024,wsize
=1024 earlyprintk=serial,uart0,57600 console=ttyBF0,57600
Root-NFS: Server returned error -13 while mounting /data/dsplinux/uClinux-dist/romfs
----------------
bfin> printenv
bootdelay=5
baudrate=57600
loads_echo=1
autoload=no
hostname=bf537-stamp
loadaddr=0x1000000
ubootfile=u-boot.bin
update=tftp $(loadaddr) $(ubootfile);protect off 0x20000000 0x2003FFFF;erase 0x20000000 0x2003FFFF;c
p.b $(loadaddr) 0x20000000 $(filesize)
addip=set bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off
ramargs=set bootargs root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console
=ttyBF0,57600
flashboot=bootm 0x20100000
ethact=Blackfin EMAC
ethaddr=00:E0:22:FE:60:B2
ramboot=tftp $(loadaddr) uImage_my;run ramargs;run addip;bootm
nfsboot=tftp $(loadaddr) vmImage_my;run nfsargs;run addip;bootm
rootpath=/data/dsplinux/uClinux-dist/romfs
nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3,rsize=1024,wsize=1024
filesize=F93B1
fileaddr=1000000
gatewayip=158.218.109.2
netmask=255.255.255.0
ipaddr=158.218.109.199
serverip=158.218.109.31
bootargs=root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,5760
0
bootcmd=run ramboot
nfsargs=set bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3,rsize=1024,wsize
=1024 earlyprintk=serial,uart0,57600 console=ttyBF0,57600
stdin=serial
stdout=serial
stderr=serial
Environment size: 1225/8188 bytes
bfin> run nfsboot
Using Blackfin EMAC device
TFTP from server 158.218.109.31; our IP address is 158.218.109.199
Filename 'vmImage_my'.
Load address: 0x1000000
Loading: #################################################################
################
done
Bytes transferred = 1183234 (120e02 hex)
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-2.6.28.10-ADI-2009R1.1
Created: 2010-08-10 17:12:43 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 1183170 Bytes = 1.1 MB
Load Address: 00001000
Entry Point: 0021b938
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 0021b938
Linux version 2.6.28.10-ADI-2009R1.1 (a0132884@gt9fq2701.gt.design.ti.com) (gcc version 4.1.2 (ADI s
vn)) #35 Tue Aug 10 13:12:11 EDT 2010
bootconsole [early_shadow0] enabled
bootconsole [early_BFuart0] enabled
early printk enabled on early_BFuart0
Warning: limiting memory to 56MB due to hardware anomaly 05000263
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
fixedcode = 0x00000400-0x00000490
text = 0x00001000-0x00161170
rodata = 0x00161170-0x001d2f48
bss = 0x001d3000-0x001f1438
data = 0x001f1438-0x0020c000
stack = 0x0020a000-0x0020c000
init = 0x0020d000-0x0022f000
available = 0x0022f000-0x037ff000
DMA Zone = 0x03f00000-0x04000000
Hardware Trace Active and Enabled
Boot Mode: 0
Reset caused by Software reset
Blackfin support (C) 2004-2009 Analog Devices, Inc.
Compiled for ADSP-BF537 Rev 0.2
Warning: Compiled for Rev 2, but running on Rev 3
Blackfin Linux support by blackfin.uclinux.org/
Processor Speed: 500 MHz core clock and 125 MHz System Clock
NOMPU: setting up cplb tables
Instruction Cache Enabled for CPU0
Data Cache Enabled for CPU0 (write-back)
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 14223
Kernel command line: root=/dev/nfs rw nfsroot=158.218.109.31:/data/dsplinux/uClinux-dist/romfs,tcp,n
fsvers=3,rsize=1024,wsize=1024 earlyprintk=serial,uart0,57600 console=ttyBF0,57600 ip=158.218.109.19
9:158.218.109.31:158.218.109.2:255.255.255.0:bf537-stamp:eth0:off
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
console [ttyBF0] enabled, bootconsole disabled
console [ttyBF0] enabled, bootconsole disabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory available: 54536k/65536k RAM, (136k init code, 1408k kernel code, 688k data, 1024k dma, 7744k
reserved)
Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)
Security Framework initialized
Mount-cache hash table entries: 512
Blackfin Scratchpad data SRAM: 4 KB
Blackfin L1 Data A SRAM: 16 KB (15 KB free)
Blackfin L1 Data B SRAM: 16 KB (16 KB free)
Blackfin L1 Instruction SRAM: 48 KB (36 KB free)
net_namespace: 288 bytes
NET: Registered protocol family 16
Blackfin DMA Controller
stamp_init(): registering device resources
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
msgmni has been set to 106
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART
brd: module loaded
bfin_mii_bus: probed
bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc
_div=24)@sclk=125MHz)
bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1
bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma ch
annel@7
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
bfin-wdt: initialized: timeout=20 sec (nowayout=0)
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-bfin rtc-bfin: setting system clock to 2006-05-13 17:17:16 UTC (1147540636)
IP-Config: Complete:
device=eth0, addr=158.218.109.199, mask=255.255.255.0, gw=158.218.109.2,
host=bf537-stamp, domain=, nis-domain=(none),
bootserver=158.218.109.31, rootserver=158.218.109.31, rootpath=
Looking up port of RPC 100003/3 on 158.218.109.31
PHY: 0:01 - Link is Up - 100/Full
Looking up port of RPC 100005/3 on 158.218.109.31
Root-NFS: Server returned error -13 while mounting /data/dsplinux/uClinux-dist/romfs
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
QuoteReplyEditDelete
2010-08-11 11:25:32 Re: nfs failure in BF537 stamp with kernel 2009R1.1
Mike Frysinger (UNITED STATES)
Message: 92325
and now you're back to posible server misconfiguration. review the documentation and your server config and make sure you can mount these paths from other machines before worrying about the Blackfin board.
QuoteReplyEditDelete
2010-08-11 14:41:58 Re: nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92333
The directory /data/dsplinux/uClinux-dist/romfs does have permission issue when trying to mount to other machine. romfs is copied to another directory /opt. Not sure if it's because dsplinux/ is automounted to /data. Now, root is mounted by nfs, thanks for the help.
A new issue is file is not sync-ed - I can't see the file from board when it's created in server.
Another problem 'Warning: unable to open an initial console.' It seems a pretty old issue in the forum, but I do see /dev/console after telnet into it...
Any hint is appreciated.
-------------------
Kernel command line: root=/dev/nfs rw nfsroot=158.218.109.31:/opt/romfs,tcp,nfsvers=3,rsize=1024,wsi
ze=1024 earlyprintk=serial,uart0,57600 console=ttyBF0,57600 ip=158.218.109.199:158.218.109.31:158.21
8.109.2:255.255.255.0:bf537-stamp:eth0:off
Looking up port of RPC 100003/3 on 158.218.109.31
PHY: 0:01 - Link is Up - 100/Full
Looking up port of RPC 100005/3 on 158.218.109.31
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 136k freed
Warning: unable to open an initial console.
root:/> cd dev
root:/dev> ls
console ptmx ram2 spi
cpu_dma_latency pts ram3 stderr
fd ram0 ram4 stdin
full ram1 ram5 stdout
kmsg ram10 ram6 tty
log ram11 ram7 ttyBF0
mem ram12 ram8 urandom
network_latency ram13 ram9 watchdog
network_throughput ram14 random zero
null ram15 rtc0
root:/dev>
QuoteReplyEditDelete
2010-08-11 18:02:05 Re: nfs failure in BF537 stamp with kernel 2009R1.1
Mike Frysinger (UNITED STATES)
Message: 92338
once again, please read the documentation:
docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:nfs#nfs_root
it specifically talks about /dev needs in your nfs root
as for the server/client issue, that is "normal" behavior when dealing with nfs mounts. i often see the same exact behavior with my linux desktop and a server. however, i never cared enough to look into the issue since nfs is such a large/complicated kernel blob and not worth the time.
if it really matters to you, you can try asking about it on the nfs mailing list:
vger.kernel.org/vger-lists.html#linux-nfs
QuoteReplyEditDelete
2010-08-11 22:02:21 Re: nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92341
Checked again the link docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:nfs#nfs_root
It says: make sure your nfsroot directory has a /dev directory and a few device nodes (like /dev/console).
As shown in my previous posting, /dev/console is there, why still ‘unable to open an initial console’?
QuoteReplyEditDelete
2010-08-11 22:22:51 Re: nfs failure in BF537 stamp with kernel 2009R1.1
Mike Frysinger (UNITED STATES)
Message: 92342
it says "the nfsroot directory". it does not say "look at what the board has mounted and populated locally". i.e. the view from the board is irrelevant.
QuoteReplyEditDelete
2010-08-12 11:53:57 Re: nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92381
Thanks, now I can see ‘Have a lot of fun’ after manually making node of console in nfsroot directory. From the sentence ‘make sure your nfsroot directory has a /dev directory and a few device nodes (like /dev/console) ‘, it seems the device nodes should be auto-generated and no need manually make ‘a few device nodes’, is it correct? Was the anomaly due to the copy from original nfs directory to the new one /opt? Or I missed something while building the file system?
QuoteReplyEditDelete
2010-08-12 12:02:41 Re: nfs failure in BF537 stamp with kernel 2009R1.1
Mike Frysinger (UNITED STATES)
Message: 92384
certain device nodes must exist in the rootfs irregardless of the /dev automatically being mounted & populated later. they must exist before userspace even executes as there is no way to open a device node for userspace if userspace hasnt been run to populate the initial /dev ...
QuoteReplyEditDelete
2010-08-12 12:40:07 Re: nfs failure in BF537 stamp with kernel 2009R1.1
garrett ding (UNITED STATES)
Message: 92385
I think I can proceed now. Appreciate your help, Mike.
QuoteReplyEditDelete
2010-08-12 13:05:29 Re: nfs failure in BF537 stamp with kernel 2009R1.1
Mike Frysinger (UNITED STATES)
Message: 92386
if you can think of wording to make the /dev thing clearer, i can update the docs. it sounds clear to me now, but that's probably because i wrote it.