Hi Matt, On 11/5/10, Matt Shao <[email protected]> wrote: > Hi Alan: > > Thank you for your kindly reply. > Last night, after send out the help mail, I have built busybox and try > to run busybox instead of android during boot. > the testing result is: > if I using following nfsroot: > nfsroot=10.67.174.128:/opt/nfsroot > busybox can run normally which seems the nfs works well. > but if I add 'v3,tcp' to the nfsroot like this: > nfsroot=10.67.174.128:/opt/nfsroot,v3,tcp > I got "kernel panic"!! > > Following is my board setting and log: > > U-Boot 2009.08-00165-g7d5aed8 (Sep 28 2010 - 10:33:27) > > CPU: Freescale i.MX51 family 3.0V at 800 MHz > mx51 pll1: 800MHz > mx51 pll2: 665MHz > mx51 pll3: 216MHz > ipg clock : 66500000Hz > ipg per clock : 665000000Hz > uart clock : 54000000Hz > cspi clock : 54000000Hz > axi_a clock : 166250000Hz > axi_b clock : 133000000Hz > emi_slow clock: 83125000Hz > ddr clock : 166250000Hz > esdhc clock : 216000000Hz > Board: MX51 BABBAGE 3.0 [POR] > Boot Device: MMC > I2C: ready > DRAM: 512 MB > MMC: FSL_ESDHC: 0, FSL_ESDHC: 1 > In: serial > Out: serial > Err: serial > PMIC Mode: SPI > Detecting HOME+POWER key for recovery ... > Net: FEC0 [PRIME] > Hit any key to stop autoboot: 1 0 > BBG U-Boot > ls t printenv > bootdelay=1 > baudrate=115200 > netdev=eth0 > ethprime=FEC0 > uboot_addr=0xa0000000 > uboot=u-boot.bin > kernel=uImage > bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; > bootm > prg_uboot=tftpboot ${loadaddr} ${uboot}; protect off ${uboot_addr} > 0xa003ffff; erase ${uboot_addr} 0xa003ffff; cp.b ${loadaddr} ${uboot_addr} > ${filesize}; setenv filesize; saveenv > bootcmd_SD=run bootargs_base bootargs_android;mmc read 0 ${loadaddr} 0x800 > 1800;mmc read 0 ${rd_loadaddr} 0x2000 0x258;bootm ${loadaddr} ${rd_loadaddr} > bootcmd_android_recovery=run bootargs_base bootargs_android_recovery;mmc > read 0 ${loadaddr} 0x800 0x1800;bootm > bootargs_android_recovery=setenv bootargs ${bootargs} init=/init > root=/dev/mmcblk0p4 rootfs=ext4 di1_primary > ethact=FEC0 > ethaddr=00:04:9f:00:ea:d3 > fec_addr=00:04:9f:00:ea:d3 > bootcmd_nfs=run bootargs_base bootargs_android bootargs_nfs; bootm > bootfile=uImage > serverip=10.67.174.128 > ipaddr=10.67.174.129 > other=dil_primary calibration > bootargs_nfs=setenv bootargs ${bootargs} ip=${nfsip} root=${rootdir} > nfsroot=${nfsroot} > bootcmd_SD1=run bootargs_base bootargs_android bootargs_SD > bootcmd_SD2=mmc read 0 ${loadaddr} 0x800 0x1800;mmc read 0 ${rd_loadaddr} > 0x2000 0x258;bootm ${loadaddr} ${rd_loadaddr} > bootargs_base=setenv bootargs console=ttymxc0,115200 > loadaddr=0x90800000 > rd_loadaddr=0x90B00000 > bootargs=console=ttymxc0,115200 init=/init androidboot.console=ttymxc0 > di1_primary calibration ip=dhcp > bootargs_SD=setenv bootargs ${bootargs} > bootcmd=run bootcmd_nfs > nfsip=10.67.174.129:10.67.174.128::255.255.255.0:lowiq-laptop:eth0:off > rootdir=/dev/nfs rw > rootpath=/opt/nfsroot > bootargs_android=setenv bootargs ${bootargs} init=/bin/sh > *nfsroot=10.67.174.128:/opt/nfsroot,v3,tcp* > stdin=serial > stdout=serial > stderr=serial > > Environment size: 1748/131068 bytes > BBG U-Boot > tftp 0x90800000 /opt/tftproot/uImage > Using FEC0 device > TFTP from server 10.67.174.128; our IP address is 10.67.174.129 > Filename '/opt/tftproot/uImage'. > Load address: 0x90800000 > Loading: * ################################################################# > ################################################################# > ################################################################# > ################################################################# > ################################################################# > ################################################################# > ################################################################# > ################################################################# > # > done > Bytes transferred = 2664372 (28a7b4 hex) > BBG U-Boot > run bot otcmd > ## Booting kernel from Legacy Image at 90800000 ... > Image Name: Android Linux Kernel > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2664308 Bytes = 2.5 MB > Load Address: 90008000 > Entry Point: 90008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > console handover: boot [ttymxc0] -> real [ttymxc0] > mxcintuart.1: ttymxc1 at MMIO 0x73fc0000 (irq = 32) is a Freescale i.MX > mxcintuart.2: ttymxc2 at MMIO 0x7000c000 (irq = 33) is a Freescale i.MX > brd: module loaded > loop: module loaded > pmem_adsp: 1 init > pmem_gpu: 3 init > FEC Ethernet Driver > fec_enet_mii_bus: probed > IEEE1588: ptp-timer is unavailable > PPP generic driver version 2.4.2 > mxc_dataflash spi1.1: at45db321d (1000 KBytes) pagesize 512 bytes (OTP) > Creating 2 MTD partitions on "mxc_dataflash": > 0x000000000000-0x000000100000 : "bootloader" > 0x000000100000-0x000000400000 : "kernel" > MXC MTD nand Driver 3.0 > i.MX GPMI NFC > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller > fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 > fsl-ehci fsl-ehci.0: irq 18, io base 0x73f80000 > fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00 > usb usb1: configuration #1 chosen from 1 choice > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 1 port detected > fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller > fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 > fsl-ehci fsl-ehci.1: irq 14, io base 0x73f80200 > fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00 > usb usb2: configuration #1 chosen from 1 choice > hub 2-0:1.0: USB hub found > hub 2-0:1.0: 1 port detected > Initializing USB Mass Storage driver... > usbcore: registered new interface driver usb-storage > USB Mass Storage support registered. > usbcore: registered new interface driver usbserial > USB Serial support registered for generic > usbcore: registered new interface driver usbserial_generic > usbserial: USB Serial Driver core > USB Serial support registered for GSM modem (1-port) > usbcore: registered new interface driver option > option: v0.7.2:USB Driver for GSM modems > ARC USBOTG Device Controller driver (1 August 2005) > mice: could not register psaux device, error: -16 > mice: PS/2 mouse device common for all mice > MXC keypad loaded > clk: Unable to get requested clock: kpp_clk > input: mxckpd as /devices/virtual/input/input0 > mc13892 rtc probe start > pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as rtc0 > mc13892 rtc probe succeed > i2c /dev entries driver > Linux video capture interface: v2.00 > i2c-adapter i2c-0: ACK not received > ov3640_write_reg:write reg error:reg=3012,val=80 > mxc_v4l2_output mxc_v4l2_output.0: Registered device video1 > usbcore: registered new interface driver uvcvideo > USB Video Class driver (v0.1.0) > APM Battery Driver > usb 2-1: new high speed USB device using fsl-ehci and address 2 > i2c-adapter i2c-1: ACK not received > MXC WatchDog Driver 2.0 > clk: Unable to get requested clock: wdog_clk > MXC Watchdog # 0 Timer: initial timeout 60 sec > device-mapper: uevent: version 1.0.3 > device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: > [email protected] > Bluetooth: Virtual HCI driver ver 1.3 > Bluetooth: Generic Bluetooth USB driver ver 0.5 > usbcore: registered new interface driver btusb > pmic_battery: probe of pmic_battery.1 failed with error -1 > VPU initialized > mxsdhci: MXC Secure Digital Host Controller Interface driver > mxsdhci: MXC SDHCI Controller Driver. > mmc0: SDHCI detect irq 128 irq 1 INTERNAL DMA > mxsdhci: MXC SDHCI Controller Driver. > mmc1: SDHCI detect irq 134 irq 2 INTERNAL DMA > Registered led device: pmic_ledsr > Registered led device: pmic_ledsg > Registered led device: pmic_ledsb > usb 2-1: configuration #1 chosen from 1 choice > hub 2-1:1.0: USB hub found > hub 2-1:1.0: 7 ports detected > usbcore: registered new interface driver usbhid > usbhid: v2.6:USB HID core driver > logger: created 64K log 'log_main' > logger: created 256K log 'log_events' > logger: created 64K log 'log_radio' > logger: created 64K log 'log_system' > Advanced Linux Sound Architecture Driver Version 1.0.20. > regulator: Unable to get requested regulator: VDDD > sgtl5000-i2c 1-000a: SGTL5000 revision 17 > mmc0: new SDHC card at address 9acd > mmcblk0: mmc0:9acd SD04G 3.69 GiB > mmcblk0: p1 p2 p3 < > No device for DAI imx-ssi-1-0 > No device for DAI imx-ssi-1-1 > No device for DAI imx-ssi-2-0 > No device for DAI imx-ssi-2-1 > p5 > DMA Sound Buffers Allocated:UseIram=1 buf->addr=1fff6000 buf->area=db856000 > size=24576 > DMA Sound Buffers Allocated:UseIram=1 buf->addr=a92c8000 buf->area=fa321000 > size=24576 > asoc: SGTL5000 <-> imx-ssi-2-0 mapping ok > p6 > p4 > ALSA device list: > #0: imx-3stack (SGTL5000) > TCP cubic registered > NET: Registered protocol family 10 > IPv6 over IPv4 tunneling driver > NET: Registered protocol family 17 > Bluetooth: L2CAP ver 2.13 > Bluetooth: L2CAP socket layer initialized > Bluetooth: SCO (Voice Link) ver 0.6 > Bluetooth: SCO socket layer initialized > Bluetooth: RFCOMM TTY layer initialized > Bluetooth: RFCOMM socket layer initialized > Bluetooth: RFCOMM ver 1.11 > Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > Bluetooth: BNEP filters: protocol multicast > Bluetooth: HIDP (Human Interface Emulation) ver 1.2 > hcd_bus_suspend > ehci_bus_suspend > OTG wakeup irq is enabled > OTG phy lowpower enable > USB Host suspended > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > <6>DVI device plug-out > VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 > regulator_init_complete: disabling GPO4 > regulator_init_complete: disabling GPO3 > regulator_init_complete: disabling GPO2 > regulator_init_complete: disabling GPO1 > regulator_init_complete: disabling VGEN1 > regulator_init_complete: disabling VCAM > regulator_init_complete: disabling VAUDIO > regulator_init_complete: disabling VSD > regulator_init_complete: disabling SWBST > android init > android_probe pdata: c0686a80 > android_bind > mass_storage_function_add > android_usb gadget: Number of LUNs=3 > adb_function_add > android_usb gadget: android_usb ready > Suspend udc for OTG auto detect > OTG wakeup irq is enabled > udc resume > OTG wakeup irq disable > OTG phy lowpower disable > OTG wakeup irq is enabled > OTG phy lowpower enable > dr_controller_run: udc enter low power mode > USB Gadget resumed > fsl-usb2-udc: bind to driver android_usb > input: mxc_ts as /devices/virtual/input/input1 > mxc input touchscreen loaded > pmic_rtc pmic_rtc.1: setting system clock to 1970-01-01 11:31:14 UTC (41474) > eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1) > IP-Config: Complete: > device=eth0, addr=10.67.174.129, mask=255.255.255.0, > gw=255.255.255.255, > host=lowiq-laptop, domain=, nis-domain=(none), > bootserver=10.67.174.128, rootserver=10.67.174.128, *rootpath= // > should rootpath be NULL?* > Looking up port of RPC 100003/3 on 10.67.174.128 > usb 2-1.6: new high speed USB device using fsl-ehci and address 3 > usb 2-1.6: configuration #1 chosen from 1 choice > scsi0 : SCSI emulation for USB Mass Storage devices > PHY: 0:00 - Link is Up - 100/Full > Looking up port of RPC 100005/3 on 10.67.174.128 > VFS: Mounted root (nfs filesystem) on device 0:11. > Freeing init memory: 176K > Warning: unable to open an initial console. > *Kernel panic - not syncing: Attempted to kill init! // if I do NOT add > 'v3,tcp' to the nfsroot, I will get busybox shell successfully* > otg is idle for some times,so we close the clock 9201120 > close otg clk ok > > Any comment? Thanks a lot! >
Strange, here when I didn't use this parameter I receiver server timeout. Did you try to use a cross-over cable connecting your computer and your board? It could work. Just remember to use fixed ip instead dhcp (i'm supposing you don't have dhcp server installed in your computer). Best Regards, Alan -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
