I'm not having much luck in either place.
On Oct 9, 8:48 pm, "Andrew Stadler" <[EMAIL PROTECTED]> wrote: > You'll probably get better feedback on this problem in the > android-internals mailing list. > > On Thu, Oct 9, 2008 at 12:51 PM, twebb <[EMAIL PROTECTED]> wrote: > > > When mounting rootfs as yaffs2, the servicemanager dies/exits almost > > immediately on android startup, and logcat output is shown below. > > However, when mounting same rootfs via NFS, I don't see this problem > > (though I do have other issues). Does the error > > > E/dalvikvm-gc( 483): Could not create 176128-byte ashmem mark stack > > > indicate a specific problem? Might there be a way to dump more > > specific/verbose output at startup to get a better understanding of > > what's wrong? > > > Thanks, > > twebb > > > I/DEBUG ( 481): debuggerd: Aug 14 2008 18:58:32 > > E/mountd ( 480): could not read initial mass storage state > > D/AndroidRuntime( 483): > > D/AndroidRuntime( 483): >>>>>>>>>>>>>> AndroidRuntime START > > <<<<<<<<<<<<<< > > D/AndroidRuntime( 483): CheckJNI is ON > > D/AndroidRuntime( 483): --- registering native functions --- > > I/Zygote ( 483): Preloading classes... > > E/dalvikvm-gc( 483): Could not create 176128-byte ashmem mark stack --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
