From: Ingo Molnar <mingo@kernel.org>
To: Mario Limonciello <superm1@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH 2/2] x86/CPU/AMD: Print the reason for the last reset
Date: Mon, 7 Apr 2025 21:04:01 +0200 [thread overview]
Message-ID: <Z_QhoXeHf-Itua95@gmail.com> (raw)
In-Reply-To: <ebfaae8d-7186-454f-ba06-b86fea357d03@kernel.org>
* Mario Limonciello <superm1@kernel.org> wrote:
> > I realize that the entire numeric value gets printed as well, but it's
> > the symbolic decoding that is most useful to humans.
>
> The way that I "envisioned" this working was someone uses their machine and
> suddenly hits a problem. When they do they look at amd/debugging.rst and
> then run:
>
> "journalctl -k | grep "System reset was due"
>
> and then map the odd duck(s) out to the table.
99% of such people wouldn't know about amd/debugging.rst (nor should
they really: why should there be an extra layer of obfuscation while we
have this thing called a 'computer' that could ... compute all that
lookup for us? ;-), and they'd be looking at information in the syslog
after weird reboots.
We should improve their quality of life as much as possible.
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-07 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 16:25 [PATCH 1/2] Documentation: Add AMD Zen debugging document Mario Limonciello
2025-04-07 16:25 ` [PATCH 2/2] x86/CPU/AMD: Print the reason for the last reset Mario Limonciello
2025-04-07 18:46 ` Ingo Molnar
2025-04-07 18:56 ` Mario Limonciello
2025-04-07 19:04 ` Ingo Molnar [this message]
2025-04-07 21:46 ` Borislav Petkov
2025-04-08 7:09 ` Ingo Molnar
2025-04-08 7:17 ` Ingo Molnar
2025-04-08 15:45 ` Dave Hansen
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=Z_QhoXeHf-Itua95@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=superm1@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/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).