[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_QhoXeHf-Itua95@gmail.com>
Date: Mon, 7 Apr 2025 21:04:01 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Mario Limonciello <superm1@...nel.org>
Cc: Borislav Petkov <bp@...en8.de>, Jonathan Corbet <corbet@....net>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Yazen Ghannam <yazen.ghannam@....com>,
Mario Limonciello <mario.limonciello@....com>
Subject: Re: [PATCH 2/2] x86/CPU/AMD: Print the reason for the last reset
* Mario Limonciello <superm1@...nel.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
Powered by blists - more mailing lists