From: Vito Caputo <vcaputo@pengaru.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Dmitry Safonov <dima@arista.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>, Mark Rutland <mark.rutland@arm.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Tycho Andersen <tycho@tycho.ws>, Dave Mielke <dave@mielke.cc>,
linux-kernel@vger.kernel.org
Subject: Re: commit 83d817f410 broke my ability to use Linux with a braille display
Date: Fri, 11 Jan 2019 11:11:55 -0800 [thread overview]
Message-ID: <20190111191155.s4e5sn5fqk33fqr4@shells.gnugeneration.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1901111239510.1512@knanqh.ubzr>
On Fri, Jan 11, 2019 at 01:33:09PM -0500, Nicolas Pitre wrote:
> I use Linux with the help of a braille display and the brltty daemon. It
> turns out that the latest mainline kernel I can work with comes from
> commit 231f8fd0cc. Anything past that and I lose the ability to read the
> console barely a few seconds after the system has booted as brltty is
> thrown a wrench and the braille display becomes completely inoperable.
>
> Things get somewhat better with commit c96cf923a9 as brltty is not
> longer incapacitated, but some programs would randomly crash. Even the
> very first login attempt won't work as I soon as I hit enter after my
> user name the password prompt is skipped over, just like if the enter
> key had been hit twice. Then lynx (the text web browser) would crash as
> soon as I switch the virtual console with LeftAlt+FN. Mind you, this
> isn't easy to perform bisection in those conditions.
>
> And the worst commit i.e. 83d817f410 is marked for stable! :-(
>
> Some interaction with brltty must be at play here otherwise such
> breakage would never have survived up to the mainline kernel.
>
> As far as latest mainline is concerned, I managed to reproduce at least
> one of the unwelcome behavior change (hoping that's all there is to this
> issue) with a very simple test case so you won't have to learn braille
> to debug this:
>
> # from any vt, make sure tty40 is allocated and empty
> openvt -c 40 -f -- true
>
> # open it and wait on read()
> cat /dev/tty40
>
> # from a second vt, simply open tty40 again
> true < /dev/tty40
>
> # come back to the first vt and watch cat bailing out with EAGAIN.
>
> Please fix.
>
>
> Nicolas
This all sounds familiar, and I suspect this is the fix:
https://lkml.org/lkml/2019/1/8/1379
Regards,
Vito Caputo
next prev parent reply other threads:[~2019-01-11 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 18:33 commit 83d817f410 broke my ability to use Linux with a braille display Nicolas Pitre
2019-01-11 19:11 ` Vito Caputo [this message]
2019-01-11 19:32 ` Nicolas Pitre
2019-01-11 19:32 ` Greg Kroah-Hartman
2019-01-11 20:10 ` Nicolas Pitre
2019-01-12 8:08 ` Greg Kroah-Hartman
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=20190111191155.s4e5sn5fqk33fqr4@shells.gnugeneration.com \
--to=vcaputo@pengaru.com \
--cc=dave@mielke.cc \
--cc=dima@arista.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nico@fluxnic.net \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tycho@tycho.ws \
/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).