From: Lee Howard <faxguy@howardsilvan.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Tilman Schmidt <tilman@imap.cc>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Robert Hancock <hancockr@shaw.ca>,
linux-serial@vger.kernel.org, tytso@mit.edu,
rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: serial flow control appears broken
Date: Fri, 27 Jul 2007 21:51:25 -0700 [thread overview]
Message-ID: <46AACB4D.7080004@howardsilvan.com> (raw)
In-Reply-To: <1185578908.2989.15.camel@x2>
Paul Fulghum wrote:
>So this seems to be a latency issue reading the receive
>FIFO in the ISR. The current rx FIFO trigger level
>should be 8 bytes (UART_FCR_R_TRIG_10) which gives the
>ISR 694usec to get the data at 115200bps.
>
>IIRC, in 2.2.X kernels this defaulted to 4 bytes
>(TRIG_01) which gave a little more time to service the interrupt.
>
>How does the data rate affect the frequency of the overrun errors?
>Does 57600bps make them go away?
>
>
The overrun error message does not occur on every instance of data
corruption. (I just became aware of this as I've not been paying so
much attention to the error messages as I have been to the corrupt
data.) The data gets far more corrupted than the error messages would
lead me to believe. Since the data being sent from the fax modem to the
host is identical (same image data) every time it's easier for me to
measure the effect of one bitrate over another by examining the number
of missing bytes from the data.
The image has a total of 140465 bytes. Just now I sent it 5 times each
at 115200, 57600, 38400, and 19200 bps.
At 115200 bps the number of bytes skipped were: 63, 5, 44, 48, and 2.
At 57600 bps the number of bytes skipped were: 0, 1, 13, 9, and 12.
At 38400 bps the number of bytes skipped were 858, 0, 0, 0, and 8.
At 19200 bps the number of bytes skipped were 0, 0, 0, 0, and 0.
Curiously, the session at 38400 bps that skipped 858 bytes... coincided,
not just in sequence but also in precice timing within the session, with
a small but noticeable disk load that I caused by grepping through a
hundred session logs. (I can't reproduce it easily, though, because of
disk caching.)
And, perhaps this is relevant... the way that I have the fax modem
sending the data to the host is by receiving it from another fax modem
which is sending it. Thus, the modem on ttyS0 is sending a fax to the
modem on ttyS1. Due to the error correction protocol that is performed
between the two fax endpoints I can guarantee that the data is correct
as it leaves the DCE. I mention this in case there is any limitation to
how the 8250 driver performs when two modems are being run simultaneously.
Thanks,
Lee.
next prev parent reply other threads:[~2007-07-28 4:52 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Z6O0xFRT69zes0Mg+agt3Uiwux4@ifi.uio.no>
2007-07-26 7:20 ` serial flow control appears broken Robert Hancock
2007-07-26 16:08 ` Lee Howard
2007-07-26 16:31 ` Alan Cox
2007-07-27 5:53 ` Lee Howard
2007-07-27 11:47 ` Alan Cox
2007-07-27 17:36 ` Lee Howard
2007-07-27 13:45 ` Tilman Schmidt
2007-07-27 19:34 ` Paul Fulghum
2007-07-27 20:48 ` Lee Howard
2007-07-27 23:28 ` Paul Fulghum
2007-07-28 4:51 ` Lee Howard [this message]
2007-07-28 9:18 ` Russell King
2007-07-28 12:00 ` Alan Cox
2007-07-28 15:39 ` Lee Howard
2007-08-01 21:54 ` Frantisek Rysanek
2007-07-28 16:41 ` Ray Lee
2007-08-04 18:21 ` Lee Howard
2007-08-04 22:07 ` Paul Fulghum
2007-08-05 0:00 ` Lee Howard
2007-08-05 14:52 ` Paul Fulghum
2007-07-27 19:34 ` Paul Fulghum
2007-07-27 20:05 ` Lee Howard
2007-07-27 11:32 ` Maciej W. Rozycki
2007-07-27 17:11 ` Lee Howard
2007-07-27 17:41 ` Alan Cox
2007-07-27 17:53 ` Maciej W. Rozycki
2007-07-27 18:11 ` Lee Howard
2007-07-30 9:36 ` Maciej W. Rozycki
2007-07-27 18:22 ` Robert Hancock
2007-07-27 18:46 ` Paul Fulghum
2007-07-27 19:05 ` Paul Fulghum
2007-07-30 9:39 ` Maciej W. Rozycki
2007-07-27 19:14 ` Paul Fulghum
2007-07-28 9:28 ` Russell King
2007-07-30 9:45 ` Maciej W. Rozycki
2007-07-30 9:59 ` Russell King
2007-08-02 14:57 ` Mark Lord
2007-08-02 16:14 ` Robert Hancock
2007-08-02 16:29 ` Mark Lord
2007-08-02 16:40 ` Robert Hancock
2007-08-02 17:13 ` Alan Cox
2007-08-04 19:38 ` Lee Howard
2007-08-02 16:57 ` Alan Cox
2007-08-02 17:02 ` Robert Hancock
2007-08-03 9:32 ` Maciej W. Rozycki
2007-07-30 9:34 ` Maciej W. Rozycki
2007-08-04 18:19 ` Lee Howard
2007-07-26 1:52 Lee Howard
2007-07-26 12:34 ` Uwe Kleine-König
2007-07-26 16:28 ` Lee Howard
2007-07-26 16:41 ` Alan Cox
2007-07-27 6:17 ` Lee Howard
2007-07-27 11:56 ` Alan Cox
2007-07-27 18:00 ` Lee Howard
2007-07-26 15:51 ` Tosoni
2007-07-26 16:31 ` Lee Howard
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=46AACB4D.7080004@howardsilvan.com \
--to=faxguy@howardsilvan.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=rmk@arm.linux.org.uk \
--cc=tilman@imap.cc \
--cc=tytso@mit.edu \
/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).