[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87plxgo21v.fsf@jogness.linutronix.de>
Date: Thu, 01 Feb 2024 12:35:32 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Sreenath Vijayan <sreenath.vijayan@...y.com>, corbet@....net,
gregkh@...uxfoundation.org, jirislaby@...nel.org, pmladek@...e.com
Cc: rdunlap@...radead.org, rostedt@...dmis.org, senozhatsky@...omium.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org, taichi.shimoyashiki@...y.com,
daniel.palmer@...y.com, anandakumar.balasubramaniam@...y.com,
sreenath.vijayan@...y.com
Subject: Re: [PATCH v4 2/2] tty/sysrq: Dump printk ring buffer messages via
sysrq
On 2024-02-01, Sreenath Vijayan <sreenath.vijayan@...y.com> wrote:
> When terminal is unresponsive, one cannot use dmesg to view printk
> ring buffer messages. Also, syslog services may be disabled,
> to check the messages after a reboot, especially on embedded systems.
> In this scenario, dump the printk ring buffer messages via sysrq
> by pressing sysrq+D.
>
> Signed-off-by: Sreenath Vijayan <sreenath.vijayan@...y.com>
> Signed-off-by: Shimoyashiki Taichi <taichi.shimoyashiki@...y.com>
Reviewed-by: John Ogness <john.ogness@...utronix.de>
Powered by blists - more mailing lists