[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ilo1wdac.fsf@jogness.linutronix.de>
Date: Wed, 13 Jul 2022 11:57:55 +0206
From: John Ogness <john.ogness@...utronix.de>
To: Sergey Senozhatsky <senozhatsky@...omium.org>,
Petr Mladek <pmladek@...e.com>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
todd.e.brandt@...ux.intel.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@...r.kernel.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: PNP0501 serial driver takes almost 2 seconds to suspend/resume
(printk issue)
On 2022-07-11, Sergey Senozhatsky <senozhatsky@...omium.org> wrote:
>> It seems that __pr_flush() does not check whether all consoles are
>> suspended. In this case the progress is not possible and it has to
>> wait the entire timeout.
>
> But isn't console_suspended set after pr_flush() call?
There should not be any printing after the suspend_console() message. If
Todd's report is coming from 5.19-rc1, then it is likely a kthread
issue, where the kthread is not respecting @console_suspended. (This
would still need to be fixed for the kthreads, but would not be relevant
for 5.19.)
John
Powered by blists - more mailing lists