aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/sysrq.txt
diff options
context:
space:
mode:
authorAndy Whitcroft <apw@canonical.com>2009-01-15 16:50:51 -0500
committerLinus Torvalds <torvalds@linux-foundation.org>2009-01-15 19:39:36 -0500
commit47c33d9c1984ae4c5bd1f144024eacc14c5bc0c0 (patch)
tree1b31cebe620ec044cfee695abe5cd6c70029de1a /Documentation/sysrq.txt
parent89365e264104b52da6a61c4e227bb5a934764fa7 (diff)
sysrq documentation: document why the command header only is shown
Document the interactions between loglevel and the sysrq output. Also document how to work round it should output be required on the console. Signed-off-by: Andy Whitcroft <apw@canonical.com> Cc: Martin Mares <mj@ucw.cz> Cc: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/sysrq.txt')
-rw-r--r--Documentation/sysrq.txt18
1 files changed, 18 insertions, 0 deletions
diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt
index 265f637b97d3..9e592c718afb 100644
--- a/Documentation/sysrq.txt
+++ b/Documentation/sysrq.txt
@@ -210,6 +210,24 @@ within a function called by handle_sysrq, you must be aware that you are in
210a lock (you are also in an interrupt handler, which means don't sleep!), so 210a lock (you are also in an interrupt handler, which means don't sleep!), so
211you must call __handle_sysrq_nolock instead. 211you must call __handle_sysrq_nolock instead.
212 212
213* When I hit a SysRq key combination only the header appears on the console?
214~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
215Sysrq output is subject to the same console loglevel control as all
216other console output. This means that if the kernel was booted 'quiet'
217as is common on distro kernels the output may not appear on the actual
218console, even though it will appear in the dmesg buffer, and be accessible
219via the dmesg command and to the consumers of /proc/kmsg. As a specific
220exception the header line from the sysrq command is passed to all console
221consumers as if the current loglevel was maximum. If only the header
222is emitted it is almost certain that the kernel loglevel is too low.
223Should you require the output on the console channel then you will need
224to temporarily up the console loglevel using alt-sysrq-8 or:
225
226 echo 8 > /proc/sysrq-trigger
227
228Remember to return the loglevel to normal after triggering the sysrq
229command you are interested in.
230
213* I have more questions, who can I ask? 231* I have more questions, who can I ask?
214~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 232~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
215And I'll answer any questions about the registration system you got, also 233And I'll answer any questions about the registration system you got, also