From: Greg KH <gregkh@linuxfoundation.org>
To: Sreenath Vijayan <sreenath.vijayan@sony.com>
Cc: linux-doc@vger.kernel.org, linux-serial@vger.kernel.org,
corbet@lwn.net, jirislaby@kernel.org,
linux-kernel@vger.kernel.org,
anandakumar.balasubramaniam@sony.com,
Shimoyashiki Taichi <taichi.shimoyashiki@sony.com>
Subject: Re: [PATCH] tty/sysrq: Dump kernel ring buffer messages via sysrq
Date: Thu, 21 Dec 2023 17:52:55 +0100 [thread overview]
Message-ID: <2023122144-enlarged-maggot-493a@gregkh> (raw)
In-Reply-To: <20231221133953.1507021-1-sreenath.vijayan@sony.com>
On Thu, Dec 21, 2023 at 07:09:53PM +0530, Sreenath Vijayan wrote:
> When terminal is unresponsive, one cannot use dmesg to view kernel
> ring buffer messages. Also, syslog services may be disabled,
> to check them after a reboot, especially on embedded systems.
> In this scenario, dump the kernel ring buffer messages via sysrq
> by pressing sysrq+D.
>
> Signed-off-by: Sreenath Vijayan <sreenath.vijayan@sony.com>
> Signed-off-by: Shimoyashiki Taichi <taichi.shimoyashiki@sony.com>
> ---
> Documentation/admin-guide/sysrq.rst | 2 ++
> drivers/tty/sysrq.c | 43 ++++++++++++++++++++++++++++-
> 2 files changed, 44 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/sysrq.rst b/Documentation/admin-guide/sysrq.rst
> index 2f2e5bd440f9..464c4e138b9d 100644
> --- a/Documentation/admin-guide/sysrq.rst
> +++ b/Documentation/admin-guide/sysrq.rst
> @@ -161,6 +161,8 @@ Command Function
> will be printed to your console. (``0``, for example would make
> it so that only emergency messages like PANICs or OOPSes would
> make it to your console.)
> +
> +``D`` Dump the kernel ring buffer
> =========== ===================================================================
Nit, this doesn't line up anymore :(
next prev parent reply other threads:[~2023-12-21 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 13:39 [PATCH] tty/sysrq: Dump kernel ring buffer messages via sysrq Sreenath Vijayan
2023-12-21 16:52 ` Greg KH [this message]
2023-12-21 23:12 ` Randy Dunlap
2023-12-22 11:44 ` Sreenath Vijayan
2023-12-22 19:43 ` Randy Dunlap
2023-12-24 11:36 ` kernel test robot
2023-12-24 14:22 ` kernel test robot
2024-01-10 15:54 ` [PATCH v2] tty/sysrq: Dump printk " Sreenath Vijayan
2024-01-10 10:20 ` John Ogness
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=2023122144-enlarged-maggot-493a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anandakumar.balasubramaniam@sony.com \
--cc=corbet@lwn.net \
--cc=jirislaby@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sreenath.vijayan@sony.com \
--cc=taichi.shimoyashiki@sony.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