From: Karl Dahlke <eklhad@comcast.net>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Bug in tty cooked mode kernel 3.12.3
Date: Sun, 08 Dec 2013 01:16:09 -0500 [thread overview]
Message-ID: <20131108011609.eklhad@comcast.net> (raw)
In-Reply-To: 20131208053621.GA6445@kroah.com
As per your direction, I applied Peters patch to n_tty.c,
which looked like it was in the ballpark, echoing newline etc,
but it did not fix the problem.
It is still reproducible on my system as below.
> Come up in run level 3, command line mode,
> and bring up two consoles with bash in cooked mode.
> Set a simple prompt like this.
>
> PS1='$ '
>
> Switch to console 2 via alt-f2.
> Hit return.
> The cursor should drop to a new line then give you the $ prompt.
> But it puts the $ prompt next too the old one, then drops down
> to a blank line.
> The $ prompt and the crlf are out of sequence.
> Hit return a few more times and it will straighten itself out.
> Then switch back to console 1 alt-f1
> Hit return and the same bug,
> $ $
>
> hit return a few more times to straighten it out.
> Switch back to console 2 and the same problem.
Thank you for your quick reply,and the patch to try.
I'm afraid however this is still an unsolved problem.
Realize that it pops up rarely and randomly in just about any cooked program;
I chose the console switch example because it most reliably reproduces the bug.
Thank you.
Karl Dahlke
next prev parent reply other threads:[~2013-12-08 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131107184607.eklhad@comcast.net>
2013-12-08 5:36 ` Bug in tty cooked mode kernel 3.12.3 Greg KH
2013-12-08 6:16 ` Karl Dahlke [this message]
2013-12-08 7:18 ` Greg KH
2013-12-09 23:06 ` Peter Hurley
2013-12-10 0:12 ` Karl Dahlke
2013-12-17 17:30 ` Greg Kroah-Hartman
2013-12-17 17:46 ` Peter Hurley
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=20131108011609.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=gregkh@linuxfoundation.org \
--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).