Hi,
I am using m5-rc14 kernel along with android-sdk_m5c14 to extract
system and data from emulator.
( diff with linux 2.6.23.1 ( from kernel.org ) and
linux-2.6.23-android-m5-rc14 )
(Apply this diff to my kernel ( 2.6.23), manullay fix which couldnt apply,
there were few).
Only these config ( for android ) in kernel.
CONFIG_ANDROID_POWER=y
CONFIG_ANDROID_POWER_STAT=y
CONFIG_ANDROID_LOGGER=y
CONFIG_ANDROID_BINDER_IPC=y
As I am using only m5-rc14 (2.6.23) , so its not require ASHMEM in kernel,
right ?
I have system and data is on sd card , sd card with ext2 fs.
#./strace -f -ff -t -s 200 /system/bin/runtime
.
.
.
[pid 241] 00:18:34 writev(3, [{"\4", 1}, {"ServiceManager\0", 15},
{"ServiceManager: waiting for service alarm\n\0", 43}], 3) = 59
[pid 241] 00:18:34 clock_gettime(CLOCK_MONOTONIC, {1114, 796875000}) = 0
[pid 241] 00:18:34 clock_gettime(CLOCK_MONOTONIC, {1114, 804687000}) = 0
[pid 241] 00:18:34 clock_gettime(CLOCK_MONOTONIC, {1114, 804687000}) = 0
[pid 241] 00:18:34 futex(0x125e4, FUTEX_WAIT, -14, {4, 992000000}) = -1
ETIMEDOUT (Connection timed out)
[pid 241] 00:18:39 clock_gettime(CLOCK_MONOTONIC, {1119, 796875000}) = 0
[pid 241] 00:18:39 writev(3, [{"\4", 1}, {"ServiceManager\0", 15},
{"ServiceManager: unable to find service alarm\n\0", 46}], 3) = 62
[pid 241] 00:18:39 ioctl(6, 0xc0186201, 0x409ffda8) = 0
[pid 241] 00:18:39 ioctl(6, 0xc0186201, 0x409ffef8) = 0
[pid 241] 00:18:39 getpid() = 226
[pid 241] 00:18:39 getuid32() = 0
[pid 241] 00:18:39 ioctl(6, 0xc0186201, 0x409ffba8) = 0
[pid 241] 00:18:39 ioctl(6, 0xc0186201, 0x409ffba8) = 0
[pid 241] 00:18:39 writev(3, [{"\4", 1}, {"ServiceManager\0", 15},
{"ServiceManager: addService(checkin, 0x13fb8)\n\0", 46}], 3) = 62
[pid 241] 00:18:39 futex(0x125e4, FUTEX_WAKE, 2147483647) = 0
[pid 241] 00:18:39 ioctl(6, 0xc0186201, 0x409ffda8) = 0
[pid 241] 00:18:39 ioctl(6, 0xc0186201, 0x409ffef8) = 0
[pid 241] 00:18:40 ioctl(6, 0xc0186201, 0x409ffda8) = 0
[pid 241] 00:18:40 ioctl(6, 0xc0186201, 0x409ffef8) = 0
[pid 226] 00:18:41 <... ioctl resumed> , 0xbef94bf8) = 0
[pid 241] 00:18:41 ioctl(6, 0xc0186201 <unfinished ...>
[pid 226] 00:18:41 ioctl(6, 0xc0186201 <unfinished ...>
[pid 241] 00:18:41 <... ioctl resumed> , 0x409ffe00) = 0
[pid 241] 00:18:41 writev(3, [{"\4", 1}, {"runtime\0", 8}, {"Grim Reaper
killing runtime...\0", 31}], 3) = 40
[pid 241] 00:18:41 getpid() = 226
[pid 241] 00:18:41 kill(226, SIGKILL) = 0
[pid 226] 00:18:41 <... ioctl resumed> , 0xbef94bf8) = ? ERESTARTSYS (To
be restarted)
[pid 237] 00:18:41 <... ioctl resumed> , 0x408ffef8) = ? ERESTARTSYS (To
be restarted)
[pid 242] 00:18:41 <... ioctl resumed> , 0x40affef8) = ? ERESTARTSYS (To
be restarted)
[pid 241] 00:18:41 +++ killed by SIGKILL +++
PANIC: handle_group_exit: 241 leader 226
Process 241 detached
[pid 237] 00:18:41 +++ killed by SIGKILL +++
PANIC: handle_group_exit: 237 leader 226
Process 237 detached
[pid 242] 00:18:41 +++ killed by SIGKILL +++
PANIC: handle_group_exit: 242 leader 226
Process 242 detached
[pid 234] 00:18:41 <... ioctl resumed> , 0x100ffef8) = ? ERESTARTSYS (To
be restarted)
[pid 234] 00:18:41 +++ killed by SIGKILL +++
PANIC: handle_group_exit: 234 leader 226
Process 234 detached
00:18:41 +++ killed by SIGKILL +++
Process 226 detached
In strace, related to binder, I have seen only two calls, open binder and
then
writev(3, [{"\4", 1}, {"runtime\0", 8}, {"Binder driver opened.
Multiprocess enabled.\n\0", 46}], 3) = 55
Not any other binder related operation , is this fine ?
[pid 241] 00:18:39 writev(3, [{"\4", 1}, {"ServiceManager\0", 15},
{"ServiceManager: unable to find service alarm\n\0", 46}], 3) = 62
is this can be an issue ?
Any clue ?
Thanks again
On Wed, Oct 15, 2008 at 2:11 AM, Markus <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> you should use Android m5-rc14, newer versions will not work without
> updating the kernel to a new release.
>
> bye
> Markus
>
> On 15 Okt., 02:48, "Porting beginner" <[EMAIL PROTECTED]>
> wrote:
> > I am using m5-rc14 kernel, which Android I should use to over come this
> > problem ?
> > My SoC kernel is based on 2.6.23 so right now I want to use m5-rc14 (
> linux
> > 2.6.23 based android ) only.
> >
> > Thanks again.
> >
> > On Tue, Oct 14, 2008 at 2:26 AM, Markus <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> >
> > > are you using m5 kernel with Android 0.9 or 1.0? They are not
> > > compatible, you should use kernel 0.9 or 1.0 (which are equal).
> >
> > > bye
> > > Markus
> >
> > > On 11 Okt., 03:56, "Porting beginner" <[EMAIL PROTECTED]>
> > > wrote:
> > > > Hi,
> >
> > > > I have linux 2.6.23 and used linux-2.6.26-android-m5rc14 as reference
> to
> > > > port
> > > > android changes.
> >
> > > > I am able to port all code, BINDER, LOGGER, LOW_MEMORY_KILL
> successfully.
> > > > Power and ASHMEM related code is not there with 2.6.23.
> >
> > > > When I am starting init , I am getting segmentation fault.
> >
> > > > When I debug using strace, found that it may ASHMEM support from
> kernel.
> > > > So I tried to port ashmem code:
> > >http://git.android.com/?p=kernel.git;a=commit;h=7c93d1ee2eba929ed9496.
> ..
> > > > my kernel (2.6.23).
> >
> > > > When I am trying to compile my 2.6.23 with these changes its failing
> with
> > > > error related to shmem_zero_setup functions declaration.
> >
> > > > I am see the new code added from 2.6.25 ( to my 2.6.23 ), there is
> extern
> > > of
> > > > shmem_zero_setup function, old function had only one arg where
> > > > other new one has two args so old code from ( mm/mmap) still using
> this
> > > > function with one arg and new ( in mm/tinyshmem.c) using
> > > > with two args.
> >
> > > > Whats should I do to overcome this problem ?
> >
> > > > Thanks
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Internals" group.
To post to this group, send email to android-internals@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-internals?hl=en
-~----------~----~----~----~------~----~------~--~---
