twebb
2008-10-21 19:22:39 UTC
I have an OMAP 35xx based eval board running android when the root
filesystem is mounted via NFS. However, when trying to run with the
identical filesystem burned into flash and mounted via YAFFS2, the
servicemanager always exits...
...
init: waitpid returned pid 492, status =
00007f00
init: process 'servicemanager', pid 492
exited
init: process 'servicemanager' killing any children in process
group
...
and the only indication I get from logcat is...
E/dalvikvm-gc( 483): Could not create 176128-byte ashmem mark stack
I'm not sure if the dalvikvm-gc error is a result of some prior
problem, or the real problem itself. I have ashmem properly
configured and it works when the FS is mounted via NFS, so I don't
believe it's an ashmem problem. The rest of init.rc appears to be
executed just fine. I have my kernel and filesystem arranged to boot
nearly identically to the android emulator. Permissions and
ownerships appear to be OK. Any other ideas as to what might cause
servicemanager to exit in this way? Could it be waiting on something
that somehow doesn't occur (correctly) when running over YAFFS2 versus
NFS?
Thanks,
twebb
filesystem is mounted via NFS. However, when trying to run with the
identical filesystem burned into flash and mounted via YAFFS2, the
servicemanager always exits...
...
init: waitpid returned pid 492, status =
00007f00
init: process 'servicemanager', pid 492
exited
init: process 'servicemanager' killing any children in process
group
...
and the only indication I get from logcat is...
E/dalvikvm-gc( 483): Could not create 176128-byte ashmem mark stack
I'm not sure if the dalvikvm-gc error is a result of some prior
problem, or the real problem itself. I have ashmem properly
configured and it works when the FS is mounted via NFS, so I don't
believe it's an ashmem problem. The rest of init.rc appears to be
executed just fine. I have my kernel and filesystem arranged to boot
nearly identically to the android emulator. Permissions and
ownerships appear to be OK. Any other ideas as to what might cause
servicemanager to exit in this way? Could it be waiting on something
that somehow doesn't occur (correctly) when running over YAFFS2 versus
NFS?
Thanks,
twebb