I have tried to debug this and found that the kernel is in the
cpu_idle() routine which is repeatedly calling default_idle() and
safe_halt(). If you then type a character on the console, using a
scope, you can see the interrupt being serviced and a character
being taken from the RX fifo, quickly. However there is no
response for some seconds. I have also noticed that if you keep the
thing busy with a benchmark or something simple like ls -lR there is
no pause.
I noticed that to get out of this loop the kernel is looking for a
process to schedule. It is as if the process is not being scheduled
as soon as it could be.
One point to consider is that this board has no RTC or CTC just the
timer wired to a 10ms interrupt.
I suspect that this is a hardware problem but I don't really know
where to start looking. Can anyone help ?
Many thanks
Simon.
__________________________
Simon Haynes - Baydel
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/