From: Ed Vance <EdV@macrolink.com>
To: "'dchristian@mail.arc.nasa.gov'" <dchristian@mail.arc.nasa.gov>
Cc: linux-kernel@vger.kernel.org
Subject: RE: 2.4.18 serial drops characters with 16654
Date: Wed, 11 Sep 2002 07:28:45 -0700 [thread overview]
Message-ID: <11E89240C407D311958800A0C9ACF7D13A7992@EXCHANGE> (raw)
On Tue, September 10, 2002 at 3:22 PM, Dan Christian wrote:
> I've got a 2.4.18-10 (RedHat) running on a 2 processor Athlon (1.5Ghz).
> If I send data over a PCI 16654 serial card (Connect Tech Blue Heat) and
> RTSCTS flow control is used, characters are dropped. The drops are
> pretty consistent. As far as I can tell, the data can only be lost in
> the driver (I'm re-trying the write until all the data gets out).
>
> If I use a 16550, then everything is fine. Unfortunately, I can't get
> rid of the 16654s.
>
> If is use a 1 processor Athlon running 2.4.9-34 (RedHat), then
> everything is fine.
>
> I haven't been about to test the 2.4.18 SMP system in single processor
> mode, because the IO-APIC goes nuts. But that's another bug...
>
> Anybody know why the serial driver is losing data?
>
> I'm not on linux-kernel, so please reply directly.
Hi Dan,
We use Exar ST16C654D chips on a cPCI 16-port mux we build and have not
(yet) had a problem report on it for this. Maybe I can reproduce the symptom
on this board. What vendor marking is on your UARTs? Could you tell me more
about your test setup and specifically how often data is dropped and how
many characters are dropped each time? What kind of device is receiving the
data and how much receive FIFO does it have left when it drops RTS to tell
the Blue Heat to stop?
Best regards,
Ed
----------------------------------------------------------------
Ed Vance serial24 (at) macrolink (dot) com
Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
----------------------------------------------------------------
next reply other threads:[~2002-09-11 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 14:28 Ed Vance [this message]
2002-09-11 23:12 ` Andreas Steinmetz
2002-09-12 8:20 ` Alan Cox
2002-09-19 17:27 ` Dan Christian
2002-09-19 17:38 ` Alan Cox
2002-09-19 18:01 ` Russell King
2002-09-19 18:38 ` Dan Christian
2002-09-19 18:24 ` Dan Christian
2002-09-19 18:42 ` Alan Cox
2002-09-19 18:43 ` Russell King
2002-09-12 14:55 ` Stuart MacDonald
-- strict thread matches above, loose matches on Subject: below --
2002-09-10 22:22 Dan Christian
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=11E89240C407D311958800A0C9ACF7D13A7992@EXCHANGE \
--to=edv@macrolink.com \
--cc=dchristian@mail.arc.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®