HI, In my case, i am not able to get bash prompt of linux... it is crashing before...
On Sun, Jan 23, 2011 at 8:19 AM, kiran <[email protected]> wrote: > During Booting , once the Bash Prompt comes on the serial terminal you can > quickly logcat & which will give more information about why it is crashing. > Regards > Kiran > > On Sat, Jan 22, 2011 at 2:22 PM, hardik patel <[email protected]> wrote: >> >> Which quick option you are telling about ... I am not sure that dsp is >> causing the issue .... how to debug the init process ... how can we >> identify main problem ? >> >> On Sat, Jan 22, 2011 at 1:53 PM, kiran <[email protected]> wrote: >> > Hi All >> > Dsp Interface part present on android ginger bread is still for froyo >> > kernel, one quick option would be to use the android froyo kernel >> > itself. >> > Regards >> > Kiran >> > >> > On Sat, Jan 22, 2011 at 1:45 PM, hardik patel <[email protected]> >> > wrote: >> >> >> >> Hi, >> >> >> >> After comment dsp related service still we are facing issue. it again >> >> crash at while loading file system. >> >> >> >> To download kernel we have use below path : >> >> >> >> http://android.git.kernel.org/?p=kernel/common.git;a=summary >> >> >> >> One thing i notice if i download 2.6.35 kernel from >> >> "http://android.git.kernel.org/?p=kernel/linux-2.6.git;a=summary"; link >> >> then i am not able to find kernel with Android compatible means i am >> >> not able to find android linux kernel specific changes (Ex Ashmem and >> >> Wakelock etc... ) Why it so i am not able to understand that .... >> >> >> >> Do not use kernel from linux2.6.git path .... Other thing that i >> >> observed that if i download kernel form >> >> "http://git.omapzoom.org/?p=kernel/omap.git;a=summary"; git then source >> >> is different then from " >> >> http://android.git.kernel.org/?p=kernel/common.git;a=summary"; tree >> >> ,... Specifically i have seen OMAP 3630 zoom3 related change is huge >> >> why this much difference between this kernel .... if any one can help >> >> to identify this difference then it is good ... >> >> >> >> I am using froyo Android file system not gingerbread ...because we are >> >> still compiling gingerbread (Android 2.3) on 64 bit setup ... we are >> >> facing lot of issue while building filesystem .... we are not getting >> >> vendot directory while check out gingerbread code ... how can we get >> >> this ? we want ti folder... >> >> >> >> >> >> On Thu, Jan 20, 2011 at 1:40 PM, Alok <[email protected]> wrote: >> >> > Hi Hardik, >> >> > >> >> > We are also going to start this activity. >> >> > Could you please provide few information >> >> > >> >> > Did you resolve by not starting dsp related service? >> >> > Is it feasible porting android 2.6.35 on zoom3? >> >> > Did you download the kernel code from google git repository? where >> >> > from u downloaded the code? >> >> > Does ti provide any support for 2.6.35 kernel for android? >> >> > >> >> > >> >> > >> >> > Regards, >> >> > -Alok >> >> > >> >> > On Jan 19, 2:05 pm, Deva R <[email protected]> wrote: >> >> >> ><5>init: process 'baseimage', pid 782 exited >> >> >> >init: process 'baseimage', pid 782 exited >> >> >> >> >> >> try basic bootup first, without dsp support.. >> >> >> probably dsp firmware is not present, or dsp bridge needs fix/patch >> >> >> for GB migration. >> >> >> >> >> >> <comment below service> >> >> >> # load DSP firmware >> >> >> service baseimage /system/bin/cexec.out >> >> >> /system/lib/dsp/baseimage.dof >> >> >> user root >> >> >> group audio >> >> >> oneshot >> >> >> >> >> >> On Tue, Jan 18, 2011 at 10:23 PM, hardik patel <[email protected]> >> >> >> wrote: >> >> >> > Hi, >> >> >> >> >> >> > I am working on OMAP 3630 zoom3 board. I am doing kernel 2.6.35 >> >> >> > porting for this board for Ginger bread version. While booting my >> >> >> > Kernel uImage on board i got carsh on mediaserver service see >> >> >> > below >> >> >> > log. >> >> >> >> >> >> > MMC1 Initalization OK >> >> >> >> >> >> > 2954888 bytes read >> >> >> > ## Booting image at 81c00000 ... >> >> >> > Image Name: Linux-2.6.35.7 >> >> >> > Image Type: ARM Linux Kernel Image (uncompressed) >> >> >> > Data Size: 2954824 Bytes = 2.8 MB >> >> >> > Load Address: 80008000 >> >> >> > Entry Point: 80008000 >> >> >> > Verifying Checksum ... OK >> >> >> > OK >> >> >> >> >> >> > Starting kernel ... >> >> >> >> >> >> > Uncompressing Linux... done, booting the kernel. >> >> >> > <6>Initializing cgroup subsys cpu >> >> >> > <5>Linux version 2.6.35.7 (user@user-desktop) (gcc version 4.3.2 >> >> >> > (Sourcery G++ Lite 2008q3-72) ) #1 PREEMPT Mon Jan 17 11:23:03 IST >> >> >> > 2011 >> >> >> > CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f >> >> >> > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction >> >> >> > cache >> >> >> > Machine: OMAP Zoom3 board >> >> >> > Memory policy: ECC disabled, Data cache writeback >> >> >> > <7>On node 0 totalpages: 131072 >> >> >> > <7>free_area_init_node: node 0, pgdat c05c0f60, node_mem_map >> >> >> > c0699000 >> >> >> > <7> Normal zone: 1024 pages used for memmap >> >> >> > <7> Normal zone: 0 pages reserved >> >> >> > <7> Normal zone: 130048 pages, LIFO batch:31 >> >> >> > <6>OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk ) >> >> >> > <6>SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000 >> >> >> > <6>Reserving 4194304 bytes SDRAM for VRAM >> >> >> > Built 1 zonelists in Zone order, mobility grouping on. Total >> >> >> > pages: >> >> >> > 130048 >> >> >> > <5>Kernel command line: androidboot.console=ttyS0 >> >> >> > console=ttyS0,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1 >> >> >> > mem=512M >> >> >> > init=/init videoout=omap24xxvout omap_vout.video1_numbuffers=6 >> >> >> > omap_vout.vid1_static_vrfb_alloc=y omapfb.vram="0:4M" >> >> >> > user_debug=31 >> >> >> > <6>PID hash table entries: 2048 (order: 1, 8192 bytes) >> >> >> > <6>Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) >> >> >> > <6>Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) >> >> >> > <6>Memory: 512MB = 512MB total >> >> >> > <5>Memory: 508952k/508952k available, 15336k reserved, 0K highmem >> >> >> > <5>Virtual kernel memory layout: >> >> >> > vector : 0xffff0000 - 0xffff1000 ( 4 kB) >> >> >> > fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) >> >> >> > DMA : 0xffc00000 - 0xffe00000 ( 2 MB) >> >> >> > vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB) >> >> >> > lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) >> >> >> > pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) >> >> >> > modules : 0xbf000000 - 0xbfe00000 ( 14 MB) >> >> >> > .init : 0xc0008000 - 0xc0038000 ( 192 kB) >> >> >> > .text : 0xc0038000 - 0xc0552000 (5224 kB) >> >> >> > .data : 0xc057a000 - 0xc05c1860 ( 287 kB) >> >> >> > <6>Hierarchical RCU implementation. >> >> >> > <6> RCU-based detection of stalled CPUs is disabled. >> >> >> > <6> Verbose stalled-CPUs detection is disabled. >> >> >> > <6>NR_IRQS:402 >> >> >> > <6>Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz >> >> >> > <3> (null): Could not get uart4_ick >> >> >> > <3> (null): Could not get uart4_fck >> >> >> > <4>omap_hwmod: l3_hwmod: cannot be enabled (3) >> >> >> > <4>omap_hwmod: l4_core_hwmod: cannot be enabled (3) >> >> >> > <4>omap_hwmod: l4_per_hwmod: cannot be enabled (3) >> >> >> > <4>omap_hwmod: l4_wkup_hwmod: cannot be enabled (3) >> >> >> > <6>Reprogramming SDRC clock to 400000000 Hz >> >> >> > <6>GPMC revision 5.0 >> >> >> > <6>IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 >> >> >> > interrupts >> >> >> > <6>Total of 96 interrupts on 1 active controller >> >> >> > <6>OMAP GPIO hardware version 2.5 >> >> >> > <6>OMAP clockevent source: GPTIMER1 at 32768 Hz >> >> >> > Console: colour dummy device 80x30 >> >> >> > <6>Calibrating delay loop... <c>597.64 BogoMIPS (lpj=2334720) >> >> >> > <6>pid_max: default: 32768 minimum: 301 >> >> >> > Mount-cache hash table entries: 512 >> >> >> > <6>Initializing cgroup subsys debug >> >> >> > <6>Initializing cgroup subsys cpuacct >> >> >> > <6>Initializing cgroup subsys freezer >> >> >> > <6>CPU: Testing write buffer coherency: ok >> >> >> > <6>regulator: core version 0.5 >> >> >> > <6>NET: Registered protocol family 16 >> >> >> > <7>mux: Setting signal i2c2_scl.i2c2_scl 0x0118 -> 0x0100 >> >> >> > <7>mux: Setting signal i2c2_sda.i2c2_sda 0x0118 -> 0x0100 >> >> >> > <7>mux: Setting signal i2c3_scl.i2c3_scl 0x0118 -> 0x0100 >> >> >> > <7>mux: Setting signal i2c3_sda.i2c3_sda 0x0118 -> 0x0100 >> >> >> > <7>mux: Setting signal sys_nirq.sys_nirq 0x0118 -> 0x4118 >> >> >> > <7>mux: Setting signal gpmc_wait2.gpio64 0x0118 -> 0x0004 >> >> >> > <6>OMAP DMA hardware revision 5.0 >> >> >> > bio: create slab <bio-0> at 0 >> >> >> > <5>SCSI subsystem initialized >> >> >> > <6>usbcore: registered new interface driver usbfs >> >> >> > <6>usbcore: registered new interface driver hub >> >> >> > <6>usbcore: registered new device driver usb >> >> >> > <6>i2c_omap i2c_omap.1: bus 1 rev4.0 at 2400 kHz >> >> >> > <6>twl4030: PIH (irq 7) chaining IRQs 368..375 >> >> >> > <6>twl4030: power (irq 373) chaining IRQs 376..383 >> >> >> > <6>twl4030: gpio (irq 368)nit: command 'chmod' r=-2 >> >> >> > init: command 'chown' r=-2 >> >> >> > <6>init: command 'chmod' r=-2 >> >> >> > init: command 'chmod' r=-2 >> >> >> > <6>init: command 'chown' r=-2 >> >> >> > init: command 'chown' r=-2 >> >> >> > <6>init: command 'write' r=-2 >> >> >> > init: command 'write' r=-2 >> >> >> > <6>init: Created socket '/dev/socket/property_service' with mode >> >> >> > '666', user '0', group '0' >> >> >> > init: Created socket '/dev/socket/property_service' with mode >> >> >> > '666', >> >> >> > user '0', group '0' >> >> >> > <6>init: processing action 0x2c3c0 (boot) >> >> >> > init: processing action 0x2c3c0 (boot) >> >> >> > <6>init: command 'ifup' r=0 >> >> >> > init: command 'ifup' r=0 >> >> >> > <6>init: command 'chmod' r=-2 >> >> >> > init: command 'chmod' r=-2 >> >> >> > <5>init: starting 'console' >> >> >> > init: starting 'console' >> >> >> > <3>init: cannot find '/system/bin/pvrsrvinit', disabling >> >> >> > 'pvrsrvinit' >> >> >> > init: cannot find '/system/bin/pvrsrvinit', disabling 'pvrsrvinit' >> >> >> > <5>init: starting 'servicemanager' >> >> >> > init: starting 'servicemanager' >> >> >> > <5>init: starting 'vold' >> >> >> > init: starting 'vold' >> >> >> > <5>init: starting 'netd' >> >> >> > init: starting 'netd' >> >> >> > <6>init: Created socket '/dev/socket/vold' with mode '660', user >> >> >> > '0', >> >> >> > group '1009' >> >> >> > init: Created socket '/dev/socket/vold' with mode '660', user '0', >> >> >> > group '1009' >> >> >> > <6>init: Created socket '/dev/socket/netd' with mode '660', user >> >> >> > '0', >> >> >> > group '1000' >> >> >> > init: Created socket '/dev/socket/netd' with mode '660', user '0', >> >> >> > group '1000' >> >> >> > <5>init: starting 'debuggerd' >> >> >> > init: starting 'debuggerd' >> >> >> > <5>init: starting 'ril-daemon' >> >> >> > init: starting 'ril-daemon' >> >> >> > <5>init: starting 'zygote' >> >> >> > init: starting 'zygote' >> >> >> > <6>init: Created socket '/dev/socket/rild-debug' with mode '660', >> >> >> > user >> >> >> > '1001', group '1000' >> >> >> > init: Created socket '/dev/socket/rild-debug' with mode '660', >> >> >> > user >> >> >> > '1001', group '1000' >> >> >> > <6>init: Created socket '/dev/socket/zygote' with mode '666', user >> >> >> > '0', group '0' >> >> >> > init: Created socket '/dev/socket/zygote' with mode '666', user >> >> >> > '0', >> >> >> > group '0' >> >> >> > <6>init: Created socket '/dev/socket/rild' with mode '660', user >> >> >> > '0', >> >> >> > group '1001' >> >> >> > init: Created socket '/dev/socket/rild' with mode '660', user '0', >> >> >> > group '1001' >> >> >> > <5>init: starting 'media' >> >> >> > init: starting 'media' >> >> >> > <5>init: starting 'dbus' >> >> >> > init: starting 'dbus' >> >> >> > <5>init: starting 'installd' >> >> >> > init: starting 'installd' >> >> >> > <6>init: Created socket '/dev/socket/dbus' with mode '660', user >> >> >> > '1002', group '1002' >> >> >> > init: Created socket '/dev/socket/dbus' with mode '660', user >> >> >> > '1002', >> >> >> > group '1002' >> >> >> > <3>init: cannot find '/system/etc/install-recovery.sh', disabling >> >> >> > 'flash_recovery' >> >> >> > init: cannot find '/system/etc/install-recovery.sh', disabling >> >> >> > 'flash_recovery' >> >> >> > <6>init: Created socket '/dev/socket/installd' with mode '600', >> >> >> > user >> >> >> > '1000', group '1000' >> >> >> > init: Created socket '/dev/socket/installd' with mode '600', user >> >> >> > '1000', group '1000' >> >> >> > <5>init: starting 'keystore' >> >> >> > init: starting 'keystore' >> >> >> > <5>init: starting 'baseimage' >> >> >> > init: starting 'baseimage' >> >> >> > <6>init: Created socket '/dev/socket/keystore' with mode '666', >> >> >> > user >> >> >> > '0', group '0' >> >> >> > init: Created socket '/dev/socket/keystore' with mode '666', user >> >> >> > '0', group '0' >> >> >> > <5>init: starting 'mux' >> >> >> > init: starting 'mux' >> >> >> > <3>init: cannot find '/system/bin/fw3a_core', disabling 'fw3a' >> >> >> > init: cannot find '/system/bin/fw3a_core', disabling 'fw3a' >> >> >> > <3>init: cannot find '/system/bin/playmp3', disabling 'bootsound' >> >> >> > init: cannot find '/system/bin/playmp3', disabling 'bootsound' >> >> >> > <5>init: starting 'uim' >> >> >> > init: starting 'uim' >> >> >> > <6>init: command 'class_start' r=0 >> >> >> > init: command 'class_start' r=0 >> >> >> > <6>init: processing action 0x2d3d8 >> >> >> > (property:persist.service.adb.enable=1) >> >> >> > init: processing action 0x2d3d8 >> >> >> > (property:persist.service.adb.enable=1) >> >> >> > <5>init: starting 'adbd' >> >> >> > init: starting 'adbd' >> >> >> > <6>init: command 'start' r=0 >> >> >> > init: command 'start' r=0 >> >> >> > # <6>init: waitpid returned pid 782, status = 0000ff00 >> >> >> > init: waitpid returned pid 782, status = 0000ff00 >> >> >> > <5>init: process 'baseimage', pid 782 exited >> >> >> > init: process 'baseimage', pid 782 exited >> >> >> > AT >> >> >> > <6>init: waitpid returned pid 784, status = 0000ff00 >> >> >> > init: waitpid returned pid 784, status = 0000ff00 >> >> >> > <5>init: process 'uim', pid 784 exited >> >> >> > init: process 'uim', pid 784 exited >> >> >> > <6>warning: `rild' uses 32-bit capabilities (legacy support in >> >> >> > use) >> >> >> > warning: `rild' uses 32-bit capabilities (legacy support in use) >> >> >> > <6>init: waitpid returned pid 776, status = 0000ff00 >> >> >> > init: waitpid returned pid 776, status = 0000ff00 >> >> >> > <5>init: process 'ril-daemon', pid 776 exited >> >> >> > init: process 'ril-daemon', pid 776 exited >> >> >> > <5>init: process 'ril-daemon' killing any children in process >> >> >> > group >> >> >> > init: process 'ril-daemon' killing any children in process group >> >> >> > ù à @ùù ïà òùAT >> >> >> > <7>mediaserver: unhandled page fault (11) at 0x00000010, code >> >> >> > 0x017 >> >> >> > <1>pgd = dff60000 >> >> >> > pgd = dff60000 >> >> >> > <1>[00000010] *pgd=9ff8a031[00000010] *pgd=9ff8a031, >> >> >> > *pte=00000000, >> >> >> > *pte=00000000, *ppte=00000000, *ppte=00000000 >> >> >> >> >> >> > Pid: 778, comm: mediaserver >> >> >> > Pid: 778, >> >> >> >> >> >> ... >> >> >> >> >> >> read more » >> >> > >> >> > -- >> >> > unsubscribe: [email protected] >> >> > website: http://groups.google.com/group/android-porting >> >> > >> >> >> >> >> >> >> >> -- >> >> Regards, >> >> Hardik >> >> >> >> "If you are doing what you have always been doing then expect what you >> >> have always been getting." >> >> >> >> -- >> >> unsubscribe: [email protected] >> >> website: http://groups.google.com/group/android-porting >> > >> > >> > >> > -- >> > Regards >> > Kiran >> > >> >> >> >> -- >> Regards, >> Hardik >> >> "If you are doing what you have always been doing then expect what you >> have always been getting." >> >> -- >> unsubscribe: [email protected] >> website: http://groups.google.com/group/android-porting > > > > -- > Regards > Kiran > -- Regards, Hardik "If you are doing what you have always been doing then expect what you have always been getting." -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
