From: Mario Limonciello <superm1@kernel.org>
To: Rong Zhang <i@rong.moe>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/CPU/AMD: Prevent reset reasons from being retained among boots
Date: Mon, 13 Oct 2025 10:37:05 -0500 [thread overview]
Message-ID: <35819fb2-637a-4ba9-8652-0ca05951c5bb@kernel.org> (raw)
In-Reply-To: <20251010165959.49737-1-i@rong.moe>
On 10/10/25 11:59 AM, Rong Zhang wrote:
> The S5_RESET_STATUS register is parsed on boot and printed to kmsg.
> However, this could sometimes be misleading and lead to users wasting a
> lot of time on meaningless debugging for two reasons:
>
> * Some bits are never cleared by hardware. It's the software's
> responsibility to clear them as per the Processor Programming Reference
> (see Link:).
>
> * Some rare hardware-initiated platform resets do not update the
> register at all.
>
> In both cases, a previous reboot could leave its trace in the register,
> resulting in users seeing unrelated reboot reasons while debugging
> random reboots afterward.
>
> Clearing all reason bits solves the issue. Since all reason bits are
> write-1-to-clear and we must preserve all other bits, this is done by
> writing the read value back to the register.
>
> Fixes: ab8131028710 ("x86/CPU/AMD: Print the reason for the last reset")
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=206537#attach_303991
> Signed-off-by: Rong Zhang <i@rong.moe>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
> ---
> Changes in v2:
> - Remove a debug message (suggested by Borislav Petkov)
> - No longer mention this behavior in the documentation
> - Link to v1: https://lore.kernel.org/r/20250913144245.23237-1-i@rong.moe/
> ---
> arch/x86/kernel/cpu/amd.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
> index 5398db4dedb4a..ccaa51ce63f6e 100644
> --- a/arch/x86/kernel/cpu/amd.c
> +++ b/arch/x86/kernel/cpu/amd.c
> @@ -1355,11 +1355,23 @@ static __init int print_s5_reset_status_mmio(void)
> return 0;
>
> value = ioread32(addr);
> - iounmap(addr);
>
> /* Value with "all bits set" is an error response and should be ignored. */
> - if (value == U32_MAX)
> + if (value == U32_MAX) {
> + iounmap(addr);
> return 0;
> + }
> +
> + /*
> + * Clear all reason bits so they won't be retained if the next reset
> + * does not update the register. Besides, some bits are never cleared by
> + * hardware so it's software's responsibility to clear them.
> + *
> + * Writing the value back effectively clears all reason bits as they are
> + * write-1-to-clear.
> + */
> + iowrite32(value, addr);
> + iounmap(addr);
>
> for (i = 0; i < ARRAY_SIZE(s5_reset_reason_txt); i++) {
> if (!(value & BIT(i)))
>
> base-commit: 7d24c651ce163bc04e7683ec75bf976b6ff042e2
next prev parent reply other threads:[~2025-10-13 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 16:59 Rong Zhang
2025-10-13 15:34 ` Yazen Ghannam
2025-10-13 15:37 ` Mario Limonciello [this message]
2025-10-15 19:54 ` [tip: x86/urgent] x86/CPU/AMD: Prevent reset reasons from being retained across reboot tip-bot2 for Rong Zhang
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=35819fb2-637a-4ba9-8652-0ca05951c5bb@kernel.org \
--to=superm1@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=i@rong.moe \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yazen.ghannam@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
all inboxes | Powered by JetHome®