Hi Girish, here is how bootargs looks
setenv bootargs console=ttyS3,115200n8 root=/dev/mmcblk0p2 rw r ootdelay=1 mem=256M init=/init videoout=omap24xxvout omap_vout.video1_numbuffers =4 omap_vout.vid1_static_vrfb_alloc=y /Shivappa On Nov 22, 11:16 pm, girish <[email protected]> wrote: > Shivappa, > What's the bootargs used? > > Girish > > On Sun, Nov 22, 2009 at 10:30 AM, Shivappa <[email protected]>wrote: > > > Hi Sreekanth, > > > Here are the console logs just before the panic. Note that I did > > create /dev/console, still for some reason, I get a console message > > saying unable to open initial console. > > > <6>twl4030_rtc twl4030_rtc: setting system clock to 2000-01-04 > > 07:48:30 UTC (946 > > 972110) > > twl4030_rtc twl4030_rtc: setting system clock to 2000-01-04 07:48:30 > > UTC (946972 > > 110) > > <3>omapdss DPI error: display already enabled > > omapdss DPI error: display already enabled > > <4>omap_vout omap_vout: 'lcd' Display already enabled > > omap_vout omap_vout: 'lcd' Display already enabled > > <3>omapdss DPI error: display already enabled > > omapdss DPI error: display already enabled > > <4>omap_vout omap_vout: 'lcd' Display already enabled > > omap_vout omap_vout: 'lcd' Display already enabled > > <6>omap_voutBuffer Size = 4096000 > > omap_voutBuffer Size = 4096000 > > <6>omap_vout: registered and initialized video device 0 [v4l2] > > omap_vout: registered and initialized video device 0 [v4l2] > > <6>omap_voutBuffer Size = 4096000 > > omap_voutBuffer Size = 4096000 > > <6>omap_vout: registered and initialized video device 1 [v4l2] > > omap_vout: registered and initialized video device 1 [v4l2] > > <7>Restoring csi2 context > > <7>imx046_sensor_power_set(ON) > > <6>imx046 2-001a: model id detected 0x46 mfr 0xb, rev# 0x2 > > imx046 2-001a: model id detected 0x46 mfr 0xb, rev# 0x2 > > <6>imx046 2-001a: imx046 chip version 0x02 detected > > imx046 2-001a: imx046 chip version 0x02 detected > > <7>imx046_sensor_power_set(OFF) > > <7>Saving csi2 context > > <7>lv8093_lens_power_set(ON) > > <6>lv8093 Lens HW detected > > lv8093 Lens HW detected > > <7>lv8093_lens_power_set(OFF) > > <6>lv8093 2-0072: Registered lv8093 as V4L2 device. > > lv8093 2-0072: Registered lv8093 as V4L2 device. > > <6>Registered lv8093 as i2c device. > > Registered lv8093 as i2c device. > > <6>Waiting 1sec before mounting root device... > > Waiting 1sec before mounting root device... > > <6>mmc1: new high speed MMC card at address 0001 > > mmc1: new high speed MMC card at address 0001 > > <6>mmcblk1: mmc1:0001 STM16G 1.00 GiB > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > > <6> mmcblk1: mmcblk1: unknown partition table > > unknown partition table > > <6>kjournald starting. Commit interval 5 seconds > > kjournald starting. Commit interval 5 seconds > > <4>EXT3-fs warning: maximal mount count reached, running e2fsck is > > recommended > > EXT3-fs warning: maximal mount count reached, running e2fsck is > > recommended > > <6>EXT3 FS on mmcblk0p2, EXT3 FS on mmcblk0p2, internal journal > > internal journal > > <6>EXT3-fs: recovery complete. > > EXT3-fs: recovery complete. > > <6>EXT3-fs: mounted filesystem with writeback data mode. > > EXT3-fs: mounted filesystem with writeback data mode. > > VFS: Mounted root (ext3 filesystem) on device 179:2. > > VFS: Mounted root (ext3 filesystem) on device 179:2. > > <6>Freeing init memory: 144K > > Freeing init memory: 144K > > <4>Warning: unable to open an initial console. > > Warning: unable to open an initial console. > > <0>Kernel panic - not syncing: Attempted to kill init! > > Kernel panic - not syncing: Attempted to kill init! > > > On Nov 22, 6:46 pm, Srikant <[email protected]> wrote: > > > Hi Shivappa, > > > > > Kernel panic - not syncing: Attempted to kill init > > > > Can you post the Kernel messages before going to panic. > > > > Regards, > > > Sreekanth > > > > On Nov 21, 5:08 pm, Shivappa <[email protected]> wrote: > > > > > Hi, > > > > > I am working on TI’s OMAP Zoom2 platform (OMAP3430). My intention is > > > > to boot Zoom2 with Android using 2.6.31 kernel. Note that I am also > > > > planning to post this in omapzoom discussion group. I think the issue > > > > is not related to platform (zoom2) but to do with Android images with > > > > Linux kernel 2.6.31 and hence posting it here as well. > > > > > Here is how I have extracted android patches > > > > > 1. Took vanilla 2.6.29 from kernel.org > > > > 2. Took Android 2.6.29 kernel fromhttp:// > > android.git.kernel.org/?p=kernel/common.git;a=shortlog;h=refs/... > > > > 3. Took the diff between 1 and 2 > > > > 4. Extracted only the android patches (ashmem, android timer, > > > > everything in staging, yaffs2 etc..) > > > > 5. Applied the android patches to OMAP tree OMAP zoom2,3430 with > > Linux > > > > 2.6.31 kernel > > > > > What is the current state?: > > > > > I am able to boot the kernel with Android patches with a file system > > > > just busybox in it. During bootup I could see some console messages > > > > related to Android (like: ashmem initialized , yaffs2 etc.. ). Also, > > > > in /proc, I can see entries related to binder. > > > > > What is the issue I am facing? : > > > > > When I try to boot the kernel with Android images, the kernel panics > > > > with the following error message > > > > > Kernel panic - not syncing: Attempted to kill init > > > > > Questions I have: > > > > > 1. Do I need to rebuild Android images (especially bionic) with > > the > > > > kernel header files of 2.6.31 ? > > > > 2. What all additional changes I have to make to boot with Android > > > > images > > > > > I appreciate your help.. > > > > > Regards > > > > Shivappa > > > -- > > unsubscribe: > > [email protected]<android-porting%[email protected]> > > website:http://groups.google.com/group/android-porting -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
