G2 writes:
>
> Hello,
>
> I'm using Android on an OMAP3530 board and I have a problem as
> described by the log below. The same rootfs (Android 1.6) was working
> on my previous custom 2.6.29 kernel. Since I upgraded to 2.6.32, the
> system resets itself because of servicemanager is killed by t
>From the return values, it looks like everything is segfaulting (0xb
== 11 == SIGSEGV). You can look in /data/tombstones for the traces or
you can launch init via strace /system/xbin/strace -F -tt -s 200 -o /
data/strace /init. It should give you some hints.
On Apr 15, 5:42 pm, Gregoire Gentil w
On Fri, 2010-04-16 at 01:59 +0530, Deva R wrote:
> Hi,
>
> > I'm using Android on an OMAP3530 board
> may i know what board you are working on? curious because android
> ports are readily available for most of omap3530 boards (but probably
> 2.6.29 kernel)
It's the Touch Book from http://www.alwa
Hi,
> I'm using Android on an OMAP3530 board
may i know what board you are working on? curious because android ports are
readily available for most of omap3530 boards (but probably 2.6.29 kernel)
Thanks,
Deva
On Fri, Apr 16, 2010 at 1:56 AM, Deva R wrote:
>
> add 'ignore_loglevel' to bootargs.
add 'ignore_loglevel' to bootargs., so as to print all printk traces in
kernel.,
there will be lot of traces, but you will get nice hints to debug..
alternatively, you can use below commands to control printk trace
levelRN_INFO
#echo 8 > /proc/sys/kernel/printk
(by default, only KERN_ERR traces ar
On Apr 15, 2:42 am, Deva R wrote:
> Hi,
> what is the filesystem partition size being used?
>
> >[ 246.085876] EXT3-fs (mmcblk0p2): using internal journal
> >[ 246.091949] EXT3-fs (mmcblk0p2): recovery complete
> >[ 246.112457] EXT3-fs (mmcblk0p2): mounted filesystem with writeback
> >data mo
