[android-internals] Re: Android on i.MX31 yaffs2 problem - Markus - com.googlegroups.android-internals

5 messages in com.googlegroups.android-internals[android-internals] Re: Android on i....

From	Sent On	Attachments
trustchen	26 Jul 2008 08:14
Markus	28 Jul 2008 02:00
deepak singal	29 Jul 2008 05:07
Markus	30 Jul 2008 03:57
Markus	06 Aug 2008 05:02

Subject:	[android-internals] Re: Android on i.MX31 yaffs2 problem
From:	Markus (vi...@in.tum.de)
Date:	07/30/2008 03:57:15 AM
List:	com.googlegroups.android-internals

active tran sactions 0, buffers 2, pages 1 e_group_exit: 1767 leader 1752 PANIC: handle_group_exit: 1755 leader 1752 PANIC: handle_group_exit: 1756 leader 1752 PANIC: handle_group_exit: 1758 leader 1752

whats this error: PANIC:handle_group_exit ??? Any clue to track the problem ???

Hi,

we do not get those PANICs, seems like your problem is something different than our problem.

Based on my experiences with Linux, PANIC is quite often something with the kernel, like missing modules/drivers for a requested feature or buggy drivers/modules. Did you check, if you compiled all the drivers specified here: http://elinux.org/Android_on_OMAP#Kernel_configuration ? I did not need to port all the energy stuff to get Android running per NFS, if those parts are making troubles. And did you integrate the freescale kernel patches to your own Android kernel? Mostly it is easier to take the provided kernel and extend it by the Android stuff. And you should also check, that those parts that you fixed manually, are right. Maybe you used a wrong pointer?

You should also try to boot directly to Android. Did you try to boot per NFS?