Hi Rams, Please check if you have given the executable permission to init.
For Androd file system give all the permission RWX and check if this error is seen. Regards, Subha On Thu, Aug 4, 2011 at 4:26 PM, Rams <[email protected]> wrote: > Dear ALl > I am trying to port android 2.6.32 kernel to OMAP 3430 (ZOOM2 > Board).init is not executing. > Can anyone please help > Log > > ## Booting image at > 81c00000 ... > Image Name: > Linux-2.6.32.9 > Image Type: ARM Linux Kernel Image > (uncompressed) > Data Size: 2601168 Bytes = 2.5 > MB > Load Address: > 80008000 > Entry Point: > 80008000 > Verifying Checksum ... > OK > OK > > Starting > kernel ... > > Linux version 2.6.32.9 (vani@vani-Veriton-Series) (gcc version 4.3.2 > (Sourcery 1 > CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), > cr=10c53c7f > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction > cache > Machine: OMAP Zoom2 > board > Memory policy: ECC disabled, Data cache > writeback > DIE ID: > 775C0000000000000156087C04016011 > OMAP3630 ES1.0 (l2cache iva sgx neon isp > 192mhz_clk ) > omap_sam_base (VA) == > 0xfe400000 > omap_sram_start (PA) == > 0x40200000 > omap_sram_size (SIZE) == > 0x10000 > SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: > 0x100000 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: > 65024 > Kernel command line: console=ttyO3,115200n8 root=/dev/mmcblk0p2 rw > rootdelay=1 M > PID hash table entries: 1024 (order: 0, 4096 > bytes) > Dentry cache hash table entries: 32768 (order: 5, 131072 > bytes) > Inode-cache hash table entries: 16384 (order: 4, 65536 > bytes) > Memory: 256MB = 256MB > total > Memory: 247424KB available (4736K code, 969K data, 180K init, 0K > highmem) > Virtual kernel memory > layout: > vector : 0xffff0000 - 0xffff1000 ( 4 > kB) > fixmap : 0xfff00000 - 0xfffe0000 ( 896 > kB) > vmalloc : 0xd0800000 - 0xf8000000 ( 632 > MB) > lowmem : 0xc0000000 - 0xd0000000 ( 256 > MB) > modules : 0xbf000000 - 0xc0000000 ( 16 > MB) > .init : 0xc0008000 - 0xc0035000 ( 180 > kB) > .text : 0xc0035000 - 0xc04d5000 (4736 > kB) > .data : 0xc04fc000 - 0xc053c890 ( 259 > kB) > Hierarchical RCU > implementation. > NR_IRQS: > 402 > IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 > interrupts > Total of 96 interrupts on 1 active > controller > clock: init parent: could not find regval 0 for clock > dpll2_fck > clock: Could not find fieldval 0 for clock dpll2_fck parent > core_ck > Clocking rate (Crystal/Core/MPU): 26.0/332/500 > MHz > Reprogramming SDRC clock to 332000000 > Hz > clock: Could not find fieldval 0 for clock dpll2_fck parent > core_ck > GPMC revision > 5.0 > OMAP GPIO hardware version > 2.5 > OMAP clockevent source: GPTIMER1 at 32768 > Hz > Calibrating delay loop... 499.92 BogoMIPS > (lpj=1949696) > Mount-cache hash table entries: > 512 > CPU: Testing write buffer coherency: > ok > regulator: core version > 0.5 > NET: Registered protocol family > 16 > OMAP DMA hardware revision > 5.0 > bio: create slab <bio-0> at > 0 > SCSI subsystem > initialized > usbcore: registered new interface driver > usbfs > usbcore: registered new interface driver > hub > usbcore: registered new device driver > usb > i2c_omap i2c_omap.1: bus 1 rev4.0 at 100 > kHz > twl4030: PIH (irq 7) chaining IRQs > 368..375 > twl4030: power (irq 373) chaining IRQs > 376..383 > twl4030: gpio (irq 368) chaining IRQs > 384..401 > regulator: VUSB1V5: 1500 mV normal > standby > regulator: VUSB1V8: 1800 mV normal > standby > regulator: VUSB3V1: 3100 mV normal > standby > twl4030_usb twl4030_usb: Initialized TWL4030 USB > module > regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal > standby > regulator: VDAC: 1800 mV normal > standby > regulator: VPLL2: 1800 mV normal > standby > regulator: VMMC2: 1850 mV normal > standby > regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal > standby > i2c_omap i2c_omap.2: bus 2 rev4.0 at 100 > kHz > i2c_omap i2c_omap.3: bus 3 rev4.0 at 400 > kHz > Sangoma WANPIPE Router v1.1 (c) 1995-2000 Sangoma Technologies > Inc. > Bluetooth: Core ver > 2.15 > NET: Registered protocol family > 31 > Bluetooth: HCI device and connection manager > initialized > Bluetooth: HCI socket layer > initialized > Switching to clocksource > 32k_counter > musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), > debug=0 > musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ > 92 > NET: Registered protocol family > 2 > IP route cache hash table entries: 2048 (order: 1, 8192 > bytes) > TCP established hash table entries: 8192 (order: 4, 65536 > bytes) > TCP bind hash table entries: 8192 (order: 3, 32768 > bytes) > TCP: Hash tables configured (established 8192 bind > 8192) > TCP reno > registered > NET: Registered protocol family > 1 > RPC: Registered udp transport > module. > RPC: Registered tcp transport > module. > RPC: Registered tcp NFSv4.1 backchannel transport > module. > dspbridge_init: 600000 bytes @ > 80800000 > zoom2_wifi_init: > start > omap-iommu omap-iommu.0: isp > registered > iovmm-omap initialized isp, major: 253, base-minor: > 0 > NetWinder Floating Point Emulator V0.97 (double > precision) > ashmem: > initialized > VFS: Disk quotas > dquot_6.5.2 > Dquot-cache hash table entries: 1024 (order 0, 4096 > bytes) > JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, > Inc. > yaffs Jul 22 2011 10:15:45 > Installing. > msgmni has been set to > 483 > alg: No test for stdrng > (krng) > io scheduler noop > registered > io scheduler anticipatory registered > (default) > io scheduler deadline > registered > io scheduler cfq > registered > omap-hsuart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP > UART0 > omap-hsuart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP > UART1 > omap-hsuart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP > UART2 > omap-hsuart.3: ttyO3 at MMIO 0x10000000 (irq = 262) is a OMAP > UART3 > console [ttyO3] > enabled > brd: module > loaded > loop: module > loaded > omap2-nand driver > initializing > smsc911x: Driver version > 2008-10-21. > smsc911x-mdio: > probed > eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, > irq=-1) > net eth0: MAC Address: 00:08:ee: > 03:47:6f > input: twl4030-keypad as /devices/platform/i2c_omap.1/i2c-1/1-004a/ > twl4030_keyp0 > synaptics_ts_probe: Product Major Version > 1 > synaptics_ts_probe: Product Minor Version > 5 > synaptics_ts_probe: product property > 2 > synaptics_ts_probe: device control > 81 > synaptics_ts_probe: interrupt enable > 3 > synaptics_ts_probe: 0xe0: 1 1 1 2 1 5 0 > 0 > synaptics_ts_probe: Sensor properties > 601 > synaptics_ts_probe: max_x 7515, max_y > 4667 > synaptics_ts_probe: inactive_x 0 0, inactive_y 0 > 0 > synaptics_ts_probe: snap_x 0-0 0-0, snap_y 0-0 > 0-0 > input: synaptics-rmi-touchscreen as /devices/virtual/input/ > input1 > synaptics_ts_probe: Start touchscreen synaptics-rmi-touchscreen in > interrupt moe > using rtc device, twl_rtc, for > alarms > twl_rtc twl_rtc: rtc core: registered twl_rtc as > rtc0 > i2c /dev entries > driver > Driver for 1-wire Dallas network > protocol. > OMAP Watchdog Timer Rev 0x31: initial timeout 60 > sec > Bluetooth: HCI UART driver ver > 2.2 > Bluetooth: HCI H4 protocol > initialized > Bluetooth: HCILL protocol > initialized > cpuidle: using governor > ladder > cpuidle: using governor > menu > 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.21. > No device for DAI > twl4030 > No device for DAI twl4030 > Voice > No device for DAI twl4030 > Clock > No device for DAI omap-mcbsp- > dai-0 > No device for DAI omap-mcbsp- > dai-1 > No device for DAI omap-mcbsp- > dai-2 > No device for DAI omap-mcbsp- > dai-3 > No device for DAI omap-mcbsp- > dai-4 > Zoom2 SoC > init > set mux for group mode = > OMAP_MCBSP2_SLAVE > No device for DAI > null > set mux for group mode = > OMAP_MCBSP4_SLAVE > TWL4030 Audio Codec > init > asoc: twl4030 <-> omap-mcbsp-dai-0 mapping > ok > asoc: twl4030 Voice <-> omap-mcbsp-dai-1 mapping > ok > asoc: null <-> omap-mcbsp-dai-1 mapping > ok > asoc: null <-> omap-mcbsp-dai-2 mapping > ok > ALSA device > list: > #0: Zoom2 > (twl4030) > oprofile: using > timer > nf_conntrack version 0.5.0 (3869 buckets, 15476 > max) > ip_tables: (C) 2000-2006 Netfilter Core > Team > arp_tables: (C) 2002 David S. > Miller > TCP cubic > registered > Initializing XFRM netlink > socket > NET: Registered protocol family > 17 > NET: Registered protocol family > 15 > Bluetooth: L2CAP ver > 2.14 > 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: HIDP (Human Interface Emulation) ver > 1.2 > Power Management for TI > OMAP3. > sr1_opp_margin[1]=37500 > sr1_opp_margin[2]=37500 > sr1_opp_margin[3]=37500 > sr1_opp_margin[4]=62500 > steps added, volt will berecaliberated > automatically > SR2:Fused Nvalues for VDD2OPP1 > 11193009 > SmartReflex driver > initialized > VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev > 3 > twl_rtc twl_rtc: setting system clock to 2000-02-02 06:58:44 UTC > (949474724) > Waiting 1sec before mounting root > device... > mmc0: host does not support reading read-only switch. assuming write- > enable. > mmc0: new high speed SD card at address > 0007 > mmcblk0: mmc0:0007 SU02G 1.83 > GiB > mmcblk0: p1 > p2 > kjournald starting. Commit interval 5 > seconds > EXT3 FS on mmcblk0p2, internal > journal > EXT3-fs: recovery > complete. > EXT3-fs: mounted filesystem with writeback data > mode. > VFS: Mounted root (ext3 filesystem) on device > 179:2. > Freeing init memory: > 180K > Warning: unable to open an initial > console. > > > ----- > > We have observed it is hanging while creating init > if (execute_command) { > run_init_process(execute_command); > printk(KERN_WARNING "Failed to execute %s. Attempting > " > "defaults...\n", > execute_command); > } > > execute_command is /init > > Please advise > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-kernel -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
