On 11/14/2012 12:48 AM, YongQin Liu wrote:
Hi, Andy & Michael
About the problem that the telnet process consumes CPU(bug1034218
<https://bugs.launchpad.net/linaro-android/+bug/1034218>),
For now I tried two ways to verify it:
1. Run the CTS test via submitting a lava-job
In this way, the process that consumes CPU is telnet
2. Run the CTS test via command line "lava-android-test run cts"
In this way, there is no process that consumes CPU to 100%,
In the meanwhile, I also opened the telnet session.
So I guess the problem is the way we calling the telnet command in
lava-dispatcher.
From my investigation, it's the select syscall in telnet that consumes CPU,
So I doubt if there is some place in lava-dispatcher that reads the
ouput of telnet in a loop without sleep in the loop.
but I did not find such place in lava-dispatcher.
How do you think about it?
Do you get 100% CPU when you run the job by hand, ie "lava-dispatch
jobfile.json"?
This just doesn't make sense. I don't see how the telnet binary's usage
of the "select" API is being influenced by its parent process.
Finally, I feel that this problem is of lava-dispatcher, not the problem
of lava-android-test or CTS,
so can we change it to be a bug of lava-dispatcher?
That's fine. The core problem remains the same. The big question is:
what do we need to try and debug next?
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
