From: Aristeu Rozanski <aris@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Error reports at boot time in Ampere Altra machines since c733ebb7c
Date: Thu, 2 Mar 2023 15:17:32 -0500 [thread overview]
Message-ID: <20230302201732.pwnhg46mum6st2bv@redhat.com> (raw)
Hi Marc,
Since c733ebb7cb67d ("irqchip/gic-v3-its: Reset each ITS's BASERn
register before probe"), Ampere Altra machines are reporting corrected
errors during boot:
[ 0.294334] HEST: Table parsing has been initialized.
[ 0.294397] sdei: SDEIv1.0 (0x0) detected in firmware.
[ 0.299622] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[ 0.299626] {1}[Hardware Error]: event severity: recoverable
[ 0.299629] {1}[Hardware Error]: Error 0, type: recoverable
[ 0.299633] {1}[Hardware Error]: section type: unknown, e8ed898d-df16-43cc-8ecc-54f060ef157f
[ 0.299638] {1}[Hardware Error]: section length: 0x30
[ 0.299645] {1}[Hardware Error]: 00000000: 00000005 ec30000e 00080110 80001001 ......0.........
[ 0.299648] {1}[Hardware Error]: 00000010: 00000300 00000000 00000000 00000000 ................
[ 0.299650] {1}[Hardware Error]: 00000020: 00000000 00000000 00000000 00000000 ................
[ 0.299714] {2}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 3
[ 0.299716] {2}[Hardware Error]: event severity: recoverable
[ 0.299717] {2}[Hardware Error]: Error 0, type: recoverable
[ 0.299718] {2}[Hardware Error]: section type: unknown, e8ed898d-df16-43cc-8ecc-54f060ef157f
[ 0.299720] {2}[Hardware Error]: section length: 0x30
[ 0.299722] {2}[Hardware Error]: 00000000: 40000005 ec30000e 00080110 80005001 ...@..0......P..
[ 0.299724] {2}[Hardware Error]: 00000010: 00000300 00000000 00000000 00000000 ................
[ 0.299726] {2}[Hardware Error]: 00000020: 00000000 00000000 00000000 00000000 ................
[ 0.299912] GHES: APEI firmware first mode is enabled by APEI bit.
Because the errors are being reported later in boot, it's hard to
pinpoint exactly what's causing it without decoding the error information,
which I currently don't know how to do it.
There're no problems other than of course triggering tests because of
the warnings.
Do you know what's going on here?
Thanks
--
Aristeu
next reply other threads:[~2023-03-02 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 20:17 Aristeu Rozanski [this message]
2023-03-02 23:25 ` Marc Zyngier
2023-03-03 3:04 ` Aristeu Rozanski
2023-03-03 19:38 ` Darren Hart
2023-03-03 20:10 ` Marc Zyngier
2023-03-03 20:23 ` Darren Hart
2023-04-03 16:26 ` Aristeu Rozanski
2023-04-03 23:50 ` Darren Hart
2023-04-04 12:57 ` Aristeu Rozanski
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=20230302201732.pwnhg46mum6st2bv@redhat.com \
--to=aris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.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®