additional logcat messages D/AndroidRuntime( 1052): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<< D/AndroidRuntime( 1052): CheckJNI is OFF E/dalvikvm( 1052): Can't open dex cache '/data/dalvik-cache/sys...@framework@core....@classes.dex': No such file or directory I/dalvikvm( 1052): Unable to open or create cache for /system/framework/core.jar (/data/dalvik-cache/sys...@framework@core....@classes.dex) D/dalvikvm( 1052): Unable to process classpath element '/system/framework/core.jar' E/dalvikvm( 1052): Can't open dex cache '/data/dalvik-cache/sys...@framework@ext....@classes.dex': No such file or directory I/dalvikvm( 1052): Unable to open or create cache for /system/framework/ext.jar (/data/dalvik-cache/sys...@framework@ext....@classes.dex) D/dalvikvm( 1052): Unable to process classpath element '/system/framework/ext.jar' E/dalvikvm( 1052): Can't open dex cache '/data/dalvik-cache/sys...@framework@framework....@classes.dex': No such file or directory I/dalvikvm( 1052): Unable to open or create cache for /system/framework/framework.jar (/data/dalvik-cache/sys...@framework@framework....@classes.dex) D/dalvikvm( 1052): Unable to process classpath element '/system/framework/framework.jar' E/dalvikvm( 1052): Can't open dex cache '/data/dalvik-cache/sys...@framework@android.policy....@classes.dex': No such file or directory I/dalvikvm( 1052): Unable to open or create cache for /system/framework/android.policy.jar (/data/dalvik-cache/sys...@framework@android.policy....@classes.dex) D/dalvikvm( 1052): Unable to process classpath element '/system/framework/android.policy.jar' E/dalvikvm( 1052): Can't open dex cache '/data/dalvik-cache/sys...@framework@services....@classes.dex': No such file or directory I/dalvikvm( 1052): Unable to open or create cache for /system/framework/services.jar (/data/dalvik-cache/sys...@framework@services....@classes.dex) D/dalvikvm( 1052): Unable to process classpath element '/system/framework/services.jar' E/dalvikvm( 1052): ERROR: no valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar' D/dalvikvm( 1052): VM cleaning up D/dalvikvm( 1052): LinearAlloc 0x0 used 4100 of 5242880 (0%) W/dalvikvm( 1052): JNI_CreateJavaVM failed E/AndroidRuntime( 1052): JNI_CreateJavaVM failed I/ ( 1054): ServiceManager: 0xad08 W/AudioHardwareInterface( 1054): Using stubbed audio hardware. No sound will be produced. D/AudioHardwareInterface( 1054): setMode(NORMAL) I/CameraService( 1054): CameraService started: pid=1054 I/AudioFlinger( 1054): AudioFlinger's thread 0xb370 ready to run E/keystore( 1080): chdir: /data/misc/keystore: No such file or directory D/AndroidRuntime( 1079):
On Tue, Dec 22, 2009 at 3:55 PM, linux newbie <linux.newbi...@gmail.com> wrote: > It seems from init.rc, data/misc/keystore directory is unable to be created. > > any idea on the possible cause? > > On Tue, Dec 22, 2009 at 3:45 PM, linux newbie <linux.newbi...@gmail.com> > wrote: >> Thanks for your reply Anil. >> >> On issuing logcat command, I got the following response. >> >> # logcat >> I/DEBUG ( 1141): debuggerd: Dec 14 2009 20:00:01 >> I/vold ( 1140): Android Volume Daemon version 2.0 >> E/vold ( 1140): Unable to open '/sys/class/mmc_host' (No such file >> or directory) >> E/vold ( 1140): Unable to open '/sys/class/switch' (No such file or >> directory) >> D/vold ( 1140): Bootstrapping complete >> E/keystore( 1152): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1171): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1198): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1221): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1244): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1267): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1288): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1309): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1330): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1351): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1372): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1393): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1410): chdir: /data/misc/keystore: No such file or directory >> E/keystore( 1431): chdir: /data/misc/keystore: No such file or directory >> >> On Tue, Dec 22, 2009 at 3:38 PM, Anil Sasidharan <anil...@gmail.com> wrote: >>> Hi, >>> >>> Try running "logcat" command from the console and see the exact >>> point of failure.. >>> >>> Warm Regards, >>> Anil >>> >>> On Mon, Dec 21, 2009 at 4:44 PM, linux newbie <linux.newbi...@gmail.com> >>> wrote: >>>> >>>> Hi, >>>> >>>> How to display the desktop sort of thing in my target? >>>> I am getting the Android shell after booting but not desktop as we run >>>> the emulator. >>>> >>>> Any suggestion? >>>> >>>> Thanks >>>> >>>> On Mon, Dec 21, 2009 at 2:05 PM, linux newbie <linux.newbi...@gmail.com> >>>> wrote: >>>> > Hi All, >>>> > >>>> > Thanks very much for your guidance. Android shell shows up :) >>>> > >>>> > Thanking You. >>>> > >>>> > On Sun, Dec 20, 2009 at 7:42 PM, Anil Sasidharan <anil...@gmail.com> >>>> > wrote: >>>> >> Hi, >>>> >> >>>> >> It seems "ASHMEM" is not enabled in kernel config (kernel log >>>> >> does not >>>> >> show the asmem init message). Please enable this module (Android Shared >>>> >> Memory) and try. >>>> >> >>>> >> Warm Regards, >>>> >> Anil >>>> >> >>>> >> On Fri, Dec 18, 2009 at 5:54 AM, linux newbie >>>> >> <linux.newbi...@gmail.com> >>>> >> wrote: >>>> >>> >>>> >>> Hi, >>>> >>> >>>> >>> STEP 1: >>>> >>> I downloaded latest Andriod patched kernel (linux.2.6.27) using git >>>> >>> clone. I applied our board specific patch on top of it and compiled it >>>> >>> using toolchain arm-none-linux-gnueabi- >>>> >>> >>>> >>> I also compiled busybox with this same tool chain and booted the >>>> >>> system and things were working fine as expected. >>>> >>> >>>> >>> STEP 2: >>>> >>> Downloaded android source using git. compiled it for "generic" >>>> >>> product. >>>> >>> As my target has 128MB of SDRAM, I made a single root fs i.e copied >>>> >>> out/target/product/generic/system to >>>> >>> /out/target/product/generic/root_fs/system. >>>> >>> >>>> >>> commented mounting yaffs2 line for system and data in init.rc file. >>>> >>> >>>> >>> created ext2 file system image and downloaded it to my target. >>>> >>> >>>> >>> But I am not succesful in booting it. Please help me out to figure out >>>> >>> the cause. Below is the log. >>>> >>> >>>> >>> Uncompressing >>>> >>> >>>> >>> Linux............................................................................................................... >>>> >>> done, booting the kernel. >>>> >>> Linux version 2.6.27-00127-gf92ea03-dirty (new...@ubuntu910vm) (gcc >>>> >>> version 4.4.0 (GCC) ) #11 Thu Dec 17 15:44:03 PST 2009 >>>> >>> CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), cr=0000397f >>>> >>> Machine: RTS G5 >>>> >>> Got g5 info >>>> >>> 102292 C 1 3 >>>> >>> 00:1A:EA:10:22:92 >>>> >>> Memory policy: ECC disabled, Data cache writeback >>>> >>> Memory clock: 99.53MHz (*27) >>>> >>> Run Mode clock: 199.07MHz (*2) >>>> >>> Turbo Mode clock: 199.07MHz (*1.0, inactive) >>>> >>> Msc0: 97787ff8 (f6000008) >>>> >>> Msc1: 23c7f8c (f600000c) >>>> >>> Msc2: 7ff07ff0 (f6000010) >>>> >>> mdcnfg: 1cb, mdrefr: 1802f >>>> >>> cccr: 141 >>>> >>> CPLD Version: a02 >>>> >>> CPU0: D VIVT undefined 5 cache >>>> >>> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets >>>> >>> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets >>>> >>> Built 1 zonelists in Zone order, mobility grouping on. Total pages: >>>> >>> 32512 >>>> >>> Kernel command line: root=/dev/ram0 rootfstype=ext2 >>>> >>> console=ttyS1,115200 >>>> >>> PID hash table entries: 512 (order: 9, 2048 bytes) >>>> >>> Console: colour dummy device 80x30 >>>> >>> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) >>>> >>> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) >>>> >>> Memory: 64MB 64MB = 128MB total >>>> >>> Memory: 103564KB available (3184K code, 778K data, 112K init) >>>> >>> SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, >>>> >>> Nodes=1 >>>> >>> Calibrating delay loop... 397.31 BogoMIPS (lpj=1986560) >>>> >>> Mount-cache hash table entries: 512 >>>> >>> CPU: Testing write buffer coherency: ok >>>> >>> khelper used greatest stack depth: 6832 bytes left >>>> >>> net_namespace: 320 bytes >>>> >>> NET: Registered protocol family 16 >>>> >>> khelper used greatest stack depth: 6536 bytes left >>>> >>> RTS Init: Dec 17 2009 14:44:42 CPLD Version: 0a02 >>>> >>> set_uart_alt_func:irq = 21 alt_func = 1 >>>> >>> set_uart_alt_func:irq = 20 alt_func = 1 >>>> >>> pwr_switch_hold_count = 30 >>>> >>> khelper used greatest stack depth: 6440 bytes left >>>> >>> SCSI subsystem initialized >>>> >>> usbcore: registered new interface driver usbfs >>>> >>> usbcore: registered new interface driver hub >>>> >>> usbcore: registered new device driver usb >>>> >>> NET: Registered protocol family 2 >>>> >>> IP route cache hash table entries: 1024 (order: 0, 4096 bytes) >>>> >>> TCP established hash table entries: 4096 (order: 3, 32768 bytes) >>>> >>> TCP bind hash table entries: 4096 (order: 4, 81920 bytes) >>>> >>> TCP: Hash tables configured (established 4096 bind 4096) >>>> >>> TCP reno registered >>>> >>> NET: Registered protocol family 1 >>>> >>> checking if image is initramfs...it isn't (no cpio magic); looks like >>>> >>> an >>>> >>> initrd >>>> >>> Freeing initrd memory: 22129K >>>> >>> rts-kbd: Traker 5 keyboard >>>> >>> input: rts-kbd as /class/input/input0 >>>> >>> audit: initializing netlink socket (disabled) >>>> >>> type=2000 audit(8.940:1): initialized >>>> >>> JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. >>>> >>> msgmni has been set to 245 >>>> >>> io scheduler noop registered >>>> >>> io scheduler anticipatory registered >>>> >>> io scheduler deadline registered >>>> >>> io scheduler cfq registered (default) >>>> >>> rts_backlight_power(): power: 1 >>>> >>> Console: switching to colour frame buffer device 80x15 >>>> >>> pxafb_smart_thread: not properly initialized, thread terminated >>>> >>> ipmi message handler version 39.2 >>>> >>> ipmi device interface >>>> >>> IPMI Watchdog: driver initialized >>>> >>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART >>>> >>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART >>>> >>> console [ttyS1] enabled >>>> >>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART >>>> >>> pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 7) is a HWUART >>>> >>> brd: module loaded >>>> >>> loop: module loaded >>>> >>> logger: created 64K log 'log_main' >>>> >>> logger: created 256K log 'log_events' >>>> >>> logger: created 64K log 'log_radio' >>>> >>> SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 bit >>>> >>> encapsulation enabled). >>>> >>> CSLIP: code copyright 1989 Regents of the University of California. >>>> >>> SLIP linefill/keepalive option. >>>> >>> Driver 'sd' needs updating - please use bus_type methods >>>> >>> physmap platform flash device: 00100000 at 00000000 >>>> >>> Found: AMD AM29LV800BB >>>> >>> physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank >>>> >>> number of JEDEC chips: 1 >>>> >>> cfi_cmdset_0002: Disabling erase-suspend-program due to code >>>> >>> brokenness. >>>> >>> RedBoot partition parsing not available >>>> >>> RTS xD/NAND driver: 14:48:29 Dec 17 2009 >>>> >>> Addr: 0x06000000 >>>> >>> Adding NAND chip >>>> >>> NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 (Toshiba NAND 32MiB >>>> >>> 3,3V 8-bit) >>>> >>> Scanning device for bad blocks >>>> >>> Using static partition definition >>>> >>> Creating 3 MTD partitions on "NAND 32MiB 3,3V 8-bit": >>>> >>> 0x00000000-0x00200000 : "kernel image" >>>> >>> 0x00200000-0x02000000 : "root file system" >>>> >>> 0x00000000-0x02000000 : "entire nand device" >>>> >>> Adding xD card >>>> >>> No NAND device found!!! >>>> >>> 116x: driver isp116x-hcd, 03 Nov 2005 >>>> >>> Initializing USB Mass Storage driver... >>>> >>> usbcore: registered new interface driver usb-storage >>>> >>> USB Mass Storage support registered. >>>> >>> usbcore: registered new interface driver usbserial >>>> >>> usbserial: USB Serial Driver core >>>> >>> mice: PS/2 mouse device common for all mice >>>> >>> i2c /dev entries driver >>>> >>> Advanced Linux Sound Architecture Driver Version 1.0.17. >>>> >>> ALSA device list: >>>> >>> #0: pxa2xx-ac97 (Philips UCB1400) >>>> >>> IPv4 over IPv4 tunneling driver >>>> >>> GRE over IPv4 tunneling driver >>>> >>> TCP cubic registered >>>> >>> Initializing XFRM netlink socket >>>> >>> NET: Registered protocol family 17 >>>> >>> NET: Registered protocol family 15 >>>> >>> XScale DSP coprocessor detected. >>>> >>> RAMDISK: Compressed image found at block 0 >>>> >>> VFS: Mounted root (ext2 filesystem). >>>> >>> Freeing init memory: 112K >>>> >>> init used greatest stack depth: 4224 bytes left >>>> >>> Kernel panic - not syncing: Attempted to kill init! >>>> >>> >>>> >>> >>>> >>> Thanks >>>> >>> >>>> >>> >>>> >>> On Thu, Dec 17, 2009 at 5:12 AM, Yi Sun <beyo...@gmail.com> wrote: >>>> >>> > your init crashed. try to get some thing dump out from your init to >>>> >>> > make >>>> >>> > sure it works correctly >>>> >>> > >>>> >>> > On Wed, 2009-12-16 at 18:21 +1100, linux newbie wrote: >>>> >>> >> Hi, >>>> >>> >> >>>> >>> >> I downloaded the latest kernel (Android supported) from git clone >>>> >>> >> git://android.git.kernel.org. >>>> >>> >> >>>> >>> >> Modified it to include our device specific stuff and booted it with >>>> >>> >> our prevoius root fs(no android) and bang got the crash. >>>> >>> >> >>>> >>> >> can anyone help me out to debug this issue. >>>> >>> >> >>>> >>> >> Uncompressing >>>> >>> >> >>>> >>> >> Linux................................................................................................................. >>>> >>> >> done, booting the kernel. >>>> >>> >> Linux version 2.6.27 (new...@newbierhel4vm) (gcc version 4.0.2) #2 >>>> >>> >> Thu >>>> >>> >> Dec 10 05:53:32 EST 2009 >>>> >>> >> CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), cr=0000397f >>>> >>> >> Machine: RTS G5 >>>> >>> >> Got g5 info >>>> >>> >> 102292 C 1 3 >>>> >>> >> 00:1A:EA:10:22:92 >>>> >>> >> Memory policy: ECC disabled, Data cache writeback >>>> >>> >> Memory clock: 99.53MHz (*27) >>>> >>> >> Run Mode clock: 199.07MHz (*2) >>>> >>> >> Turbo Mode clock: 199.07MHz (*1.0, inactive) >>>> >>> >> Msc0: 97787ff8 (f6000008) >>>> >>> >> Msc1: 23c7f8c (f600000c) >>>> >>> >> Msc2: 7ff07ff0 (f6000010) >>>> >>> >> mdcnfg: 1cb, mdrefr: 1802f >>>> >>> >> cccr: 141 >>>> >>> >> CPLD Version: a02 >>>> >>> >> CPU0: D VIVT undefined 5 cache >>>> >>> >> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 >>>> >>> >> sets >>>> >>> >> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 >>>> >>> >> sets >>>> >>> >> Built 1 zonelists in Zone order, mobility grouping on. Total >>>> >>> >> pages: >>>> >>> >> 32512 >>>> >>> >> Kernel command line: root=/dev/mtdblock2 rootfstype=jffs2 >>>> >>> >> console=ttyS1,115200 >>>> >>> >> PID hash table entries: 512 (order: 9, 2048 bytes) >>>> >>> >> Console: colour dummy device 80x30 >>>> >>> >> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) >>>> >>> >> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) >>>> >>> >> Memory: 64MB 64MB = 128MB total >>>> >>> >> Memory: 125596KB available (3260K code, 780K data, 116K init) >>>> >>> >> SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, >>>> >>> >> Nodes=1 >>>> >>> >> Calibrating delay loop... 397.31 BogoMIPS (lpj=1986560) >>>> >>> >> Mount-cache hash table entries: 512 >>>> >>> >> CPU: Testing write buffer coherency: ok >>>> >>> >> net_namespace: 320 bytes >>>> >>> >> NET: Registered protocol family 16 >>>> >>> >> RTS Init: Dec 10 2009 05:06:54 CPLD Version: 0a02 >>>> >>> >> set_uart_alt_func:irq = 21 alt_func = 1 >>>> >>> >> set_uart_alt_func:irq = 20 alt_func = 1 >>>> >>> >> pwr_switch_hold_count = 30 >>>> >>> >> SCSI subsystem initialized >>>> >>> >> usbcore: registered new interface driver usbfs >>>> >>> >> usbcore: registered new interface driver hub >>>> >>> >> usbcore: registered new device driver usb >>>> >>> >> NET: Registered protocol family 2 >>>> >>> >> IP route cache hash table entries: 1024 (order: 0, 4096 bytes) >>>> >>> >> TCP established hash table entries: 4096 (order: 3, 32768 bytes) >>>> >>> >> TCP bind hash table entries: 4096 (order: 4, 81920 bytes) >>>> >>> >> TCP: Hash tables configured (established 4096 bind 4096) >>>> >>> >> TCP reno registered >>>> >>> >> NET: Registered protocol family 1 >>>> >>> >> rts-kbd: Traker 5 keyboard >>>> >>> >> input: rts-kbd as /class/input/input0 >>>> >>> >> audit: initializing netlink socket (disabled) >>>> >>> >> type=2000 audit(0.490:1): initialized >>>> >>> >> JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. >>>> >>> >> msgmni has been set to 245 >>>> >>> >> io scheduler noop registered >>>> >>> >> io scheduler anticipatory registered >>>> >>> >> io scheduler deadline registered >>>> >>> >> io scheduler cfq registered (default) >>>> >>> >> rts_backlight_power(): power: 1 >>>> >>> >> Console: switching to colour frame buffer device 80x15 >>>> >>> >> pxafb_smart_thread: not properly initialized, thread terminated >>>> >>> >> ipmi message handler version 39.2 >>>> >>> >> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART >>>> >>> >> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART >>>> >>> >> console [ttyS1] enabled >>>> >>> >> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART >>>> >>> >> pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 7) is a HWUART >>>> >>> >> brd: module loaded >>>> >>> >> loop: module loaded >>>> >>> >> logger: created 64K log 'log_main' >>>> >>> >> logger: created 256K log 'log_events' >>>> >>> >> logger: created 64K log 'log_radio' >>>> >>> >> SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 >>>> >>> >> bit >>>> >>> >> encapsulation enabled). >>>> >>> >> CSLIP: code copyright 1989 Regents of the University of California. >>>> >>> >> SLIP linefill/keepalive option. >>>> >>> >> Driver 'sd' needs updating - please use bus_type methods >>>> >>> >> physmap platform flash device: 00100000 at 00000000 >>>> >>> >> Found: AMD AM29LV800BB >>>> >>> >> physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank >>>> >>> >> number of JEDEC chips: 1 >>>> >>> >> cfi_cmdset_0002: Disabling erase-suspend-program due to code >>>> >>> >> brokenness. >>>> >>> >> RedBoot partition parsing not available >>>> >>> >> RTS xD/NAND driver: 05:07:00 Dec 10 2009 >>>> >>> >> Addr: 0x06000000 >>>> >>> >> Adding NAND chip >>>> >>> >> NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 (Toshiba NAND >>>> >>> >> 32MiB >>>> >>> >> 3,3V 8-bit) >>>> >>> >> Scanning device for bad blocks >>>> >>> >> Using static partition definition >>>> >>> >> Creating 3 MTD partitions on "NAND 32MiB 3,3V 8-bit": >>>> >>> >> 0x00000000-0x00200000 : "kernel image" >>>> >>> >> 0x00200000-0x02000000 : "root file system" >>>> >>> >> 0x00000000-0x02000000 : "entire nand device" >>>> >>> >> Adding xD card >>>> >>> >> No NAND device found!!! >>>> >>> >> 116x: driver isp116x-hcd, 03 Nov 2005 >>>> >>> >> Initializing USB Mass Storage driver... >>>> >>> >> usbcore: registered new interface driver usb-storage >>>> >>> >> USB Mass Storage support registered. >>>> >>> >> usbcore: registered new interface driver usbserial >>>> >>> >> usbserial: USB Serial Driver core >>>> >>> >> mice: PS/2 mouse device common for all mice >>>> >>> >> i2c /dev entries driver >>>> >>> >> Advanced Linux Sound Architecture Driver Version 1.0.17. >>>> >>> >> ALSA device list: >>>> >>> >> #0: pxa2xx-ac97 (Philips UCB1400) >>>> >>> >> IPv4 over IPv4 tunneling driver >>>> >>> >> GRE over IPv4 tunneling driver >>>> >>> >> TCP cubic registered >>>> >>> >> Initializing XFRM netlink socket >>>> >>> >> NET: Registered protocol family 17 >>>> >>> >> NET: Registered protocol family 15 >>>> >>> >> XScale DSP coprocessor detected. >>>> >>> >> Empty flash at 0x00506c78 ends at 0x00506e00 >>>> >>> >> jffs2_scan_inode_node(): CRC failed on node at 0x00da89ec: Read >>>> >>> >> 0xffffffff, calculated 0xa44aeeec >>>> >>> >> Empty flash at 0x00da8a30 ends at 0x00da8c00 >>>> >>> >> jffs2_scan_inode_node(): CRC failed on node at 0x0108ebd8: Read >>>> >>> >> 0xffffffff, calculated 0x45ea5198 >>>> >>> >> mtd->read(0x3c40 bytes from 0x10943c0) returned ECC error >>>> >>> >> jffs2_scan_inode_node(): CRC failed on node at 0x010945c4: Read >>>> >>> >> 0x0624050b, calculated 0xc6062405 >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x01094638: >>>> >>> >> 0x85ff instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x0109463c: >>>> >>> >> 0x74e0 instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x01094640: >>>> >>> >> 0xbc00 instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x01094644: >>>> >>> >> 0x5f68 instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x01094648: >>>> >>> >> 0x6000 instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x0109464c: >>>> >>> >> 0xa400 instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x01094654: >>>> >>> >> 0x8000 instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x01094658: >>>> >>> >> 0xac00 instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x0109465c: >>>> >>> >> 0xac00 instead >>>> >>> >> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at >>>> >>> >> 0x01094660: >>>> >>> >> 0xac00 instead >>>> >>> >> Further such events for this erase block will not be printed >>>> >>> >> jffs2_scan_inode_node(): CRC failed on node at 0x0109a5d0: Read >>>> >>> >> 0xffffffff, calculated 0x662e61ab >>>> >>> >> Empty flash at 0x010d8c10 ends at 0x010d8e00 >>>> >>> >> Empty flash at 0x010e9614 ends at 0x010e9800 >>>> >>> >> jffs2_scan_inode_node(): CRC failed on node at 0x010ee5ec: Read >>>> >>> >> 0xffffffff, calculated 0xe54a14a9 >>>> >>> >> jffs2_scan_dirent_node(): Node CRC failed on node at 0x012299f0: >>>> >>> >> Read >>>> >>> >> 0xffffffff, calculated 0x17e5bbcb >>>> >>> >> Empty flash at 0x01229a20 ends at 0x01229c00 >>>> >>> >> jffs2_scan_dirent_node(): Node CRC failed on node at 0x012f2bf4: >>>> >>> >> Read >>>> >>> >> 0xffffffff, calculated 0x2322e93d >>>> >>> >> Empty flash at 0x012f2c24 ends at 0x012f2e00 >>>> >>> >> VFS: Mounted root (jffs2 filesystem). >>>> >>> >> Freeing init memory: 116K >>>> >>> >> Kernel panic - not syncing: Attempted to kill init! >>>> >>> >> >>>> >>> >> On Wed, Dec 16, 2009 at 4:48 PM, Sayiram K N >>>> >>> >> <sayiram.koth...@gmail.com> wrote: >>>> >>> >> > Hi >>>> >>> >> > before loading the android can you try to load the linux kernel?? >>>> >>> >> > if >>>> >>> >> > it succeeds then you can switch to Android.may be change the root >>>> >>> >> > args >>>> >>> >> > as /sbin/init >>>> >>> >> > >>>> >>> >> > >>>> >>> >> > On 12/16/09, jack <yichang.zhu...@gmail.com> wrote: >>>> >>> >> >> Hello, >>>> >>> >> >> >>>> >>> >> >> As Novin said, your kernel does not have the necessary stuff >>>> >>> >> >> Android >>>> >>> >> >> needs. >>>> >>> >> >> You have to get your source code from >>>> >>> >> >> http://android.git.kernel.org/ >>>> >>> >> >> >>>> >>> >> >> Regards, >>>> >>> >> >> Jack >>>> >>> >> >> >>>> >>> >> >> On 12月16日, 上午10時08分, linux newbie <linux.newbi...@gmail.com> >>>> >>> >> >> wrote: >>>> >>> >> >>> Hi, >>>> >>> >> >>> >>>> >>> >> >>> I already enabled CONFIG_ARM_THUMB. >>>> >>> >> >>> >>>> >>> >> >>> Is it enough to make changes in make menuconfig of downloaded >>>> >>> >> >>> kernel >>>> >>> >> >>> for android? I am not finding ashmem under kernel/mm. >>>> >>> >> >>> >>>> >>> >> >>> Thanks >>>> >>> >> >>> >>>> >>> >> >>> >>>> >>> >> >>> >>>> >>> >> >>> On Wed, Dec 16, 2009 at 12:58 PM, jack >>>> >>> >> >>> <yichang.zhu...@gmail.com> >>>> >>> >> >>> wrote: >>>> >>> >> >>> > Hello, >>>> >>> >> >>> >>>> >>> >> >>> > Your log before the kernel panic is much the same as what I >>>> >>> >> >>> > had >>>> >>> >> >>> > before. >>>> >>> >> >>> > I solve my problem by enabling the CONFIG_ARM_THUMB of >>>> >>> >> >>> > processor >>>> >>> >> >>> > feature to support Thumb user binaries. >>>> >>> >> >>> > Good luck. >>>> >>> >> >>> >>>> >>> >> >>> > Regards, >>>> >>> >> >>> > Jack >>>> >>> >> >>> >>>> >>> >> >>> > On 12月16日, 上午7時53分, linux newbie <linux.newbi...@gmail.com> >>>> >>> >> >>> > wrote: >>>> >>> >> >>> >> Hi, >>>> >>> >> >>> >>>> >>> >> >>> >> Here is the log before crash. >>>> >>> >> >>> >>>> >>> >> >>> >> Starting kernel ... >>>> >>> >> >>> >>>> >>> >> >>> >> Uncompressing >>>> >>> >> >>> >> >>>> >>> >> >>> >> >>>> >>> >> >>> >> Linux...................................................................... >>>> >>> >> >>> >> ..................................................... >>>> >>> >> >>> >> done, booting the kernel. >>>> >>> >> >>> >> Linux version 2.6.31.1 (new...@ubuntu910vm) (gcc version >>>> >>> >> >>> >> 4.4.0 >>>> >>> >> >>> >> (GCC) ) >>>> >>> >> >>> >> #29 Tue Dec 15 14:54:04 PST 2009 >>>> >>> >> >>> >> CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), >>>> >>> >> >>> >> cr=0000397f >>>> >>> >> >>> >> CPU: VIVT data cache, VIVT instruction cache >>>> >>> >> >>> >> Machine: RTS G5 >>>> >>> >> >>> >> Got g5 info >>>> >>> >> >>> >> 102292 C 1 3 >>>> >>> >> >>> >> 00:1A:EA:10:22:92 >>>> >>> >> >>> >> Memory policy: ECC disabled, Data cache writeback >>>> >>> >> >>> >> Memory clock: 99.53MHz (*27) >>>> >>> >> >>> >> Run Mode clock: 199.07MHz (*2) >>>> >>> >> >>> >> Turbo Mode clock: 199.07MHz (*1.0, inactive) >>>> >>> >> >>> >> Msc0: 97787ff8 (f6000008) >>>> >>> >> >>> >> Msc1: 23c7f8c (f600000c) >>>> >>> >> >>> >> Msc2: 7ff07ff0 (f6000010) >>>> >>> >> >>> >> mdcnfg: 1cb, mdrefr: 1802f >>>> >>> >> >>> >> cccr: 141 >>>> >>> >> >>> >> CPLD Version: a02 >>>> >>> >> >>> >> Built 1 zonelists in Zone order, mobility grouping on. >>>> >>> >> >>> >> Total >>>> >>> >> >>> >> pages: >>>> >>> >> >>> >> 32512 >>>> >>> >> >>> >> Kernel command line: root=/dev/ram0 rootfstype=ext2 >>>> >>> >> >>> >> console=ttyS1,115200 >>>> >>> >> >>> >> PID hash table entries: 512 (order: 9, 2048 bytes) >>>> >>> >> >>> >> Dentry cache hash table entries: 16384 (order: 4, 65536 >>>> >>> >> >>> >> bytes) >>>> >>> >> >>> >> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) >>>> >>> >> >>> >> Memory: 64MB 64MB = 128MB total >>>> >>> >> >>> >> Memory: 103580KB available (3424K code, 397K data, 108K >>>> >>> >> >>> >> init, 0K >>>> >>> >> >>> >> highmem) >>>> >>> >> >>> >> SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, >>>> >>> >> >>> >> CPUs=1, >>>> >>> >> >>> >> Nodes=1 >>>> >>> >> >>> >> NR_IRQS:208 >>>> >>> >> >>> >> Console: colour dummy device 80x30 >>>> >>> >> >>> >> Calibrating delay loop... 397.31 BogoMIPS (lpj=1986560) >>>> >>> >> >>> >> Mount-cache hash table entries: 512 >>>> >>> >> >>> >> CPU: Testing write buffer coherency: ok >>>> >>> >> >>> >> NET: Registered protocol family 16 >>>> >>> >> >>> >> RTS Init: Dec 14 2009 21:48:29 CPLD Version: 0a02 >>>> >>> >> >>> >> set_uart_alt_func:irq = 21 alt_func = 1 >>>> >>> >> >>> >> set_uart_alt_func:irq = 20 alt_func = 1 >>>> >>> >> >>> >> pwr_switch_hold_count = 30 >>>> >>> >> >>> >> 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 >>>> >>> >> >>> >> cfg80211: Calling CRDA to update world regulatory domain >>>> >>> >> >>> >> NET: Registered protocol family 2 >>>> >>> >> >>> >> IP route cache hash table entries: 1024 (order: 0, 4096 >>>> >>> >> >>> >> bytes) >>>> >>> >> >>> >> TCP established hash table entries: 4096 (order: 3, 32768 >>>> >>> >> >>> >> bytes) >>>> >>> >> >>> >> TCP bind hash table entries: 4096 (order: 2, 16384 bytes) >>>> >>> >> >>> >> TCP: Hash tables configured (established 4096 bind 4096) >>>> >>> >> >>> >> TCP reno registered >>>> >>> >> >>> >> NET: Registered protocol family 1 >>>> >>> >> >>> >> Trying to unpack rootfs image as initramfs... >>>> >>> >> >>> >> rootfs image is not initramfs (no cpio magic); looks like an >>>> >>> >> >>> >> initrd >>>> >>> >> >>> >> Freeing initrd memory: 22128K >>>> >>> >> >>> >> rts-kbd: Traker 5 keyboard >>>> >>> >> >>> >> input: rts-kbd as /class/input/input0 >>>> >>> >> >>> >> NetWinder Floating Point Emulator V0.97 (double precision) >>>> >>> >> >>> >> JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. >>>> >>> >> >>> >> msgmni has been set to 245 >>>> >>> >> >>> >> alg: No test for stdrng (krng) >>>> >>> >> >>> >> io scheduler noop registered >>>> >>> >> >>> >> io scheduler anticipatory registered >>>> >>> >> >>> >> io scheduler deadline registered >>>> >>> >> >>> >> io scheduler cfq registered (default) >>>> >>> >> >>> >> rts_backlight_power(): power: 1 >>>> >>> >> >>> >> Console: switching to colour frame buffer device 80x15 >>>> >>> >> >>> >> ipmi message handler version 39.2 >>>> >>> >> >>> >> ipmi device interface >>>> >>> >> >>> >> IPMI Watchdog: driver initialized >>>> >>> >> >>> >> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a >>>> >>> >> >>> >> FFUART >>>> >>> >> >>> >> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a >>>> >>> >> >>> >> BTUART >>>> >>> >> >>> >> console [ttyS1] enabled >>>> >>> >> >>> >> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a >>>> >>> >> >>> >> STUART >>>> >>> >> >>> >> pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 7) is a >>>> >>> >> >>> >> HWUART >>>> >>> >> >>> >> brd: module loaded >>>> >>> >> >>> >> loop: module loaded >>>> >>> >> >>> >> nbd: registered device at major 43 >>>> >>> >> >>> >> SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, >>>> >>> >> >>> >> max=256) >>>> >>> >> >>> >> (6 bit >>>> >>> >> >>> >> encapsulation enabled). >>>> >>> >> >>> >> CSLIP: code copyright 1989 Regents of the University of >>>> >>> >> >>> >> California. >>>> >>> >> >>> >> SLIP linefill/keepalive option. >>>> >>> >> >>> >> smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <n...@cam.org> >>>> >>> >> >>> >> eth0: SMC91C11xFD (rev 1) at c88ba300 IRQ 90 [nowait] >>>> >>> >> >>> >> eth0: Ethernet addr: 00:1a:ea:10:22:92 >>>> >>> >> >>> >> physmap platform flash device: 00100000 at 00000000 >>>> >>> >> >>> >> Found: AMD AM29LV800BB >>>> >>> >> >>> >> physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank >>>> >>> >> >>> >> number of JEDEC chips: 1 >>>> >>> >> >>> >> cfi_cmdset_0002: Disabling erase-suspend-program due to code >>>> >>> >> >>> >> brokenness. >>>> >>> >> >>> >> RedBoot partition parsing not available >>>> >>> >> >>> >> RTS xD/NAND driver: 21:53:13 Dec 14 2009 >>>> >>> >> >>> >> Addr: 0x06000000 >>>> >>> >> >>> >> Adding NAND chip >>>> >>> >> >>> >> NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 (Toshiba >>>> >>> >> >>> >> NAND >>>> >>> >> >>> >> 32MiB >>>> >>> >> >>> >> 3,3V 8-bit) >>>> >>> >> >>> >> Scanning device for bad blocks >>>> >>> >> >>> >> Bad eraseblock 0 at 0x000000000000 >>>> >>> >> >>> >> Using static partition definition >>>> >>> >> >>> >> Creating 3 MTD partitions on "NAND 32MiB 3,3V 8-bit": >>>> >>> >> >>> >> 0x000000000000-0x000000200000 : "kernel image" >>>> >>> >> >>> >> 0x000000200000-0x000002000000 : "root file system" >>>> >>> >> >>> >> 0x000000000000-0x000002000000 : "entire nand device" >>>> >>> >> >>> >> Adding xD card >>>> >>> >> >>> >> No NAND device found!!! >>>> >>> >> >>> >> reset disable >>>> >>> >> >>> >> driver isp1362-hcd, 2005-04-04 >>>> >>> >> >>> >> isp1362-hcd isp1362-hcd.0: ISP1362 Host Controller >>>> >>> >> >>> >> isp1362-hcd isp1362-hcd.0: new USB bus registered, assigned >>>> >>> >> >>> >> bus >>>> >>> >> >>> >> number >>>> >>> >> >>> >> 1 >>>> >>> >> >>> >> isp1362_hc_reset: >>>> >>> >> >>> >> isp1362-hcd isp1362-hcd.0: irq 87, io mem 0x08000000 >>>> >>> >> >>> >> isp1362_hc_start: >>>> >>> >> >>> >> isp1362-hcd isp1362-hcd.0: ISP1362 Memory usage: >>>> >>> >> >>> >> isp1362-hcd isp1362-hcd.0: ISTL: 2 * 256: 512 @ >>>> >>> >> >>> >> $0000:$0100 >>>> >>> >> >>> >> isp1362-hcd isp1362-hcd.0: INTL: 16 * ( 64+8): 1152 @ >>>> >>> >> >>> >> $0200 >>>> >>> >> >>> >> isp1362-hcd isp1362-hcd.0: ATL : 32 * ( 64+8): 2304 @ >>>> >>> >> >>> >> $0680 >>>> >>> >> >>> >> isp1362-hcd isp1362-hcd.0: USED/FREE: 3968 128 >>>> >>> >> >>> >> usb usb1: New USB device found, idVendor=1d6b, >>>> >>> >> >>> >> idProduct=0001 >>>> >>> >> >>> >> usb usb1: New USB device strings: Mfr=3, Product=2, >>>> >>> >> >>> >> SerialNumber=1 >>>> >>> >> >>> >> usb usb1: Product: ISP1362 Host Controller >>>> >>> >> >>> >> usb usb1: Manufacturer: Linux 2.6.31.1 isp1362-hcd >>>> >>> >> >>> >> usb usb1: SerialNumber: isp1362-hcd.0 >>>> >>> >> >>> >> usb usb1: configuration #1 chosen from 1 choice >>>> >>> >> >>> >> hub 1-0:1.0: USB hub found >>>> >>> >> >>> >> hub 1-0:1.0: 2 ports detected >>>> >>> >> >>> >> ISP1362 Host Controller, irq 87 >>>> >>> >> >>> >> Initializing USB Mass Storage driver... >>>> >>> >> >>> >> usbcore: registered new interface driver usb-storage >>>> >>> >> >>> >> USB Mass Storage support registered. >>>> >>> >> >>> >> usbcore: registered new interface driver usbserial >>>> >>> >> >>> >> usbserial: USB Serial Driver core >>>> >>> >> >>> >> mice: PS/2 mouse device common for all mice >>>> >>> >> >>> >> i2c /dev entries driver >>>> >>> >> >>> >> I2C: i2c-0: PXA I2C adapter >>>> >>> >> >>> >> Advanced Linux Sound Architecture Driver Version 1.0.20. >>>> >>> >> >>> >> ALSA device list: >>>> >>> >> >>> >> #0: pxa2xx-ac97 (Philips UCB1400) >>>> >>> >> >>> >> IPv4 over IPv4 tunneling driver >>>> >>> >> >>> >> GRE over IPv4 tunneling driver >>>> >>> >> >>> >> TCP cubic registered >>>> >>> >> >>> >> Initializing XFRM netlink socket >>>> >>> >> >>> >> NET: Registered protocol family 17 >>>> >>> >> >>> >> NET: Registered protocol family 15 >>>> >>> >> >>> >> lib80211: common routines for IEEE802.11 drivers >>>> >>> >> >>> >> XScale DSP coprocessor detected. >>>> >>> >> >>> >> RAMDISK: gzip image found at block 0 >>>> >>> >> >>> >> VFS: Mounted root (ext2 filesystem) on device 1:0. >>>> >>> >> >>> >> Freeing init memory: 108K >>>> >>> >> >>> >> Kernel panic - not syncing: Attempted to kill init! >>>> >>> >> >>> >> [<c00294e0>] (unwind_backtrace+0x0/0xd8) from [<c02a0524>] >>>> >>> >> >>> >> (panic+0x40/0x108) >>>> >>> >> >>> >> [<c02a0524>] (panic+0x40/0x108) from [<c0041318>] >>>> >>> >> >>> >> (do_exit+0x68/0x5dc) >>>> >>> >> >>> >> [<c0041318>] (do_exit+0x68/0x5dc) from [<c0041918>] >>>> >>> >> >>> >> (do_group_exit+0x8c/0xc0) >>>> >>> >> >>> >> [<c0041918>] (do_group_exit+0x8c/0xc0) from [<c004a48c>] >>>> >>> >> >>> >> (get_signal_to_deliver+0x2d8/0x310) >>>> >>> >> >>> >> [<c004a48c>] (get_signal_to_deliver+0x2d8/0x310) from >>>> >>> >> >>> >> [<c0026490>] >>>> >>> >> >>> >> (do_signal+0x54/0x4ec) >>>> >>> >> >>> >> [<c0026490>] (do_signal+0x54/0x4ec) from [<c0023e0c>] >>>> >>> >> >>> >> (work_pending+0x1c/0x20) >>>> >>> >> >>> >>>> >>> >> >>> >> On Wed, Dec 16, 2009 at 9:32 AM, linux newbie >>>> >>> >> >>> >> <linux.newbi...@gmail.com> wrote: >>>> >>> >> >>> >> > Hi, >>>> >>> >> >>> >>>> >>> >> >>> >> > I download the 2.6.31 kernel from kernel.org and updated >>>> >>> >> >>> >> > it >>>> >>> >> >>> >> > with our >>>> >>> >> >>> >> > board specific patch. Then I enabled Android specific >>>> >>> >> >>> >> > stuff >>>> >>> >> >>> >> > using >>>> >>> >> >>> >> > make >>>> >>> >> >>> >> > menuconfig -> device drivers->staging drivers->Andriod. >>>> >>> >> >>> >>>> >>> >> >>> >> > I havent updated the kernel with yaffs2 patch, as I am >>>> >>> >> >>> >> > downloading >>>> >>> >> >>> >> > the >>>> >>> >> >>> >> > andriod rootfs into SDRAM (ext2) and commenting out >>>> >>> >> >>> >> > mounting >>>> >>> >> >>> >> > yaffs2 >>>> >>> >> >>> >> > in >>>> >>> >> >>> >> > init.rc file. >>>> >>> >> >>> >>>> >>> >> >>> >> > Apart from above kernel modifications do I need to make >>>> >>> >> >>> >> > any >>>> >>> >> >>> >> > other >>>> >>> >> >>> >> > changes in kernel? >>>> >>> >> >>> >>>> >>> >> >>> >> > Thanks >>>> >>> >> >>> >>>> >>> >> >>> >> > On Wed, Dec 16, 2009 at 7:05 AM, Novin S. >>>> >>> >> >>> >> > <novin...@gmail.com> >>>> >>> >> >>> >> > wrote: >>>> >>> >> >>> >> >> The problem is that the kernel you are using on your >>>> >>> >> >>> >> >> device >>>> >>> >> >>> >> >> is not >>>> >>> >> >>> >> >> suited for the version of the root fs or it is not >>>> >>> >> >>> >> >> properly >>>> >>> >> >>> >> >> patched >>>> >>> >> >>> >> >> with android specific diffs.... >>>> >>> >> >>> >>>> >>> >> >>> >> >> On Dec 15, 3:24 pm, "Dennis.Yxun" <dennis.y...@gmail.com> >>>> >>> >> >>> >> >> wrote: >>>> >>> >> >>> >> >>> do u use ramdisk or others? >>>> >>> >> >>> >> >>> make sure kernel can find 'init' program >>>> >>> >> >>> >>>> >>> >> >>> >> >>> On Tue, Dec 15, 2009 at 4:34 PM, linux newbie >>>> >>> >> >>> >> >>> <linux.newbi...@gmail.com>wrote: >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > Hi, >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > Thanks for your reply. >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > As the messages are printing on the lcd, I couldn't >>>> >>> >> >>> >> >>> > able >>>> >>> >> >>> >> >>> > to get >>>> >>> >> >>> >> >>> > the >>>> >>> >> >>> >> >>> > logs. Anyway I shall try tomorrow. >>>> >>> >> >>> >> >>> > After Freeing Init memory, I am getting this Kernel >>>> >>> >> >>> >> >>> > Panic >>>> >>> >> >>> >> >>> > (seems >>>> >>> >> >>> >> >>> > console is opened properly) >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > Please let me know, whether the procedure I am using >>>> >>> >> >>> >> >>> > to >>>> >>> >> >>> >> >>> > bring up >>>> >>> >> >>> >> >>> > Android is correct or not? >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > Thanks >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > On Tue, Dec 15, 2009 at 6:29 PM, jack >>>> >>> >> >>> >> >>> > <yichang.zhu...@gmail.com> >>>> >>> >> >>> >> >>> > wrote: >>>> >>> >> >>> >> >>> > > Hello, >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > > According to my porting experience, there will be >>>> >>> >> >>> >> >>> > > many >>>> >>> >> >>> >> >>> > > causes >>>> >>> >> >>> >> >>> > > resulting in kernel panic. >>>> >>> >> >>> >> >>> > > Pasting more logs before the line kernel panic will >>>> >>> >> >>> >> >>> > > help >>>> >>> >> >>> >> >>> > > for >>>> >>> >> >>> >> >>> > > others to >>>> >>> >> >>> >> >>> > > figure out your problem. Thanks. >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > > Regards >>>> >>> >> >>> >> >>> > > Jack >>>> >>> >> >>> >>>> >>> >> >>> >> >>> > > On 12月15日, >>>> >>> >> >>> >>>> >>> >> >>> ... >>>> >>> >> >>> >>>> >>> >> >>> 閱讀更多 »- 隱藏被引用文字 - >>>> >>> >> >>> >>>> >>> >> >>> - 顯示被引用文字 - >>>> >>> >> >> >>>> >>> >> >> -- >>>> >>> >> >> unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> >>> >> >> website: http://groups.google.com/group/android-porting >>>> >>> >> > >>>> >>> >> > -- >>>> >>> >> > unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> >>> >> > website: http://groups.google.com/group/android-porting >>>> >>> >> >>>> >>> >> -- >>>> >>> >> unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> >>> >> website: http://groups.google.com/group/android-porting >>>> >>> > >>>> >>> > >>>> >>> > -- >>>> >>> > Android-x86 >>>> >>> > www.android-x86.org >>>> >>> > >>>> >>> > -- >>>> >>> > unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> >>> > website: http://groups.google.com/group/android-porting >>>> >>> >>>> >>> -- >>>> >>> unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> >>> website: http://groups.google.com/group/android-porting >>>> >> >>>> >> -- >>>> >> unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> >> website: http://groups.google.com/group/android-porting >>>> > >>>> >>>> -- >>>> unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> website: http://groups.google.com/group/android-porting >>> >>> -- >>> unsubscribe: android-porting+unsubscr...@googlegroups.com >>> website: http://groups.google.com/group/android-porting >> > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
