Re: "pon" fails and gives "ttyS overrun" in syslog

From: Al Hayes (ashayes_at_gto.net)
Date: 07/06/04 

Date: 6 Jul 2004 09:18:54 -0700

gerg@panix.com (Greg Andrews) wrote in message news:<ccd79b$c55$1@reader2.panix.com>...
> Isn't this one of the risks of using a non-stable version?

Sure, I guess. Although with Debian, there are three versions:
   stable, testing, and experimental

"testing" has the occasional hiccups but it's "experimental"
that is subject to the serious problems.
Using "testing" helps to shake out bugs and gives one the opportunity
to try out the wide range of free software that is available.
So both oneself and the community benefits.

Indeed, the kind of serious problem that I am currently
is quite rare under testing. Also, the problem is quite mystifying.
There seems to be some unusal combination and, if one thinks about it,
such problems also occur on the supposedly stable systems.

As to my current situation, I have done searches against both google
and against Debian's bug tracking system.
However, I have yet to find anything useful.

Perhaps I need to ask an even lower-level questions.
What _is_ this "overrun" problem that I describe at the start of the thread?
How can such basic functionality mess up?
Surely, there has to be some way to track down this problem.
So any guesses/ideas out there? What could possibly be triggering
these "overrun" problems?