Closed kangear closed 10 years ago
这个用SuperBoot来启动NFS Android4 文件系统也会有这个问题,从启动可以看出Android已经挂载上了,只是在在启动到69.25087后出现了问题,网上搜集资料,很可能是android文件系统中启动配置文件中对开发板ip进行了重置,导致的问题。
这个虽然已经不算是Bootloader的问题了,但是记录下来也是有意义的。
挂载部分NFS文件系统(非根文件系统)也出现了这个BUG,但是不影响使用。原来应该是一样的原理。
busybox mount -t nfs -o nolock 192.168.8.104:/work /work
/work # ls
[ 75.947278] BUG: sleeping function called from invalid context at mm/slub.c:847
[ 75.947349] in_atomic(): 1, irqs_disabled(): 0, pid: 2319, name: ndroid.calendar
[ 75.947442]
以前一直是没有怎么做android开发,就把嵌入式linux的一些经验拿到Android上来,比如这次的nfs,工作的时间长了,现在认识到在Android中是一个相当鸡肋的功能。Android提供的adb sync一键同步PC上的文件。甩nfs几条街。
android NFS如下操作方法: 1.chmod 777 /work/a8/android-4.0.3_r1/rootfs_dir
2、重启服务 $sudo /etc/init.d/portmap restart $sudo /etc/init.d/nfs-kernel-server restart
3.setenv root=/dev/nfs nfsroot=192.168.1.229:/work/a8/android-4.0.3_r1/rootfs_dir ip=192.168.1.230:192.168.1.229:192.168.1.1:255.255.255.0::eth0:off rw console=ttySAC0,115200 init=/linuxrc androidboot.console=ttySAC0 mem=512M androidboot.console=s3c2410_serial0 mem=512M skipcali=y ctp=2
启动过程: [ 3.156601] s5p-tvout s5p-tvout: hpd status is cable removed [ 3.184270] dm9000 dm9000: eth0: link down [ 3.184447] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 65.403108] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 65.418609] dm9000 dm9000: eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 65.418820] IP-Config: Complete: [ 65.418850] device=eth0, addr=192.168.1.230, mask=255.255.255.0, gw=192.168.1.1, [ 65.418921] host=192.168.1.230, domain=, nis-domain=(none), [ 65.419923] bootserver=192.168.1.229, rootserver=192.168.1.229, rootpath= [ 65.427728] Freeing init memory: 1456K 192.168.1.229 /work/a8/android-4.0.3_r1/rootfs_dir 192.168.1.230 192.168.1.229 192.168.1.1 255.255.255.0 eth0 off [ 65.588592] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead. [ 65.721276] init: cannot open '/initlogo.rle' [ 67.549250] init: cannot find '/system/bin/zte_mf210_dial', disabling 'pppd_gprs' [ 67.553061] BUG: sleeping function called from invalid context at mm/slub.c:847 [ 67.553127] in_atomic(): 1, irqs_disabled(): 0, pid: 1504, name: init [ 67.553211] from
[ 67.557187] from
[ 67.565929] from
[ 67.574677] from
[ 67.583695] from
[ 67.592787] from
[ 67.601974] from
[ 67.611444] from
[ 67.620692] from
[ 67.629273] from
[ 67.638718] from
[ 67.648424] from
[ 67.657867] from
[ 67.667399] from
[ 67.676325] from
[ 67.684990] from
[ 67.693136] from
[ 67.701023] from
[ 67.708987] Exception stack(0xd895fee8 to 0xd895ff30)
[ 67.714014] fee0: 00027e36 00000017 c03301e8 20000013 ffffffff d895ff64
[ 67.722162] ff00: d820b000 00000000 00027e36 20000113 00000000 beae6d34 00027e36 d895ff30
[ 67.730303] ff20: c0179b20 c0179b24 60000113 ffffffff
[ 67.735336] from
[ 67.743315] from
[ 68.377319] init: service 'console' requires console
[ 68.377504] android_usb: already disabled
[ 68.377795] adb_bind_config
[ 68.385981] android_work: did not send uevent (0 0 (null))
[ 68.520431] adb_open
[ 68.655133] android_work: sent uevent USB_STATE=CONNECTED
[ 68.750553] android_usb gadget: high speed config #1: android
[ 68.759647] android_work: sent uevent USB_STATE=CONFIGURED
[ 69.250879] PVR_K:(Warning): SysFinalise: Version string: SGX540 S5PC110 [543, drivers/gpu/pvr/s5pc110/sysconfig.c]
[ 112.078779] nfs: server 192.168.1.229 not responding, still trying
[ 112.078868] nfs: server 192.168.1.229 not responding, still trying
[ 112.078946] nfs: server 192.168.1.229 not responding, still trying
[ 112.079022] nfs: server 192.168.1.229 not responding, still trying
[ 112.081162] nfs: server 192.168.1.229 not responding, still trying
[ 112.087312] nfs: server 192.168.1.229 not responding, still trying
[ 140.906887] nfs: server 192.168.1.229 not responding, still trying