From: Robert Richter <rrichter@marvell.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Robert Richter <rrichter@marvell.com>,
Marcin Benka <mbenka@marvell.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH] efi/arm: Show SMBIOS bank/device location in cper and ghes error logs
Date: Wed, 20 Mar 2019 13:05:37 +0000 [thread overview]
Message-ID: <20190320130502.16667-1-rrichter@marvell.com> (raw)
Run dmi_memdev_walk() for arch arm* as other archs do. This improves
error logging as the memory device handle is translated now to the
DIMM entry's name provided by the DMI handle.
Before:
{1}[Hardware Error]: DIMM location: not present. DMI handle: 0x0038
After:
{1}[Hardware Error]: DIMM location: N0 DIMM_A0
Signed-off-by: Marcin Benka <mbenka@marvell.com>
Signed-off-by: Robert Richter <rrichter@marvell.com>
---
drivers/firmware/efi/arm-runtime.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/firmware/efi/arm-runtime.c b/drivers/firmware/efi/arm-runtime.c
index 0c1af675c338..4a0dfe4ab829 100644
--- a/drivers/firmware/efi/arm-runtime.c
+++ b/drivers/firmware/efi/arm-runtime.c
@@ -167,6 +167,7 @@ static int __init arm_dmi_init(void)
* itself, depends on dmi_scan_machine() having been called already.
*/
dmi_scan_machine();
+ dmi_memdev_walk();
if (dmi_available)
dmi_set_dump_stack_arch_desc();
return 0;
--
2.20.1
next reply other threads:[~2019-03-20 13:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 13:05 Robert Richter [this message]
2019-03-20 13:16 ` [PATCH] efi: Unify dmi setup code over architectures arm/arm64, io64 and x86 Robert Richter
2019-03-20 14:48 ` Robert Richter
2019-03-20 15:22 ` [PATCH v2] " Robert Richter
2019-03-20 22:02 ` Ard Biesheuvel
2019-03-21 9:39 ` Robert Richter
2019-03-21 9:51 ` Ard Biesheuvel
2019-03-21 10:08 ` Robert Richter
2019-03-21 10:09 ` Ard Biesheuvel
2019-03-21 10:11 ` Jean Delvare
2019-03-21 10:14 ` Ard Biesheuvel
2019-03-27 18:53 ` Ard Biesheuvel
2019-03-28 7:55 ` Robert Richter
2019-03-28 7:57 ` Ard Biesheuvel
2019-03-28 7:42 ` Robert Richter
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=20190320130502.16667-1-rrichter@marvell.com \
--to=rrichter@marvell.com \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenka@marvell.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
all inboxes | Powered by JetHome®