From: Esben Haabendal <esben@geanix.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: "Petr Mladek" <pmladek@suse.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
linux-rt-users@vger.kernel.org,
"Martin Hundebøll" <martin@geanix.com>
Subject: Re: [PATCH 1/2] printk: export pr_flush()
Date: Tue, 02 Apr 2024 13:19:09 +0200 [thread overview]
Message-ID: <87jzlgf1w2.fsf@geanix.com> (raw)
In-Reply-To: <874jckqcxu.fsf@jogness.linutronix.de> (John Ogness's message of "Tue, 02 Apr 2024 12:31:01 +0206")
John Ogness <john.ogness@linutronix.de> writes:
> On 2024-04-02, Esben Haabendal <esben@geanix.com> wrote:
>> Outside prinkt users might wan't assure whatever printed has reached
>> its destination before continuing. E.g. during the shutdown-procedure,
>> where printk-buffers aren't emptied before the system goes down.
>
> This is a reposting of:
>
> https://lore.kernel.org/lkml/20231030092432.3434623-1-martin@geanix.com
>
> As I wrote in that thread:
>
> printk() tries to print directly from the calling context. Are you
> experiencing problems where you do not see the restarting message?
Yes, that is exactly what we are seing.
> (If your answer is "yes", please explain the scenario and provide
> information about the console driver you are using.)
It is an i.MX8MP system, and console is attached to ttymxc1
(drivers/tty/serial/imx.c).
Booting up, and simply executing "reboot" command. Without these two
patches, the "reboot: Restarting system" message is not written to
ttymxc1 console. With the patches, it is.
> I assume you have tried the latest RT development version.
I have reproduced the problem with v6.6.23-rt28. I haven't upgraded to
6.7 or 6.8 yet. Do you need me to retest with 6.8?
/Esben
next prev parent reply other threads:[~2024-04-02 11:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 10:10 [PATCH 1/2] printk: export pr_flush() Esben Haabendal
2024-04-02 10:13 ` Esben Haabendal
2024-04-02 10:12 ` Esben Haabendal
2024-04-02 10:10 ` [PATCH 2/2] reboot: flush printk buffers before final shutdown Esben Haabendal
2024-04-02 10:13 ` Esben Haabendal
2024-04-02 10:12 ` Esben Haabendal
2024-04-02 10:25 ` [PATCH 1/2] printk: export pr_flush() John Ogness
2024-04-02 11:19 ` Esben Haabendal [this message]
2024-04-02 13:23 ` John Ogness
2024-04-02 14:41 ` Esben Haabendal
2024-04-02 15:20 ` John Ogness
2024-04-03 9:45 ` Esben Haabendal
2024-04-03 10:09 ` John Ogness
-- strict thread matches above, loose matches on Subject: below --
2023-10-30 9:24 Martin Hundebøll
2023-10-31 11:03 ` 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=87jzlgf1w2.fsf@geanix.com \
--to=esben@geanix.com \
--cc=john.ogness@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=martin@geanix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.