Hi Guys,
The following configurations are not working. I am getting following kernel
panic.
affs: dev is 32505861 name is "mtdblock5"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.5, "mtdblock5"
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs2 filesystem).
Freeing init memory: 120K
Warning: unable to open an initial console.
init: /init.rc: 142: group option accepts at most 6 supp. groups
Ösh: can't access tty; job control turned offinit: starting 'servicemanager'
# init: starting 'mountd'
init: Created socket '/dev/socket/mountd' with mode '660', user '0', group
'1009'
init: starting 'debuggerd'
init: starting 'ril-daemon'
init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001',
group '1000'
init: starting 'zygote'
init: Created socket '/dev/socket/zygote' with mode '666', user '0', group
'0'
init: Created socket '/dev/socket/rild' with mode '660', user '0', group
'1001'
init: starting 'media'
init: cannot find '/system/bin/playmp3', disabling 'bootsound'
init: starting 'dbus'
init: Created socket '/dev/socket/dbus' with mode '660', user '1002', group
'1002'
init: starting 'installd'
init: cannot find '/system/bin/nomadik_init', disabling 'auto1'
init: Created socket '/dev/socket/installd' with mode '600', user '1000',
group '1000'
init: command 'class_start' r=0
init: processing action 0x27790 (property:persist.service.adb.enable=1)
init: starting 'adbd'
init: command 'start' r=0
init: event { 'add', '/class/vc/vcs1', 'vc', '', 7, 1 }
init: event { 'add', '/class/vc/vcsa1', 'vc', '', 7, 129 }
init: event { 'remove', '/class/vc/vcs1', 'vc', '', 7, 1 }
init: event { 'remove', '/class/vc/vcsa1', 'vc', '', 7, 129 }
init: event { 'add', '/class/vc/vcs1', 'vc', '', 7, 1 }
init: event { 'add', '/class/vc/vcsa1', 'vc', '', 7, 129 }
init: event { 'remove', '/class/vc/vcs1', 'vc', '', 7, 1 }
init: event { 'remove', '/class/vc/vcsa1', 'vc', '', 7, 129 }
init: event { 'add', '/class/vc/vcs1', 'vc', '', 7, 1 }
init: event { 'add', '/class/vc/vcsa1', 'vc', '', 7, 129 }
init: event { 'remove', '/class/vc/vcs1', 'vc', '', 7, 1 }
init: event { 'remove', '/class/vc/vcsa1', 'vc', '', 7, 129 }
init: event { 'add', '/kernel/uids/1000', 'uids', '', -1, -1 }
init: event { 'add', '/kernel/uids/1002', 'uids', '', -1, -1 }
init: event { 'add', '/kernel/uids/1001', 'uids', '', -1, -1 }
warning: `rild' uses 32-bit capabilities (legacy support in use)
Kernel panic - not syncing: Attempted to kill init!
I apologize for wrong information.
Only the compilation is succeeded while boot I am getting the above kernel
panic.
With or without the following changes in linux-arm.mk, if I compile the
android package with ARMv6 toolchain the above kernel panic is observed. So
linux-arm.mk changes are not affecting the compilation.
with logcat I am getting following information:
# logcat &
# I/DEBUG ( 1552): debuggerd: Apr 2 2009 22:41:19
D/mountd ( 1551): AddMountPoint device: /dev/block/mmcblk0, mountPoint:
/sdcard driverStorePath: /s
ys/devices/platform/usb_mass_storage/lun0/file
E/mountd ( 1551): could not read initial mass storage state
D/mountd ( 1551): USB offline
D/mountd ( 1551): RequestMount /sdcard
# D/AndroidRuntime( 1554):
D/AndroidRuntime( 1554): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1554): CheckJNI is ON
E/dalvikvm( 1554): Bad asm sizeof sizeofGlobal_debuggerActive (4), should be
1
E/dalvikvm( 1554): Bad asm sizeof sizeofClassStatus (4), should be 1
E/dalvikvm( 1554): Bad asm sizeof sizeofClassStatus (4), should be 1
E/dalvikvm( 1554): Bad asm sizeof sizeofMethodType (4), should be 1
E/dalvikvm( 1554): Please correct the values in mterp/common/asm-constants.h
E/dalvikvm( 1554): VM aborting
I/DEBUG ( 1552): *** *** *** *** *** *** *** *** *** *** *** *** *** ***
*** ***
I/DEBUG ( 1552): Build fingerprint:
'generic/generic/generic/:1.5/MAIN/eng.manishsh.20090402.21385
1:eng/test-keys'
I/DEBUG ( 1552): pid: 1554, tid: 1554 >>> zygote <<<
I/DEBUG ( 1552): signal 11 (SIGSEGV), fault addr deadd00d
I/DEBUG ( 1552): r0 00000320 r1 0000000c r2 0000000c r3 00000026
I/DEBUG ( 1552): r4 deadd00d r5 ad06a964 r6 00000004 r7 00000001
I/DEBUG ( 1552): r8 ad084e04 r9 00000000 10 ad069f44 fp 00000000
I/DEBUG ( 1552): ip ad084ee0 sp bef0f7b0 lr afe13f8d pc ad03b6ca cpsr
20000030
I/DEBUG ( 1552): #00 pc 0003b6ca /system/lib/libdvm.so
I/DEBUG ( 1552): #01 pc 00017b00 /system/lib/libdvm.so
I/DEBUG ( 1552): #02 pc 0003c94e /system/lib/libdvm.so
I/DEBUG ( 1552): #03 pc 00040fc2 /system/lib/libdvm.so
I/DEBUG ( 1552): #04 pc 00028f58
/system/lib/libandroid_runtime.so
I/DEBUG ( 1552): #05 pc 00008bf2 /system/bin/app_process
I/DEBUG ( 1552): #06 pc 0Kernel panic - not syncing: Attempted
to kill init!
001fe22 /system/lib/libc.so
I/DEBUG ( 1552): #07 pc 0000bc22 /system/lib/libc.so
I/DEBUG ( 1552): #08 pc b0001424 /system/bin/linker
I/DEBUG ( 1552): stack:
I/DEBUG ( 1552): bef0f770 0000000a
I/DEBUG ( 1552): bef0f774 00000000
I/DEBUG ( 1552): bef0f778 afe37f94
I/DEBUG ( 1552): bef0f77c afe37fe8
I/DEBUG ( 1552): bef0f780 00000000
I/DEBUG ( 1552): bef0f784 afe13f8d /system/lib/libc.so
I/DEBUG ( 1552): bef0f788 0000ab58 [heap]
I/DEBUG ( 1552): bef0f78c afe12fa9 /system/lib/libc.so
I/DEBUG ( 1552): bef0f790 ad348f40 /system/lib/libandroid_runtime.so
I/DEBUG ( 1552): bef0f794 ad084e04
I/DEBUG ( 1552): bef0f798 ad06a964 /system/lib/libdvm.so
I/DEBUG ( 1552): bef0f79c 00000004
I/DEBUG ( 1552): bef0f7a0 00000001
I/DEBUG ( 1552): bef0f7a4 afe1300d /system/lib/libc.so
I/DEBUG ( 1552): bef0f7a8 e3a07077
I/DEBUG ( 1552): bef0f7ac ef900077
I/DEBUG ( 1552): #00 bef0f7b0 ad06a9a8 /system/lib/libdvm.so
I/DEBUG ( 1552): bef0f7b4 ad017b04 /system/lib/libdvm.so
I/DEBUG ( 1552): #01 bef0f7b8 00000004
I/DEBUG ( 1552): bef0f7bc 00000001
I/DEBUG ( 1552): bef0f7c0 0000a938 [heap]
I/DEBUG ( 1552): bef0f7c4 ad085ac8
I/DEBUG ( 1552): bef0f7c8 00000320
I/DEBUG ( 1552): bef0f7cc 00000000
I/DEBUG ( 1552): bef0f7d0 ad084e04
I/DEBUG ( 1552): bef0f7d4 00000000
I/DEBUG ( 1552): bef0f7d8 00000000
I/DEBUG ( 1552): bef0f7dc ad03c951 /system/lib/libdvm.so
The same code base works fine with arm-eabi toolchain.
Thanks and Regards,
MS
On Thu, Apr 2, 2009 at 8:36 PM, Manish Sharma <[email protected]>wrote:
> Hi All,
>
> Further on this topic. I have updated the build/core/combo/linux-arm.mkfile
> with following rules.
>
> TARGET_ARCH_VERSION := armv6
>
> RULES for ARMv6:
>
> ifeq ($(TARGET_ARCH_VERSION),armv6)
> $(warning ARMv6 support added)
> ARCH_ARM_HAVE_THUMB_SUPPORT := true
> ARCH_ARM_HAVE_THUMB_INTERWORKING := true
> ARCH_ARM_HAVE_64BIT_DATA := true
> ARCH_ARM_HAVE_HALFWORD_MULTIPLY := true
> ARCH_ARM_HAVE_CLZ := true
> ARCH_ARM_HAVE_FFS := true
> arch_version_cflags := -march=armv5t -Wa,-march=armv6 -D__ARM_ARCH_6__
> After this compiled with ARMv6 toolchain. Compilation was successful and I
> am able to get the android desktop.
>
> Can someone confirm the changes mentioned above are sufficient and correct?
>
> Regards,
> MS
> On Tue, Mar 31, 2009 at 9:14 AM, Manish Sharma <[email protected]
> > wrote:
>
>> Hi Fadden,
>> No! it is working fine with the current rules. Still I would like to use
>> armv6 compilation rules.
>> Regards,
>> MS
>>
>> On Tue, Mar 31, 2009 at 1:14 AM, fadden <[email protected]> wrote:
>>
>>>
>>> On Mar 27, 11:30 pm, Manish Sharma <[email protected]> wrote:
>>> > I have got information from this mailing list that to compile android
>>> > package for armv6 we need to modify the linux-arm.mk and add rules for
>>> > building ARMv6. Are these rules available with someone? Please share
>>> the
>>> > rules/info it would be of great help.
>>>
>>> Is it failing to compile with the current rules?
>>>
>>> >>>
>>>
>>
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
