From: Thomas Huth <thuth@redhat.com>
To: Rob Landley <rob@landley.net>, QEMU Developers <qemu-devel@nongnu.org>
Cc: qemu-ppc@nongnu.org, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: serial hang in qemu-system-ppc64 -M pseries
Date: Wed, 27 Apr 2022 17:36:42 +0200 [thread overview]
Message-ID: <4106256f-1648-cf8b-b0e2-cefc84caf18e@redhat.com> (raw)
In-Reply-To: <8558c117-75a0-dc73-9b1a-be128e04056c@redhat.com>
On 27/04/2022 17.27, Thomas Huth wrote:
> On 26/04/2022 12.26, Rob Landley wrote:
>> When I cut and paste 80-ish characters of text into the Linux serial
>> console, it
>> reads 16 characters and stops. When I hit space, it reads another 16
>> characters,
>> and if I keep at it will eventually catch up without losing data. If I type,
>> every character shows up immediately.
>
> That "16" certainly comes from VTERM_BUFSIZE in hw/char/spapr_vty.c in the
> QEMU sources, I think.
>
>> (On other qemu targets and kernels I can cut and paste an entire uuencoded
>> binary and it goes through just fine in one go, but this target hangs with
>> big
>> pastes until I hit keys.)
>>
>> Is this a qemu-side bug, or a kernel-side bug?
>>
>> Kernel config attached (linux 5.18-rc3 or thereabouts), qemu invocation is:
>>
>> qemu-system-ppc64 -M pseries -vga none -nographic -no-reboot -m 256 -kernel
>> vmlinux -initrd powerpc64leroot.cpio.gz -append "panic=1 HOST=powerpc64le
>> console=hvc0"
>
> Which version of QEMU are you using? Which frontend (GTK or terminal?) ...
> this rings a distant bell, but I thought we had fixed these issues long ago
> in the past... e.g.:
>
> https://yhbt.net/lore/all/1380113886-16845-10-git-send-email-mdroth@linux.vnet.ibm.com/
>
> https://git.qemu.org/?p=qemu.git;a=commitdiff;h=8a273cbe53221d28
>
> ... but maybe my memory also just fails and this has never been properly fixed.
In case you're using GTK, I think I just found the problem that I was
remembering again:
https://lists.gnu.org/archive/html/qemu-ppc/2016-11/msg00142.html
https://lists.gnu.org/archive/html/qemu-ppc/2016-11/msg00143.html
I assume this has never been properly fixed.
Thomas
next prev parent reply other threads:[~2022-04-27 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 10:26 serial hang in qemu-system-ppc64 -M pseries Rob Landley
2022-04-27 15:27 ` Thomas Huth
2022-04-27 15:36 ` Thomas Huth [this message]
2022-04-28 5:41 ` Rob Landley
2022-04-28 6:04 ` Rob Landley
2022-04-29 21:43 ` Fabiano Rosas
2022-04-30 9:08 ` Rob Landley
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=4106256f-1648-cf8b-b0e2-cefc84caf18e@redhat.com \
--to=thuth@redhat.com \
--cc=kraxel@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rob@landley.net \
/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).