mirror of https://lore.kernel.org/lkml/
 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: Wed, 1 Aug 2018 11:59:37 -0400	[thread overview]
Message-ID: <20180801155937.hwsgqpa5n4q2dkfe@redhat.com> (raw)
In-Reply-To: <4e5def8b-df29-0efb-7e35-e71070e94d91@kernel.org>

On Mon, Jul 30, 2018 at 12:43:34PM -0700, Sinan Kaya wrote:
> Hi Don,
> 
> On 7/30/2018 12:28 PM, Don Zickus wrote:
> > > [    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.
> 
> Sorry, I should have been more clear. I'm only suppressing the first
> error message.
> 
> [    0.152492] NMI watchdog: Perf event create on CPU 0 failed with -2
> 
> Second message is still visible during boot. User knows that NMI watchdog is
> disabled.
> 
> [    0.156002] NMI watchdog: Perf NMI watchdog permanently disabled
> 
> Code is trying to probe the platform capabilities and is failing
> because of missing PMU in the system. If someone is interested in
> finding out why watchdog was disabled, they can turn on the debug
> message level.
> 
> > 
> > Or are you running the watchdog in a different configuration such that this
> > is a common nuisance that you are trying to suppress?
> 
> Yup, system doesn't support PMU.

Hi Sinan,

Oh, I see.  You are just trying to hide the always failing probe.  It seems
to make sense.

Acked-by: Don Zickus <dzickus@redhat.com>


  reply	other threads:[~2018-08-01 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 19:09 Sinan Kaya
2018-07-30 19:28 ` Don Zickus
2018-07-30 19:43   ` Sinan Kaya
2018-08-01 15:59     ` Don Zickus [this message]
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=20180801155937.hwsgqpa5n4q2dkfe@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

all inboxes | Powered by JetHome®