From: John Ogness <john.ogness@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Mike Galbraith <efault@gmx.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: printk: add pr_flush()
Date: Fri, 23 Oct 2020 09:29:41 +0206 [thread overview]
Message-ID: <877drhmmma.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20201022145214.a5sm66naswycezae@linutronix.de>
Hi Sebastian,
The "printk: add pr_flush()" patch should be removed from PREEMPT_RT
until this issue is resolved. I am getting several independent bug
reports of reboot problems.
Note that on crash situations the full ringbuffer should still be
printed. pr_flush() was only responsible for non-crash scenarios.
John Ogness
next prev parent reply other threads:[~2020-10-23 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 14:12 printk: add pr_flush() Mike Galbraith
2020-10-22 14:15 ` Sebastian Andrzej Siewior
2020-10-22 14:36 ` Mike Galbraith
2020-10-22 14:47 ` Mike Galbraith
2020-10-22 14:52 ` Sebastian Andrzej Siewior
2020-10-23 7:23 ` John Ogness [this message]
2020-10-23 11:08 ` Sebastian Andrzej Siewior
2020-10-22 15:04 ` 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=877drhmmma.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=linux-rt-users@vger.kernel.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).