public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Todd Brandt <todd.e.brandt@linux.intel.com>
To: John Ogness <john.ogness@linutronix.de>, pmladek@suse.com
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	senozhatsky@chromium.org, rostedt@goodmis.org
Subject: Re: PNP0501 serial driver takes almost 2 seconds to suspend/resume (printk issue)
Date: Fri, 08 Jul 2022 14:35:59 -0700	[thread overview]
Message-ID: <045ebee30af2b80aaeace1dab18ecd113e3f17c7.camel@linux.intel.com> (raw)
In-Reply-To: <87czegxccb.fsf@jogness.linutronix.de>

On Fri, 2022-07-08 at 10:07 +0206, John Ogness wrote:
> Hi Todd,
> 
> Thanks for reporting this.
> 
> On 2022-07-07, Todd Brandt <todd.e.brandt@linux.intel.com> wrote:
> > Ever since 5.19.0-rc1 the serial device has taken almost a second
> > longer in both suspend and resume. This effect is witnessed in half
> > the machines in our lab (~10 machines). It occurs on dell, asus,
> > gigabyte and other machines so it's not hardware specific.
> 
> Please provide a full dmesg log if you can. The important parts of
> the
> log would be:
> 
> - boot arguments
> - any lines with "printk" in it
> - timing information
> - messages during suspend and resume
> 
> pr_flush() uses a timeout of 1 second. I assume your console driver
> is
> not printing and therefore not making any forward progress.
> 
> John Ogness

The dmesg logs are in the html timelines themselves, just click the
"dmesg" button in the upper right hand corner. The log button shows all
kinds of system info as well.


  reply	other threads:[~2022-07-08 21:36 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 [this message]
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
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=045ebee30af2b80aaeace1dab18ecd113e3f17c7.camel@linux.intel.com \
    --to=todd.e.brandt@linux.intel.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=pmladek@suse.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