From: Daniel Gibson <daniel@gibson.sh>
To: "Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Mario Limonciello" <superm1@kernel.org>
Cc: Daniel Gibson <daniel@gibson.sh>
Subject: [PATCH v3 4/5] Documentation/arch/x86/amd-debugging: Add example for reset register
Date: Tue, 12 May 2026 22:26:44 +0200 [thread overview]
Message-ID: <20260512202645.1549111-5-daniel@gibson.sh> (raw)
In-Reply-To: <20260512202645.1549111-1-daniel@gibson.sh>
The amd debugging documentation didn't state how to identify kernel log
lines with information from the reset register about the cause of a
previous random reboot.
The added example rectifies this.
Suggested-by: Mario Limonciello (AMD) <superm1@kernel.org>
Signed-off-by: Daniel Gibson <daniel@gibson.sh>
---
Documentation/arch/x86/amd-debugging.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/arch/x86/amd-debugging.rst b/Documentation/arch/x86/amd-debugging.rst
index d92bf59d62c7..3176a1240fee 100644
--- a/Documentation/arch/x86/amd-debugging.rst
+++ b/Documentation/arch/x86/amd-debugging.rst
@@ -366,3 +366,8 @@ There are 6 classes of reasons for the reboot:
This information is read by the kernel at bootup and printed into
the syslog. When a random reboot occurs this message can be helpful
to determine the next component to debug.
+
+For example, if bit 19 was set, you will get a message like this in the log on
+next bootup::
+
+ x86/amd: Previous system reset reason [0x00080000]: software wrote 0x6 to reset control register 0xCF9
--
2.48.1
next prev parent reply other threads:[~2026-05-12 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 20:26 [PATCH v3 0/5] amd_pmc: Delay s2idle suspend for some devices Daniel Gibson
2026-05-12 20:26 ` [PATCH v3 1/5] platform/x86/amd/pmc: Check for intermediate wakeup in function Daniel Gibson
2026-05-12 20:26 ` [PATCH v3 2/5] platform/x86/amd/pmc: Delay suspend for some Lenovo Laptops Daniel Gibson
2026-05-12 20:26 ` [PATCH v3 3/5] platform/x86/amd/pmc: Add delay_suspend module parameter Daniel Gibson
2026-05-12 20:26 ` Daniel Gibson [this message]
2026-05-12 20:26 ` [PATCH v3 5/5] Documentation/arch/x86/amd-debugging: Add section about delay_suspend Daniel Gibson
2026-05-21 14:44 ` [PATCH v3 0/5] amd_pmc: Delay s2idle suspend for some devices Mario Limonciello
2026-05-21 19:13 ` Daniel Gibson
2026-05-21 19:43 ` Mario Limonciello
2026-05-21 20:32 ` Daniel Gibson
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=20260512202645.1549111-5-daniel@gibson.sh \
--to=daniel@gibson.sh \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=superm1@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®