Android Porting to s3c6400 - futex() system call Timedout - Continuously

[ajay]

Hi all



I am porting the android onto s3c6400.



I referred the procedures mentioned in the following websites
before starting the porting



http://benno.id.au/blog/2007/11/21/android-neo1973



http://euedge.com/blog/2007/12/06/google-android-runs-on-sharp-zaurus-sl-c760/



- http://elinux.org/Android_on_OMAP





I am using the Linux-2.6.23 kernel version

I used the M3-rc20 android patch from benno's blog

My Board is ArmV6 compatible.



Root file system is YAFFS2.



Since I do not have sufficient memory to keep all android file
systems on to the Board, I used the NFS, to place the android File
systems in a directory in my desktop machine ( The shared directory in
my desktop machine is ext2fs).



The Board is enabled with the eth0 and loopback network
interfaces.



Now the problem is that, once I started the android shell script
( a.sh ) I am getting only the black screen.

Using the strace, I compared the log generated with the log
reported by Benno in his blog and found that the following are the
differences:





1)

12:18:37.500223 socket(PF_FILE, SOCK_STREAM, 0) = 3

12:18:37.502357 connect(3,
{sa_family=AF_FILE,path=@property_service}, 19) = -1

ECONNREFUSED (Connection
refused)



2)

After some time the log repeats only the following
statements:



[pid 859] 12:21:13.012556 clock_gettime(CLOCK_MONOTONIC,
{267, 176202000}) = 0

[pid 859] 12:21:13.013456 clock_gettime(CLOCK_MONOTONIC, {267,
177085000}) = 0

[pid 859] 12:21:13.014337 clock_gettime(CLOCK_MONOTONIC, {267,
177963000}) = 0

[pid 859] 12:21:13.015230 futex(0x134ac, FUTEX_WAIT, -3, {4,
998000000})





In the group I saw some of the developers got the same problem
during porting, but I did’nt find the solution.

Thank you for any help or suggestions from the group





Regards

Ajay

[ananth]

[Prathapnirmal]

Hi Ajay,
  The second parameter should be the socket address. I think in your case the target socket is either not listening for connections or not accepting the connect call from the specific client. I think the clock and fast user space mutex (futex) calls are not related to this. They might be just the logs of programs that run after the connect call. Hope this helps, to find the actual problem.

thanks
~
Prathap
US - 408 802 9567
India - 91 99465 56643
http://prathapnirmal.in
"Be the change that you wish to see in this world"
"Love and Compassion are not Luxuries, they are Necessities"

[Porting beginner]

On Mon, Sep 29, 2008 at 3:24 AM, ajay <mekaa...@gmail.com> wrote:

Hi,

I am facing same problem.

00:44:05 clock_gettime(CLOCK_MONOTONIC, {2645, 585937000}) = 0
00:44:05 clock_gettime(CLOCK_MONOTONIC, {2645, 585937000}) = 0
00:44:05 clock_gettime(CLOCK_MONOTONIC, {2645, 585937000}) = 0
00:44:05 clock_gettime(CLOCK_MONOTONIC, {2645, 585937000}) = 0
00:44:05 futex(0x125e4, FUTEX_WAIT, 0, {5, 0}) = -1 ETIMEDOUT (Connection timed
out)
00:44:10 clock_gettime(CLOCK_MONOTONIC, {2650, 585937000}) = 0
00:44:10 clock_gettime(CLOCK_MONOTONIC, {2650, 585937000}) = 0
00:44:10 clock_gettime(CLOCK_MONOTONIC, {2650, 585937000}) = 0
00:44:10 clock_gettime(CLOCK_MONOTONIC, {2650, 585937000}) = 0
00:44:10 futex(0x125e4, FUTEX_WAIT, 0, {5, 0}

Any suggestion ?

Thanks
 

[Ananth M]

Hi Pratap

The problem was resolved by enabling the some more network options
in the kernel.
Anyway, thank you for the update

Regards
Ajay

[Porting beginner]

If we dont want network then ... is this problem because of network services not configured ?

Thanks

[Porting beginner]

Can you plz share which network options you enabled in kernel ?

Thanks

On Fri, Oct 10, 2008 at 2:22 AM, Ananth M <mekaa...@gmail.com> wrote: