From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: linux-serial@vger.kernel.org
Cc: Len Sorensen <lsorense@csclub.uwaterloo.ca>,
linux-kernel@vger.kernel.org,
Breno Leitao <leitao@linux.vnet.ibm.com>
Subject: Very strange data loss with jsm driver
Date: Fri, 29 Jul 2011 12:04:16 -0400 [thread overview]
Message-ID: <20110729160416.GK8562@caffeine.csclub.uwaterloo.ca> (raw)
I discovered a strange situation where the jsm driver discards the
majority of transmit data.
I have two text files.
The first file consists of 9100 lines of:
0123456789<newline>
Total 100100 bytes.
The second file consists of 100 lines of:
01234567890123456789.....0123456789<newline> (1000 character line)
Total 100100 bytes.
The first file transmits instantly, with the receiving end getting
approximately 100 bytes of the data.
The second file sends in about 1 minute and 40 seconds at 9600 baud
(the speed doesn't affect the behaviour in any noticeable way) as one
would expect, and the other end sees all the data.
The trigger point appears to be lines of up to 14 bytes, followed by
a newline. With 15 bytes or more per line it seems to be OK.
Anyone got a clue?
I was testing on 3.0.0. Same on 2.6.32.
3.0.0 unfortunately no longer has port statistics on the jsm driver in
/proc/tty/driver/jsm making it hard to see what the driver believes is
going on, it seems 2.6.37 broke that with some serial cleanup.
I am cleaning up a patch to fix that.
--
Len Sorensen
next reply other threads:[~2011-07-29 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 16:04 Lennart Sorensen [this message]
2011-07-29 16:27 ` Very strange data loss with jsm driver Alan Cox
2011-07-29 16:53 ` Lennart Sorensen
2011-07-29 18:06 ` Lennart Sorensen
2011-07-29 18:14 ` Alan Cox
2011-07-29 18:13 ` Lennart Sorensen
2011-08-02 14:17 ` Breno Leitao
2011-08-02 14:22 ` Lennart Sorensen
2011-08-02 14:23 ` Lennart Sorensen
2011-08-02 14:49 ` Breno Leitao
2011-08-02 14:52 ` Lennart Sorensen
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=20110729160416.GK8562@caffeine.csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=leitao@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).