Lines Matching +full:no +full:- +full:reset +full:- +full:on +full:- +full:init
22 - 0 - disable sysrq completely
23 - 1 - enable all functions of sysrq
24 - >1 - bitmask of allowed sysrq functions (see below for detailed function
27 2 = 0x2 - enable control of console logging level
28 4 = 0x4 - enable control of keyboard (SAK, unraw)
29 8 = 0x8 - enable debugging dumps of processes etc.
30 16 = 0x10 - enable sync command
31 32 = 0x20 - enable remount read-only
32 64 = 0x40 - enable signalling of processes (term, kill, oom-kill)
33 128 = 0x80 - allow reboot/poweroff
34 256 = 0x100 - allow nicing of all RT tasks
45 via a keyboard. Invocation of any operation via ``/proc/sysrq-trigger`` is
51 On x86
52 You press the key combo :kbd:`ALT-SysRq-<command key>`.
62 On SPARC
63 You press :kbd:`ALT-STOP-<command key>`, I believe.
65 On the serial console (PC style standard serial ports only)
69 On PowerPC
70 Press :kbd:`ALT - Print Screen` (or :kbd:`F13`) - :kbd:`<command key>`.
71 :kbd:`Print Screen` (or :kbd:`F13`) - :kbd:`<command key>` may suffice.
73 On other
77 On all
78 Write a single character to /proc/sysrq-trigger.
84 echo t > /proc/sysrq-trigger
89 echo _reisub > /proc/sysrq-trigger
107 ``e`` Send a SIGTERM to all processes, except for init.
115 here will display help. but ``h`` is easy to remember :-)
117 ``i`` Send a SIGKILL to all processes, except for init.
119 ``j`` Forcibly "Just thaw it" - filesystems frozen by the FIFREEZE ioctl.
121 ``k`` Secure Access Key (SAK) Kills all programs on the current virtual
128 ``n`` Used to make RT tasks nice-able
145 ``u`` Will attempt to remount all mounted filesystems read-only.
148 ``v`` Causes ETM buffer dump [ARM-specific]
152 ``x`` Used by xmon interface on ppc/powerpc platforms.
153 Show global PMU Registers on sparc64.
154 Dump all TLB entries on MIPS.
156 ``y`` Show global CPU Registers [SPARC-64 specific]
160 ``0``-``9`` Sets the console log level, controlling which kernel messages
165 ``R`` Replay the kernel log messages on consoles.
173 sak(k) (Secure Access Key) is useful when you want to be sure there is no
175 when you would try to login. It will kill all programs on given console,
177 the one from init, not some trojan program.
190 of pressing the "reset" button.
193 Note that this just triggers a crash if there is no dump mechanism available.
196 shell that provides no graceful shutdown -- it will ensure your data is
198 the "OK" and "Done" appear on the screen.
201 running system's point of view, they will be remounted read-only. The remount
202 isn't complete until you see the "OK" and "Done" message appear on the screen.
204 The loglevels ``0``-``9`` are useful when your console is being flooded with
220 messages depend on current console loglevel, which can be modified using
221 sysrq[0-9] (see above).
226 When this happens, try tapping shift, alt and control on both sides of the
228 :kbd:`alt-sysrq-z`).
237 pre-defined value of 99
238 (see ``KEY_SYSRQ`` in ``include/uapi/linux/input-event-codes.h``), or
239 which don't have a SysRq key at all. In these cases, run ``showkey -s`` to find
281 When I hit a SysRq key combination only the header appears on the console?
286 as is common on distro kernels the output may not appear on the actual
292 Should you require the output on the console channel then you will need
293 to temporarily up the console loglevel using :kbd:`alt-sysrq-8` or::
295 echo 8 > /proc/sysrq-trigger
303 Just ask them on the linux-kernel mailing list:
304 linux-kernel@vger.kernel.org
309 - Written by Mydraal <vulpyne@vulpyne.net>
310 - Updated by Adam Sulmicki <adam@cfar.umd.edu>
311 - Updated by Jeremy M. Dolan <jmd@turbogeek.org> 2001/01/28 10:15:59
312 - Added to by Crutcher Dunnavant <crutcher+kernel@datastacks.com>