From: Todd Brandt <todd.e.brandt@linux.intel.com>
To: John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Petr Mladek <pmladek@suse.com>,
rafael.j.wysocki@intel.com, len.brown@intel.com
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: PNP0501 serial driver takes almost 2 seconds to suspend/resume (printk issue)
Date: Thu, 14 Jul 2022 15:16:39 -0700 [thread overview]
Message-ID: <472f7fc2d44d781edb64f19f9970fe50eec79c1f.camel@linux.intel.com> (raw)
In-Reply-To: <875yk0908j.fsf@jogness.linutronix.de>
On Wed, 2022-07-13 at 23:28 +0206, John Ogness wrote:
> On 2022-07-13, Todd Brandt <todd.e.brandt@linux.intel.com> wrote:
> > URGENT: Removing the commit FIXES the issue.
> >
> > I just ran a 5.19.0-rc6 kernel with the offending commit removed
> > and
> > it fixed the problem completely on all 3 machines.
>
> I believe to have found the issue. A patch was posted to bugzilla:
>
> https://bugzilla.kernel.org/attachment.cgi?id=301413
>
> Please test this. Thanks.
>
> John Ogness
I ran with your fix on 30 systems. On the 7 machines where this problem
appears, the patch fixes it completely. On the 23 machines where this
problem does not appear, there are no issues or regressions.
Fix verified, thank you!
next prev parent reply other threads:[~2022-07-14 22:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 20:31 PNP0501 serial driver takes almost 2 seconds to suspend/resume (printk issue) Todd Brandt
2022-07-07 20:45 ` Todd Brandt
2022-07-08 8:01 ` John Ogness
2022-07-08 21:35 ` Todd Brandt
2022-07-09 20:41 ` John Ogness
2022-07-10 19:39 ` Andy Shevchenko
2022-07-10 20:04 ` John Ogness
2022-07-11 8:13 ` Petr Mladek
2022-07-11 10:10 ` Sergey Senozhatsky
2022-07-13 9:51 ` John Ogness
2022-07-13 14:24 ` Todd Brandt
2022-07-13 17:11 ` Todd Brandt
2022-07-13 18:23 ` Todd Brandt
2022-07-13 21:22 ` John Ogness
2022-07-13 22:01 ` John Ogness
2022-07-14 22:16 ` Todd Brandt [this message]
2022-07-15 6:14 ` John Ogness
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=472f7fc2d44d781edb64f19f9970fe50eec79c1f.camel@linux.intel.com \
--to=todd.e.brandt@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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