From: Roger Davis <rogerdavis@verizon.net>
To: linux-serial@vger.kernel.org
Subject: Linux Serial Code Problems
Date: Wed, 04 Sep 2013 18:38:56 -0500 (CDT) [thread overview]
Message-ID: <30148664.203459.1378337936840.JavaMail.root@vznit170080> (raw)
On Mon, Sep 02, 2013 at 06:14:30PM -0500, Roger Davis wrote:
I have been pursuing a serial port problem for over a year, using Ubuntu 12.04.
I reported it on 2012-12-07, and the bug was confirmed soon after that. I'm not
sure if the root cause is in the basic Linux kernel, or if it is only in Ubuntu.
Others are having problems with similar modems.
The exact same computer and modem (USR 5610C, PCI, 16550 chip, Linux
compatible, http://www.usr.com/products/modem/modem-comparison.asp , with
integral controller and serial port, NOT a Wimmodem ) works just fine in
Windoze. I switch OS's by hardwire switches in removable drive trays, so it is
really the exact very same computer, not just another one of the same spec.
The serial port ttyS4 seems to be detected, but yet not detected, and not
usable by the modem. IRQ 17 also seems to behave oddly. I suspect that internal
modems with both controller and integral serial ports have been kinda
"overlooked" during coding, so the code gets confused and stumbles?
There has been no fix action since I reported it, and the bug is still
unassigned.
Please see confirmed bug " https://bugs.launchpad.net/ubuntu/+bug/1087519 " for
much more details.
next reply other threads:[~2013-09-05 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 23:38 Roger Davis [this message]
2013-09-05 2:43 ` Linux Serial Code Problems Greg KH
2013-09-05 3:06 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2013-09-05 7:57 Roger Davis
2013-09-05 13:30 ` Theodore Ts'o
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=30148664.203459.1378337936840.JavaMail.root@vznit170080 \
--to=rogerdavis@verizon.net \
--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).