From: "Paul Rolland" <rol@as2917.net>
To: <linux-kernel@vger.kernel.org>
Cc: <rol@as2917.net>
Subject: Spy'ing characters sent to serial port.
Date: Wed, 6 Jul 2005 20:36:32 +0200 [thread overview]
Message-ID: <200507061836.j66IaWD27125@tag.witbe.net> (raw)
Hello,
We have a machine connected to a modem using the serial port, and from
time to time, the modem complains the machine sent him a full 2K buffer
(in fact, 2047 bytes) which were already sent.
We've been investigating at the application level, using strace to
monitor what is sent to the serial port, and at no time such a buffer is
sent.
This problem is occuring on a random basis, and attempts to reproduce
it in a test environment failed to date.
Is it possible to '(log|copy|...)' the chars that are sent on the
serial port to some other place (without altering too much the performance
of the machine, we are running the port a 9600bps), at the lowest level ?
Or is there a known issue of the serial port (or tty) buffer being
resent on the line in some weird conditions ? Any change done on
->head and ->tail handling that could fix that ?
This problem is with Linux 2.4.27 (I know 2.4.31 is out, but nothing
related to that is present in the Changelog)
Regards,
Paul
reply other threads:[~2005-07-06 23:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200507061836.j66IaWD27125@tag.witbe.net \
--to=rol@as2917.net \
--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®