Hello all,
I have a overo gumstix air board with 2.4 linux kernel in it. I have an
application running on it which will talk to two custom char drivers that
I've written. The application has a tcp socket which talks to an outside
server. I frequently noticed that the blue light showing the wifi
connectivity turns off automatically. First I thought that this is something
with the internet connectivity and I wrote a small daemon program to tackle
that. But I got to know then it's not the internet connection, but the whole
system is stuck at that point. So I enabled the watchdog timer thanks to the
great help from readers of this mailing list. Then I started to notice that
my machine keeps on restarting during the runtime of my program. Can this be
something with wrong practice in writing the drivers? Or has anyone seen
this kind of behaviors? Or is there any way I can narrow down what caused
the system stuck condition?
(I'm sorry if this post is not relevant to gumstix, But I'm trying to figure
out where my issue is being generated.)
Thanks all.
--
View this message in context: http://gumstix.8.n6.nabble.com/Overo-Gumstix-Reboot-automatically-frequently-tp4375966p4375966.html
Sent from the Gumstix mailing list archive at Nabble.com.
|