Help, Can only run to red startup bar, Could not start up to the mainscreen.

[Raymond]

Hi
I am just trying to port android to my platform with 2.6.21 kernel.
I add all the android's drivers to my kernel, except for the lowmemory
killer.
I can run up to the red startup bar, but never goes to the main
screen.

It shows like:

# /bin/strace_android -ff -F -tt -s 200 -o /tmp/strace /init
init: HOW ARE YOU GENTLEMEN
init: reading config file
init: device init
init: mtd partition -1,
init: mtd partition 0, "bootloade
init: mtd partition 1, "params"
init: mtd partition 2, "kernel"
init: mtd partition 3, "filesyste
init: mtd partition 4, "Mass"
sh: can't access tty; job control turned off
# binder_open(c06849f8 c0703c00) (pid 470) got c001e000


# # # binder_open(c06849f8 c6a04a40) (pid 477) got c7fe7000
android_power: auto off timeout set to 604800 seconds
tsdev (compaq touchscreen emulation) is scheduled for removal.
See Documentation/feature-removal-schedule.txt for details.
PANIC: handle_group_exit: 479 leader 470
PANIC: handle_group_exit: 493 lebinder_release(c06849f8 c0703c00) (pid
483) pd c001e000
ader 470
PANIC: handle_group_exit: 510 leader 470
PANIC: handle_group_exit: 483 leader 470
pid 477 stray syscall exit
pid 496 stray syscall exit
pid 484 stray syscall exit
pid 500 stray syscall exit
pid 501 stray syscall exit
PANIC: handle_group_exit: 480 leader 477
PANIC: handle_group_exit: 481 leader 477
PANIC: handle_group_exit: 492 leader 477
PANIC: handle_group_exit: 495 leader 477
PANIC: handle_group_exit: 502 leader 477
PANIC: handle_group_exit: 478 leader 477
PANIC: handle_group_exit: 506 leader 477
PANIC: handle_group_exit: 507 leader 477
PANIC: handle_group_exit: 509 leader 477
PANIC: handle_group_exit: 508 leader 477
pid 477 stray syscall exit
pid 496 stray syscall exit
pid 484 stray syscall exit
PANIC: handle_group_exit: 491 leader 477
....


I notice that the startup bar runs much faster then it is on the
simulator. and a process called system_server use up almost 99% of the
CPU.

I use benno's filesystem, and 2x the fb virtual_yres , the log,
binder, power driver seems work fine.
Is there anything I miss to run up the system ? Any clue is welcome.

Thanks.

[Raymond]

seems that this part of strace information is showing the error:

14:19:18.246489 getpriority(PRIO_PROCESS, 0) = 25
14:19:18.247537 ioctl(7, 0xc0186201, 0x101ffda8) = 0
14:19:18.251421 ioctl(7, 0xc0186201, 0x101ffef8) = 0
14:19:18.260346 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
14:19:18.261953 sigaction(SIGUSR1, {SIG_IGN}, {SIG_DFL}, 0) = 0
14:19:18.263555 gettid() = 614
14:19:18.264541 socket(PF_FILE, SOCK_STREAM, 0) = 8
14:19:18.265620 connect(8, {sa_family=AF_FILE,
path=@android:debuggerd}, 20) = 0
14:19:18.267182 write(8, "f\2\0\0", 4) = 4
14:19:18.268319 read(8, 0x101ffa8c, 1) = ? ERESTARTSYS (To be
restarted)
14:19:19.113162 +++ killed by SIGKILL +++

but, why is there a Segmentation fault ?

[Raymond]

Since I find that the sigsegv always occur after an ioctl to the
binder driver
so , today, I try to enable the debug of the openbinder
on runtime startup, the binder driver print out a lot of debug
messages....
this time I wait for 30 minutes, no sigsegv occur
I wait and wait .... after I have a lunch the system finally boot into
the main screen.....

Really strange,
no idea how track the problem .....

> > Thanks.- 隐藏被引用文字 -
>
> - 显示引用的文字 -

[Anil Sasidharan]

Hi,

           Does it mean that you are able to view the Android home screen just by enabling the debug traces in binder driver?

Warm Regards,
Anil

2008/2/22 Raymond <rgbb...@gmail.com>:

[Liu Raymond]

Yes, I successed twice by this way.

But I could not find any clue from this fact up to now

 

在08-2-26，Anil Sasidharan <ani...@gmail.com> 写道：