From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>, "M K, Muralidhara" <muralimk@amd.com>
Cc: yazen.ghannam@amd.com, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org, mchehab@kernel.org,
Muralidhara M K <muralidhara.mk@amd.com>,
Avadhut Naik <Avadhut.Naik@amd.com>
Subject: Re: [PATCH v2 1/4] EDAC/mce_amd: Remove SMCA Extended Error code descriptions
Date: Thu, 26 Oct 2023 09:05:51 -0400 [thread overview]
Message-ID: <dd13363e-fd7e-4e88-8c23-91cfffe11dc3@amd.com> (raw)
In-Reply-To: <20231026123754.GBZTpdojw+pNuZMyJy@fat_crate.local>
On 10/26/2023 8:37 AM, Borislav Petkov wrote:
> On Thu, Oct 26, 2023 at 05:32:17PM +0530, M K, Muralidhara wrote:
>> Not possible. User has to check the kernel dmesg log and using "Ext.
>> Error code" user has to refer the "error string" in the PPR for
>> a particular Error code.
>
> Let me paste from my previous email:
>
> "If that is not possible with rasdaemon yet, then this patch should not
> remove the error descriptions but limit them only to the families for
> which they're valid.
>
> Bottom line is, I don't want to have the situation mcelog is in where
> decoding errors with it is a total disaster.
>
> IOW, I'd like error decoding on AMD to always work and be trivially easy
> to do."
>
+Avadhut
Post-processing is one of the features that Avadhut implemented.
https://github.com/mchehab/rasdaemon/commit/932118b04a04104dfac6b8536419803f236e6118
Thanks,
Yazen
next prev parent reply other threads:[~2023-10-26 13:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 5:14 [PATCH v2 0/4] Few cleanups and AMD Family 19h Models 90h-9fh EDAC Support Muralidhara M K
2023-10-25 5:14 ` [PATCH v2 1/4] EDAC/mce_amd: Remove SMCA Extended Error code descriptions Muralidhara M K
2023-10-25 19:08 ` Borislav Petkov
2023-10-26 9:42 ` M K, Muralidhara
2023-10-26 11:14 ` Borislav Petkov
2023-10-26 12:02 ` M K, Muralidhara
2023-10-26 12:37 ` Borislav Petkov
2023-10-26 13:05 ` Yazen Ghannam [this message]
2023-10-26 13:40 ` Borislav Petkov
2023-10-27 5:05 ` M K, Muralidhara
2023-10-25 5:14 ` [PATCH v2 2/4] x86/MCE/AMD: Add new MA_LLC, USR_DP, and USR_CP bank types Muralidhara M K
2023-10-26 8:19 ` Borislav Petkov
2023-10-26 9:46 ` M K, Muralidhara
2023-10-25 5:14 ` [PATCH v2 3/4] EDAC/mc: Add new HBM3 memory type Muralidhara M K
2023-10-25 5:14 ` [PATCH v2 4/4] EDAC/amd64: Add Family 19h Models 90h ~ 9fh enumeration support Muralidhara M K
[not found] ` <20231027144552.GGZTvNIE7g1S3jBM72@fat_crate.local>
2023-10-30 4:23 ` M K, Muralidhara
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=dd13363e-fd7e-4e88-8c23-91cfffe11dc3@amd.com \
--to=yazen.ghannam@amd.com \
--cc=Avadhut.Naik@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=muralidhara.mk@amd.com \
--cc=muralimk@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