Re: [linux-usb-devel] 2.6.0-test4 - PL2303 OOPS - see also 2.4.22: OOPS on disconnect PL2303 adapter

From: Jan-Benedict Glaw
Date: Sat Sep 06 2003 - 05:56:21 EST


On Sat, 2003-09-06 15:55:46 +0800, Michael Frank <mhf@xxxxxxxxxxxxx>
wrote in message <200309061555.47065.mhf@xxxxxxxxxxxxx>:
> On Saturday 06 September 2003 15:38, Jan-Benedict Glaw wrote:
> > On Fri, 2003-09-05 16:08:52 -0700, Greg KH <greg@xxxxxxxxx>
> > wrote in message <20030905230852.GA18196@xxxxxxxxx>:
> > > On Wed, Sep 03, 2003 at 02:32:16PM +0800, Michael Frank wrote:
> > > > On Wednesday 03 September 2003 07:52, Greg KH wrote:
> > > > Sep 3 12:52:15 mhfl2 kernel: ttyUSB0: 1 input overrun(s)
> > > > Sep 3 12:54:30 mhfl2 last message repeated 2 times
> > >
> > > Hm, what is causing this?
> > > That is probably why cu is getting confused, right?
> >
> > I've seen the input overrun message also (with the vanilla driver, not
> > patched).
> > It's effect is that the first bytes (maybe up to 100..300
> > bytes) are scrambled. It's like accessing a serial link with a horribly
> > wrong baud rate.
>
> I have seen that too, but rarely. Most the time it hangs after the first
> few hundred bytes.

I've never seen that. My impression is that this (only?) happens if
there are some bytes received from serial, but not read out from
userspace. For NMEA, this is mostly always the case because the GPS
receiver is sending data all the time:)

MfG, JBG

--
Jan-Benedict Glaw jbglaw@xxxxxxxxxx . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

Attachment: pgp00001.pgp
Description: PGP signature