From: Matt Turner <mattst88@gmail.com>
To: Magnus Lindholm <linmag7@gmail.com>
Cc: richard.henderson@linaro.org, linux-kernel@vger.kernel.org,
linux-alpha@vger.kernel.org
Subject: Re: [PATCH v7 0/5] alpha: improve Tsunami machine check reporting
Date: Tue, 13 Oct 2026 22:10:18 -0400 [thread overview]
Message-ID: <20261014021020.3842132-1-mattst88@gmail.com> (raw)
In-Reply-To: <20261013211551.991723-1-linmag7@gmail.com>
On Tue, Oct 13, 2026 at 23:15 +0200, Magnus Lindholm wrote:
> This series adds Tsunami/Typhoon system-error diagnostics and Clipper
> ES40 environmental reporting.
I rebuilt 4 and 5 (1-3 are unchanged): vmlinux, W=1, for GENERIC,
DP264, SHARK and EIGER, plus DP264 without CONFIG_VERBOSE_MCHECK. No
warnings in the touched files. Minimal configs, not booted.
I also went through the 21272 HRM and the ES40 Service Guide this
time. The PERROR and MISC decoding, the frame layouts and the Clipper
bit tables all match.
You were right about SERR, the note in 8.8.2.6 is unconditional. And
8.8.2.1 says configuration reads never set NDS, so my probing question
goes away.
Comments on 4 and 5 in reply to those patches.
prev parent reply other threads:[~2026-10-14 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 21:15 Magnus Lindholm
2026-10-13 21:15 ` [PATCH v7 1/5] alpha: move Tsunami machine check handling to err_tsunami.c Magnus Lindholm
2026-10-13 21:15 ` [PATCH v7 2/5] alpha: describe the Tsunami system machine check frame Magnus Lindholm
2026-10-13 21:15 ` [PATCH v7 3/5] alpha: bound EV6 logout decoding by the processor area Magnus Lindholm
2026-10-13 21:15 ` [PATCH v7 4/5] alpha: decode and acknowledge Tsunami system machine checks Magnus Lindholm
2026-10-14 2:10 ` Matt Turner
2026-10-13 21:15 ` [PATCH v7 5/5] alpha: decode Clipper environmental events and retain console logs Magnus Lindholm
2026-10-14 2:10 ` Matt Turner
2026-10-14 2:10 ` Matt Turner [this message]
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=20261014021020.3842132-1-mattst88@gmail.com \
--to=mattst88@gmail.com \
--cc=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.henderson@linaro.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®