Comment 10 for bug 1205353

when it comes down to the clock_gettime(), poll() and read() system calls one needs to identify the thread PID and then probably attach gdb to find out where in the code it is calling these particular system calls. I'm not really able to explain why it's only happening on ARM, but since one can trap all this activity in userspace I doubt the underlying cause is a kernel issue.