Thanks Martin,

> Without a message?

I can not say clearly that. I use the the console occasionnaly.
I am running netbsd on a notebook and I _do_ have connected the serial
port to the console of the TS7200.The SBC is running 24/7 but not the noteb=
ook.
Also, sending a BREAK with minicom the SBC goes into the debugger..

To be honest last week I left the notebook also running 24/7 and I did
not noticed any hang until this morning where I had to shut down the
notebook..

I will disconnect the serial cable and see how it will go this week.

Thanks again
Christos

> There are two common cases this happens: (1) in a panic() call, but that
> prints some error message before entering the debugger and (2) when
> receiving a BREAK signal on the serial console. If you power off the
> machine the console is connected to this often causes a break.
>
> > If I type continue in db I get the above message (where xxxx is a
> > number different every time) and everything works fine after the next
> > stale..
>
> The message is nothing to worry about - interrupts are blocked while
> in the debugger, so they are not handled in time and the receiver overrun=
s.
>
> > I am rather new to NetBSD on SBCs' and I do not know how to debug such
> > problems using the debugger.... So any help on this would be greatly
> > appreciated.
>
> The "backtrace" command (bt) gives you a call stack, so you can see where
> you are coming from. This is usualy the first thing you need to know when
> debugging something.
>
> Martin
>