Unfortunately I did not keep those traces. What I remember is the first "init" process that triggers the "SWI 0" instruction did not resume. This causes the kernel panic. We traces into the vector_swi handler, and realize that we did not configure EABI for our target. As soon as, we turn the option on, we succeed the kernel post-init. In other words, we succeeded the Android user init.
Before we made the change, we always got "illegal instruction" exception. I hope it would help. Neil --- On Thu, 6/4/09, Vinay Rao <[email protected]> wrote: > From: Vinay Rao <[email protected]> > Subject: [android-porting] Re: init process unknown instruction call > To: [email protected] > Date: Thursday, June 4, 2009, 7:48 AM > > Can you post your strace log?? > > On 6/3/09, Neil Nguyen <[email protected]> > wrote: > > > > > > I have the same issue but it is my kernel > configuration. > > I did not have CONFIG_EABI and CONFIG_OABI_COMPAT > turned on. > > You give it a try and see if it helps. > > Neil > > > > --- On Wed, 6/3/09, sathish kumar <[email protected]> > wrote: > > > >> From: sathish kumar <[email protected]> > >> Subject: [android-porting] init process unknown > instruction call > >> To: [email protected] > >> Date: Wednesday, June 3, 2009, 4:50 AM > >> > >> strace log of Android init process gives unknown > system > >> call. > >> Have anyone faced such issues while porting > Android > >> different platforms? > >> > >> -- > >> sathish > >> > >> > > >> > > > > > > > > > > > > > > > > -- > VINAY.R.RAO > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
