Hi. You are right. Kernel panic was because my 2.6.31 kernel didn't have ASHMEM driver, i found it in core/init/ source files. The good news is that ASHMEM driver is the same for all linux kernels from 6.27 to 6.32. So yesterday i added ASHEMEM driver to my 2.6.31 kernel and it works. No Kernel Panic. But now i have very strange platform's behavior: it repeats in cycle create media service, and kill it. Here is my log:
init: starting 'console' init: starting 'servicemanager' init: starting 'vold' init: starting 'debuggerd' init: starting 'ril-daemon' init: starting 'zygote' init: Created socket '/dev/socket/zygote' with mode '666', user '0', group '0' init: Created socket '/dev/socket/vold' with mode '660', user '0', group '1009' init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000' init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001' init: starting 'media' init: cannot find '/system/bin/playmp3', disabling 'bootsound' init: starting 'dbus' init: starting 'installd' init: Created socket '/dev/socket/installd' with mode '600', user '1000', group '1000' init: Created socket '/dev/socket/dbus' with mode '660', user '1002', group '1002' sh: can't access tty; job control turned off init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' # init: starting 'keystore' init: command 'class_start' r=0 init: processing action 0x28b98 (property:persist.service.adb.enable=1) init: starting 'adbd' init: command 'start' r=0 init: Created socket '/dev/socket/keystore' with mode '666', user '0', group '0' init: waitpid returned pid 1712, status = 0000000b init: process 'media', pid 1712 exited init: process 'media' killing any children in process group init: starting 'media' init: waitpid returned pid 1718, status = 0000000b init: process 'media', pid 1718 exited init: process 'media' killing any children in process group In mgmain JNI_OnLoad init: starting 'media' init: waitpid returned pid 1719, status = 0000000b init: process 'media', pid 1719 exited init: process 'media' killing any children in process group init: starting 'media' init: waitpid returned pid 1720, status = 0000000b init: process 'media', pid 1720 exited init: process 'media' killing any children in process group init: starting 'media' init: waitpid returned pid 1721, status = 0000000b init: process 'media', pid 1721 exited init: process 'media' killing any children in process group init: starting 'media' Jan 1, 1970 12:00:32 AM com.ibm.icu4jni.util.Resources createTimeZoneNamesFor INFO: Loaded time zone names for en_US in 5925ms. init: waitpid returned pid 1722, status = 0000000b init: process 'media', pid 1722 exited init: process 'media' killing any children in process group init: starting 'media' init: waitpid returned pid 1723, status = 0000000b init: process 'media', pid 1723 exited init: process 'media' killing any children in process group init: starting 'media' init: waitpid returned pid 1724, status = 0000000b init: process 'media', pid 1724 exited init: process 'media' killing any children in process group Jan 1, 1970 12:00:43 AM javax.net.ssl.SSLSocketFactory log INFO: Using factory org.apache.harmony.xnet.provider.jsse.opensslsocketfactoryi...@401b9eb8 init: starting 'media' init: waitpid returned pid 1725, status = 0000000b init: process 'media', pid 1725 exited init: process 'media' killing any children in process group init: starting 'media' warning: `zygote' uses 32-bit capabilities (legacy support in use) init: waitpid returned pid 1726, status = 0000000b init: process 'media', pid 1726 exited init: process 'media' killing any children in process group init: starting 'media' select 1706 (sh), adj 0, size 25, to kill select 1707 (servicemanager), adj 0, size 27, to kill select 1708 (vold), adj 0, size 32, to kill select 1709 (debuggerd), adj 0, size 42, to kill select 1710 (rild), adj 0, size 48, to kill select 1711 (zygote), adj 0, size 2580, to kill select 1727 (system_server), adj 0, size 3263, to kill send sigkill to 1727 (system_server), adj 0, size 3263 init: waitpid returned pid 1711, status = 00000009 init: process 'zygote', pid 1711 exited init: process 'zygote' killing any children in process group init: service 'media' is being killed init: starting 'media' init: starting 'zygote' init: waitpid returned pid 1731, status = 0000000f init: untracked pid 1731 exited init: Created socket '/dev/socket/zygote' with mode '666', user '0', group '0' init: waitpid returned pid 1734, status = 0000000b init: process 'media', pid 1734 exited init: process 'media' killing any children in process group init: starting 'media' In mgmain JNI_OnLoad init: waitpid returned pid 1736, status = 0000000b init: process 'media', pid 1736 exited init: process 'media' killing any children in process group init: starting 'media' init: waitpid returned pid 1737, status = 0000000b init: process 'media', pid 1737 exited init: process 'media' killing any children in process group init: starting 'media' On Mar 16, 3:47 am, abukustfan <[email protected]> wrote: > Did you add ash memory to your kernel? > > On Mar 13, 3:37šam, íÁËÓÉÍ áÎÄÒÕÝÅÎËÏ <[email protected]> wrote: > > > Hello! > > > I am porting Android on s3c6410 compatible platform. So, using Android > > sources, i created platform's profile, and compiled ramdisk.img, > > system.img, userdata.img. > > > I use 2.6.31-rc4 kernel, in which i included android specific drivers: > > > # Android > > # > > CONFIG_ANDROID=y > > CONFIG_ANDROID_BINDER_IPC=y > > CONFIG_ANDROID_LOGGER=y > > CONFIG_ANDROID_RAM_CONSOLE=y > > CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y > > CONFIG_ANDROID_RAM_CONSOLE_EARLY_INIT=y > > CONFIG_ANDROID_RAM_CONSOLE_EARLY_ADDR=0 > > CONFIG_ANDROID_RAM_CONSOLE_EARLY_SIZE=0 > > CONFIG_ANDROID_TIMED_OUTPUT=y > > # CONFIG_ANDROID_TIMED_GPIO is not set > > CONFIG_ANDROID_LOW_MEMORY_KILLER=y > > > All my platform's driver compiled into kernel statically. > > Also i included ramdisk.img into kernel,because it's small sized - 160kb. > > I just unzipped ramdisk.img wit command šgzip -d ramdisk.img and got > > ramdisk.cpio > > Here is how i included this ramdisk.cpio to kernel. > > > CONFIG_BLK_DEV_INITRD=y > > CONFIG_INITRAMFS_SOURCE="/1/ramdisk.cpio" > > CONFIG_INITRAMFS_ROOT_UID=0 > > CONFIG_INITRAMFS_ROOT_GID=0 > > CONFIG_RD_GZIP=y > > # CONFIG_RD_BZIP2 is not set > > # CONFIG_RD_LZMA is not set > > CONFIG_INITRAMFS_COMPRESSION_NONE=y > > > Then I compiled kernel and got uImage. > > > Using U_BOOT i wrote kernle, system.img and userdata.img into nand flash. > > Here is my parameters in u-boot environment to kernel: > > mtdparts=s3c6400-nand:384k(u-boot),3m(kernel),65m(system),59m(userdata) > > console=ttySAC2,115200 > > which means > > mtdpart0 - u-boot > > mtdpart1 - linux kernel > > mtdpart2 - system.img (yaffs2) > > mtdpart3 - userdata.img (yaffs2) > > > But it's a pity, at the end of kernel booting i got an error: > > Freeing init memory: 348K > > s3c6410_setup_sdhci2_cfg_card: CTRL 2=00000100, 3=80808080 clk_ctrl=0008 > > s3c6410_setup_sdhci2_cfg_card: CTRL 2=00000100, 3=80808080 clk_ctrl=0008 > > Kernel panic - not syncing: Attempted to kill init! > > > What can it be the problem with? > > How init binary from ramdisk.img knows where i placed system.img and > > userdata.img? > > > Because in the init.rc i found something like this: > > mount yaffs m...@system /system > > > So isn't it strange? -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
