From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Petr Mladek <pmladek@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@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 12:12:29 -0700 [thread overview]
Message-ID: <CA+55aFxCnmd8+9qYs1pBG+N3ULQjMOV5S6yZCjA-w_pwc6kXyA@mail.gmail.com> (raw)
In-Reply-To: <20171013091857.4afe8a7a@gandalf.local.home>
On Fri, Oct 13, 2017 at 6:18 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> 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.
By the time 40 sec has passed, I suspect most people have just
rebooted the machine.
I think an NMI watchdog should just force the flush - the same way an
oops should. Deadlocks aren't really relevant if something doesn't get
printed out anyway.
Linus
next prev parent reply other threads:[~2017-10-13 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 16:16 NMI watchdog dump does not print on hard lockup Steven Rostedt
2017-10-12 19:26 ` Peter Zijlstra
2017-10-13 11:14 ` Petr Mladek
2017-10-13 13:18 ` Steven Rostedt
2017-10-13 19:12 ` Linus Torvalds [this message]
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=CA+55aFxCnmd8+9qYs1pBG+N3ULQjMOV5S6yZCjA-w_pwc6kXyA@mail.gmail.com \
--to=torvalds@linux-foundation.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=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
/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.