linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Mikko Rapeli <mikko.rapeli@linaro.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: Wed, 18 Oct 2023 08:28:22 +0300	[thread overview]
Message-ID: <20231018052822.GP27774@atomide.com> (raw)
In-Reply-To: <87cdf04bfd7997465dad157d9d81fc14ca7d122f.camel@linuxfoundation.org>

* Richard Purdie <richard.purdie@linuxfoundation.org> [231017 22:15]:
> On Tue, 2023-10-17 at 09:56 +0300, Tony Lindgren wrote:
> > * Richard Purdie <richard.purdie@linuxfoundation.org> [231016 08:10]:
> > > The port sometimes doesn't come up properly at boot.
> > > 
> > > To be clear, the "\n\n" from the qemu side into the port doesn't seem
> > > to help. The "echo helloB > /dev/ttyS1" inside the image does seem to
> > > wake it up. 
> > 
> > So if I understand correctly, this issue still happens with kernel patched
> > with commit 81a61051e0ce ("serial: core: Fix checks for tx runtime PM
> > state"), and the issue now only happens sometimes.
> 
> The issue has always been intermittent and it appeared to happen less
> frequently with 81a61051e0ce added but it was hard to know if I was
> imagining that.

Oh OK.

> > I wonder if the following additional change might help?
> 
> I've added it into testing and have not reproduced the failure with it
> applied yet, locally or on our autobuilder. We need to sort some
> release pieces which have been delayed by these issues and we're going
> with a workaround for that. Once that is built I can get back to
> testing this change more extensively, see if we can still provoke the
> issue or not. It may take a day or two of testing before we know with
> any certainty if the issue is resolved or not.

Thanks for the update, let's wait a few days and see then.

Regards,

Tony

  reply	other threads:[~2023-10-18  5:28 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
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 [this message]
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=20231018052822.GP27774@atomide.com \
    --to=tony@atomide.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=randy.macleod@windriver.com \
    --cc=richard.purdie@linuxfoundation.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).