From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org,
openembedded-core <openembedded-core@lists.openembedded.org>,
Bruce Ashfield <bruce.ashfield@gmail.com>,
Randy MacLeod <randy.macleod@windriver.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: Kernel 6.5 ttyS1 hang with qemu (was Re: [OE-core] Summary of the remaining 6.5 kernel serial issue (and 6.5 summary)
Date: Mon, 16 Oct 2023 10:16:06 +0300 [thread overview]
Message-ID: <ZSzjNgdCH_wmB4u2@nuoska> (raw)
In-Reply-To: <20231016063501.GL27774@atomide.com>
Hi,
On Mon, Oct 16, 2023 at 09:35:01AM +0300, Tony Lindgren wrote:
> * Richard Purdie <richard.purdie@linuxfoundation.org> [231015 21:30]:
> > On Sun, 2023-10-15 at 17:31 +0200, Greg Kroah-Hartman wrote:
> > > Can you try the patch below? I just sent it to Linus and it's from Tony
> > > to resolve some other pm issues with the serial port code.
> >
> > Thanks for the pointer to this. I've put it through some testing and
> > had one failure so far so I suspect this isn't enough unfortunately.
> >
> > FWIW I was looping the testing on the complete removal of the
> > conditions and didn't see any failures with that.
>
> Care to clarify what's the failing test now?
>
> Is the issue still the second port not always coming up after boot or
> something else?
Yes, data from the ttyS1 getty is not coming through from kernel and qemu to
the test framework looking for login prompt after qemu machine boot.
Workarounds like sending "\n\n" from the test framework through qemu to ttyS1
or "echo helloB > /dev/ttyS1" via working ttyS0 don't seem to help and wake
it up.
Cheers,
-Mikko
next prev parent reply other threads:[~2023-10-16 7:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <178BF2895FF685E6.5378@lists.openembedded.org>
[not found] ` <a2ad67a0575548b6d5d8d187e597dcd72ae07f64.camel@linuxfoundation.org>
2023-10-09 10:05 ` Kernel 6.5 ttyS1 hang with qemu (was Re: [OE-core] Summary of the remaining 6.5 kernel serial issue (and 6.5 summary) Mikko Rapeli
2023-10-14 9:41 ` Richard Purdie
2023-10-14 11:13 ` Richard Purdie
[not found] ` <178DF50519C11C84.8679@lists.openembedded.org>
2023-10-15 12:29 ` Richard Purdie
2023-10-15 15:31 ` Greg Kroah-Hartman
2023-10-15 21:30 ` Richard Purdie
2023-10-16 6:35 ` Tony Lindgren
2023-10-16 7:16 ` Mikko Rapeli [this message]
2023-10-16 7:23 ` Tony Lindgren
2023-10-16 8:09 ` Mikko Rapeli
2023-10-16 8:10 ` Richard Purdie
2023-10-17 6:56 ` Tony Lindgren
2023-10-17 22:14 ` Richard Purdie
2023-10-18 5:28 ` Tony Lindgren
2023-10-19 12:44 ` Richard Purdie
[not found] <ZSlfF+2cEHb8nUwO@windriver.com>
[not found] ` <178C6861D9B097E8.24994@lists.openembedded.org>
2023-10-16 5:59 ` Mikko Rapeli
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=ZSzjNgdCH_wmB4u2@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=bruce.ashfield@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.gortmaker@windriver.com \
--cc=randy.macleod@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=tony@atomide.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