From: Theodore Ts'o <tytso@mit.edu>
To: Bob Bell <bbell@users.sourceforge.net>
Cc: linux-serial@vger.kernel.org
Subject: Re: Serial driver related problems on Linux
Date: Mon, 14 Mar 2005 21:11:28 -0500 [thread overview]
Message-ID: <20050315021128.GC15418@thunk.org> (raw)
In-Reply-To: <20050310154125.GB12846@magick.macroped.net>
On Thu, Mar 10, 2005 at 10:41:27AM -0500, Bob Bell wrote:
>
> I'm contacting you because I'm experiencing a problem on Linux with a
> serial line, and I've traced the problem as far as the Linux kernel.
> I'm hoping that this is the best way to further troubleshoot this
> problem; I noted that Ted T'so is listed as the maintainer for the 2.4
> series (I'm running a 2.4.21 kernel) and Russell for the 2.6 series, so
> I'm hoping a message sent to this mailing list gets the attention of
> whomever is currently actively maintaining the serial/tty code.
>
> The user-visible symptoms of this problem are that after typing in a
> username and hitting enter, the serial login prompt hangs. I've traced
> this hang to an ioctl in the login code (TCSETSF, a result of calling
> tcsetattr(,TCSAFLUSH,)). I've further traced that ioctl to being stuck
> in tty_wait_until_sent().
>
> The debugging output has a lot of references to "pts", which is not
> surprising as I'm running `crash`, etc. from an ssh login. Filtering
> those out leaves the following from the time of the login:
> ttyS wait until sent...
> waiting ttyS...(1)
> waiting ttyS...(62)
> interrupted
It's possible this was caused by a lost transmitter interrupt, so the
transmit queue never drained; it's also possible that some UART's are
wired to not signal a transmitter interrupt while the serial port is
flow controlled. In order to figure out what is going on, you'd have
to add debugging logic into the interrupt handler as well (i.e.,
#define SERIAL_DEBUG_INTR).
- Ted
next prev parent reply other threads:[~2005-03-15 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 15:41 Serial driver related problems on Linux Bob Bell
2005-03-15 2:11 ` Theodore Ts'o [this message]
2005-03-17 18:07 ` Bob Bell
2005-03-30 12:49 ` Bob Bell
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=20050315021128.GC15418@thunk.org \
--to=tytso@mit.edu \
--cc=bbell@users.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.