Thank you Alexander,

I watched memory resources while connecting/disconnecting, but the
system wasn't low on memory.
The crash occurs spontaneously, but it's difficult to say, when exactly,
but sooner or later it eventually will
fail. I connected a serial console, sending all log messages to it, but
there was no indication of an error, logging
just stopped.

Any further ideas?

Dietmar

--- In [email protected], "xfingerfox32" <[EMAIL PROTECTED]> wrote:
>
> Hello Dietmar,
>
> Try to check if you have spawned too many threads making foxboard run
> out of memory.
> Use "top" command and watch the memory in use by your program while
> you connect and disconnect the ethernet cable.
>
> Hope this helps.
>
> Alexander
>
>
> --- In [email protected], "dietmar.dreyer33"
> dietmar.dreyer33@ wrote:
> >
> > Hi all!
> >
> > I encountered a very strange problem on the fox board on kernel 2.4
> > (using Axis Developer Boards/Device Server SDK Release 2.01).
> > I wrote a daemon program that uses libcurl for periodically
> uploading
> > data to an FTP server in several threads (using pthread lib).
> > Up to this point all goes well, the problems begin when pulling the
> > ethernet connection from the foxboard and reconnecting some time
> > later. When telnetting to the fox board sometimes the board seems to
> > freeze, i.e. I receive part of the welcome message (Connected to
> > 192.168.xxx.xxx
> > etc.), but I don't get the actual login prompt and cannot login
> > anymore, as there is no response. Furthermore the blinking red
> status
> > led freezes (blinking is caused by program statusled), halting in a
> > on- or off-state, which seems to indicate, that several programs
> crashed,
> > so I suppose, there might be a kernel problem/ethernet driver
> problem?
> > I noticed, that the fox board still responded to ping requests, but
> in
> > one case, the yellow led also freezed.
> > I wrote syslogs to usb flash disk, but there was no indication of
> any
> > problems.
> >
> > Any ideas, what might be wrong? Thanks a lot!
> >
> > Dietmar
> >
>


Reply via email to