From: Guenter Roeck <linux@roeck-us.net>
To: Steve Wahl <steve.wahl@hpe.com>,
Craig Lamparter <craig.lamparter@hpe.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Russ Anderson <rja@hpe.com>, Dimitri Sivanich <sivanich@hpe.com>,
Kyle Meyer <kyle.meyer@hpe.com>,
Keng-Yu Lin <keng-yu.lin@hpe.com>,
Collins@owl.eag.rdlabs.hpecorp.net, Steve <s.collins@hpe.com>
Subject: Re: [PATCH] Refine hpwdt message for UV platform
Date: Tue, 17 Mar 2026 11:39:23 -0700 [thread overview]
Message-ID: <90d4f6fd-bc84-4ecb-b5c5-6c0a2a40fadb@roeck-us.net> (raw)
In-Reply-To: <20260316214530.104344-1-steve.wahl@hpe.com>
On 3/16/26 14:45, Steve Wahl wrote:
> The watchdog hardware the hpwdt driver uses was added to the UV
> platform for UV5, but the logging mentioned by this driver was not
> added to the BIOS. When the watchdog fires, the printed message had
> the administrators and developers looking for non-existent log files,
> and confused about whether a watchdog actually tripped.
>
> Change the message that prints on UV platforms so it doesn't send the
> user looking for non-existent logs.
>
> To aid in any future debugging, include all 8 bits of the NMISTAT
> register in the output, not just the two bits being used to determine
> this was "mynmi". And provide names to the bits in NMISTAT so the
> code is easier to understand.
>
> Signed-off-by: Steve Wahl <steve.wahl@hpe.com>
The subject should start with "watchdog:". I almost missed this patch.
Guenter
next prev parent reply other threads:[~2026-03-17 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 21:45 Steve Wahl
2026-03-17 18:38 ` Guenter Roeck
2026-03-17 18:39 ` Guenter Roeck [this message]
2026-04-07 20:33 ` kernel test robot
2026-04-07 21:08 ` Steve Wahl
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=90d4f6fd-bc84-4ecb-b5c5-6c0a2a40fadb@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Collins@owl.eag.rdlabs.hpecorp.net \
--cc=craig.lamparter@hpe.com \
--cc=keng-yu.lin@hpe.com \
--cc=kyle.meyer@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rja@hpe.com \
--cc=s.collins@hpe.com \
--cc=sivanich@hpe.com \
--cc=steve.wahl@hpe.com \
--cc=wim@linux-watchdog.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®