From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] 2.6.0-test4 - PL2303 OOPS - see also 2.4.22: OOPS on disconnect PL2303 adapter
Date: Sat, 6 Sep 2003 12:55:23 +0200 [thread overview]
Message-ID: <20030906105523.GF14376@lug-owl.de> (raw)
In-Reply-To: <200309061555.47065.mhf@linuxmail.org>
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
On Sat, 2003-09-06 15:55:46 +0800, Michael Frank <mhf@linuxmail.org>
wrote in message <200309061555.47065.mhf@linuxmail.org>:
> On Saturday 06 September 2003 15:38, Jan-Benedict Glaw wrote:
> > On Fri, 2003-09-05 16:08:52 -0700, Greg KH <greg@kroah.com>
> > wrote in message <20030905230852.GA18196@kroah.com>:
> > > 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@lug-owl.de . +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 #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-09-06 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 17:39 2.6.0-test4 - PL2303 OOPS - see also 2.4.22: OOPS on disconnect PL2303 adapter Michael Frank
2003-09-01 18:53 ` Jan-Benedict Glaw
2003-09-02 16:43 ` [linux-usb-devel] " Greg KH
2003-09-02 22:13 ` Michael Frank
2003-09-02 23:52 ` Greg KH
2003-09-03 6:32 ` Michael Frank
2003-09-05 23:08 ` Greg KH
2003-09-06 2:31 ` Michael Frank
2003-09-06 5:48 ` Greg KH
2003-09-06 8:01 ` Michael Frank
2003-09-06 7:38 ` Jan-Benedict Glaw
2003-09-06 7:55 ` Michael Frank
2003-09-06 10:55 ` Jan-Benedict Glaw [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030906105523.GF14376@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).