diff options
author | Sreenath Vijayan <[email protected]> | 2024-03-13 15:52:52 +0530 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2024-04-11 14:22:52 +0200 |
commit | 1b743485e27f3d874695434cc8103f557dfdf4b9 (patch) | |
tree | 14b82b81d65986d60c3042316a322f6590c3cdff /drivers/usb/cdns3/cdns3-trace.c | |
parent | 693f75b91a9171e99f84fc193e39f48e21ba4a4f (diff) |
tty/sysrq: Replay kernel log messages on consoles via sysrq
When terminal is unresponsive, one cannot use dmesg to view
the printk ring buffer messages. Also, syslog services may be
disabled, especially on embedded systems, to check the messages
after a reboot. In this scenario, replay the messages in printk
ring buffer on consoles via sysrq by pressing sysrq+R.
The console loglevel will determine which all kernel log messages
are displayed. The messages will be displayed only when
console_trylock() succeeds. Users could repeat the sysrq key when
it fails. If the owner of console subsystem lock is stuck,
repeating the key won't work.
Suggested-by: Petr Mladek <[email protected]>
Signed-off-by: Shimoyashiki Taichi <[email protected]>
Reviewed-by: John Ogness <[email protected]>
Signed-off-by: Sreenath Vijayan <[email protected]>
Link: https://lore.kernel.org/r/cc3b9b1aae60a236c6aed1dc7b0ffa2c7cd1f183.1710220326.git.sreenath.vijayan@sony.com
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'drivers/usb/cdns3/cdns3-trace.c')
0 files changed, 0 insertions, 0 deletions