linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Sinan Kaya <okaya@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Colin Ian King <colin.king@canonical.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] watchdog: Reduce message verbosity
Date: Mon, 30 Jul 2018 15:28:01 -0400	[thread overview]
Message-ID: <20180730192800.nqdhugzbxmin6e25@redhat.com> (raw)
In-Reply-To: <20180730190949.141996-1-okaya@kernel.org>

On Mon, Jul 30, 2018 at 12:09:47PM -0700, Sinan Kaya wrote:
> Reducing the verbosity level to debug for people that are interested in
> debugging watchdog issues.
> 
> [    0.152492] NMI watchdog: Perf event create on CPU 0 failed with -2
> [    0.156002] NMI watchdog: Perf NMI watchdog permanently disabled

Hi Sinan,

Any reason why?  Usually when the 'perf event' fails, that indicates a
system problem.  And most folks don't boot with the 'debug' option.  This
means these unusual failures are hidden and become difficult to debug later
when it propagates.

Or are you running the watchdog in a different configuration such that this
is a common nuisance that you are trying to suppress?

Cheers,
Don

> 
> Signed-off-by: Sinan Kaya <okaya@kernel.org>
> ---
>  kernel/watchdog_hld.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/watchdog_hld.c b/kernel/watchdog_hld.c
> index e449a23e9d59..1f7020d65d0a 100644
> --- a/kernel/watchdog_hld.c
> +++ b/kernel/watchdog_hld.c
> @@ -175,8 +175,8 @@ static int hardlockup_detector_event_create(void)
>  	evt = perf_event_create_kernel_counter(wd_attr, cpu, NULL,
>  					       watchdog_overflow_callback, NULL);
>  	if (IS_ERR(evt)) {
> -		pr_info("Perf event create on CPU %d failed with %ld\n", cpu,
> -			PTR_ERR(evt));
> +		pr_debug("Perf event create on CPU %d failed with %ld\n", cpu,
> +			 PTR_ERR(evt));
>  		return PTR_ERR(evt);
>  	}
>  	this_cpu_write(watchdog_ev, evt);
> -- 
> 2.17.1
> 

  reply	other threads:[~2018-07-30 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 19:09 [PATCH] watchdog: Reduce message verbosity Sinan Kaya
2018-07-30 19:28 ` Don Zickus [this message]
2018-07-30 19:43   ` Sinan Kaya
2018-08-01 15:59     ` Don Zickus
2018-08-02 12:18 ` Thomas Gleixner
2018-08-02 14:44   ` Sinan Kaya

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=20180730192800.nqdhugzbxmin6e25@redhat.com \
    --to=dzickus@redhat.com \
    --cc=colin.king@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=okaya@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pombredanne@nexb.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 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).