Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
22 lines
626 B
ReStructuredText
22 lines
626 B
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
|
|
|
Error decoding
|
|
==============
|
|
|
|
x86
|
|
---
|
|
|
|
Error decoding on AMD systems should be done using the rasdaemon tool:
|
|
https://github.com/mchehab/rasdaemon/
|
|
|
|
While the daemon is running, it would automatically log and decode
|
|
errors. If not, one can still decode such errors by supplying the
|
|
hardware information from the error::
|
|
|
|
$ rasdaemon -p --status <STATUS> --ipid <IPID> --smca
|
|
|
|
Also, the user can pass particular family and model to decode the error
|
|
string::
|
|
|
|
$ rasdaemon -p --status <STATUS> --ipid <IPID> --smca --family <CPU Family> --model <CPU Model> --bank <BANK_NUM>
|