From: Steven Rostedt <rostedt@goodmis.org>
To: Petr Mladek <pmladek@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: NMI watchdog dump does not print on hard lockup
Date: Fri, 13 Oct 2017 09:18:57 -0400 [thread overview]
Message-ID: <20171013091857.4afe8a7a@gandalf.local.home> (raw)
In-Reply-To: <20171013111444.GB2795@pathway.suse.cz>
On Fri, 13 Oct 2017 13:14:44 +0200
Petr Mladek <pmladek@suse.com> wrote:
> In general, we could either improve detection of situations when
> the entire system is locked. It would be a reason to risk calling
> consoles even in NMI.
>
> Or we could accept that the "default" printk is not good for all
> situations and allow more special "debugging" modes:
>
> + Peter's force_early_printk stuff
>
> + Allow to disable printk_safe and printk_safe_nmi.
> There will be a risk of a deadlock caused by printk.
> But there also will be a chance to see the messages.
Or add the following case: The watchdog triggers, does the print, then
if it triggers again in a certain amount of time, and the print still
hasn't been flushed, the flush happens then.
-- Steve
next prev parent reply other threads:[~2017-10-13 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 16:16 Steven Rostedt
2017-10-12 19:26 ` Peter Zijlstra
2017-10-13 11:14 ` Petr Mladek
2017-10-13 13:18 ` Steven Rostedt [this message]
2017-10-13 19:12 ` Linus Torvalds
2017-10-16 11:12 ` Petr Mladek
2017-10-16 13:13 ` Sergey Senozhatsky
2017-10-16 14:15 ` Steven Rostedt
2017-10-17 7:50 ` Sergey Senozhatsky
2018-10-23 6:49 ` Sergey Senozhatsky
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=20171013091857.4afe8a7a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®