From: Jason Gunthorpe <jgg@mellanox.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Leon Romanovsky <leonro@mellanox.com>
Subject: Re: Regression from patch 'tty: hvc: hvc_poll() break hv read loop'
Date: Tue, 4 Sep 2018 15:16:35 -0600 [thread overview]
Message-ID: <20180904211635.GD335@mellanox.com> (raw)
In-Reply-To: <20180905071529.3b7a09c4@roar.ozlabs.ibm.com>
On Wed, Sep 05, 2018 at 07:15:29AM +1000, Nicholas Piggin wrote:
> On Tue, 4 Sep 2018 11:48:08 -0600
> Jason Gunthorpe <jgg@mellanox.com> wrote:
>
> > Hi Nicholas,
> >
> > I am testing 4.19-rc2 and I see bad behavior with my qemu hvc0
> > console..
> >
> > Running interactive with qemu (qemu-2.11.2-1.fc28) on the console
> > providing hvc0, using options like:
> >
> > -nographic
> > -chardev stdio,id=stdio,mux=on,signal=off
> > -mon chardev=stdio
> > -device isa-serial,chardev=stdio
> > -device virtio-serial-pci
> > -device virtconsole,chardev=stdio
> >
> > I see the hvc0 console hang regularly, ie doing something like 'up
> > arrow' in bash causes the hvc0 console to hang. Prior kernels worked
> > OK.
> >
> > Any ideas? I'm not familiar with this code.. Thanks!
>
> Yes I have had another report, I'm working on a fix. Sorry it has taken
> a while and thank you for the report.
Okay, let me know when you have a fix and I will be able to test it
for you!
Thanks,
Jason
next prev parent reply other threads:[~2018-09-04 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 17:48 Regression from patch 'tty: hvc: hvc_poll() break hv read loop' Jason Gunthorpe
2018-09-04 21:15 ` Nicholas Piggin
2018-09-04 21:16 ` Jason Gunthorpe [this message]
2018-09-05 3:51 ` Nicholas Piggin
2018-09-05 4:42 ` Leon Romanovsky
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=20180904211635.GD335@mellanox.com \
--to=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
/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).