Lines Matching +full:per +full:- +full:console
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
52 You press the key combo :kbd:`ALT-SysRq-<command key>`.
63 You press :kbd:`ALT-STOP-<command key>`, I believe.
65 On the serial console (PC style standard serial ports only)
70 Press :kbd:`ALT - Print Screen` (or :kbd:`F13`) - :kbd:`<command key>`.
71 :kbd:`Print Screen` (or :kbd:`F13`) - :kbd:`<command key>` may suffice.
78 Write a character to /proc/sysrq-trigger. e.g.::
80 echo t > /proc/sysrq-trigger
106 here will display help. but ``h`` is easy to remember :-)
110 ``j`` Forcibly "Just thaw it" - filesystems frozen by the FIFREEZE ioctl.
113 console. NOTE: See important comments below in SAK section.
117 ``m`` Will dump current memory info to your console.
119 ``n`` Used to make RT tasks nice-able
123 ``p`` Will dump the current registers and flags to your console.
125 ``q`` Will dump per CPU lists of all armed hrtimers (but NOT regular
134 console.
136 ``u`` Will attempt to remount all mounted filesystems read-only.
138 ``v`` Forcefully restores framebuffer console
139 ``v`` Causes ETM buffer dump [ARM-specific]
147 ``y`` Show global CPU Registers [SPARC-64 specific]
151 ``0``-``9`` Sets the console log level, controlling which kernel messages
152 will be printed to your console. (``0``, for example would make
154 make it to your console.)
163 trojan program running at console which could grab your password
164 when you would try to login. It will kill all programs on given console,
185 shell that provides no graceful shutdown -- it will ensure your data is
190 running system's point of view, they will be remounted read-only. The remount
193 The loglevels ``0``-``9`` are useful when your console is being flooded with
195 the most urgent kernel messages from reaching your console. (They will
210 :kbd:`alt-sysrq-z`).
212 Switching to another virtual console (:kbd:`ALT+Fn`) and then back again
219 pre-defined value of 99
220 (see ``KEY_SYSRQ`` in ``include/uapi/linux/input-event-codes.h``), or
221 which don't have a SysRq key at all. In these cases, run ``showkey -s`` to find
263 When I hit a SysRq key combination only the header appears on the console?
266 Sysrq output is subject to the same console loglevel control as all
267 other console output. This means that if the kernel was booted 'quiet'
269 console, even though it will appear in the dmesg buffer, and be accessible
271 exception the header line from the sysrq command is passed to all console
274 Should you require the output on the console channel then you will need
275 to temporarily up the console loglevel using :kbd:`alt-sysrq-8` or::
277 echo 8 > /proc/sysrq-trigger
285 Just ask them on the linux-kernel mailing list:
286 linux-kernel@vger.kernel.org
291 - Written by Mydraal <vulpyne@vulpyne.net>
292 - Updated by Adam Sulmicki <adam@cfar.umd.edu>
293 - Updated by Jeremy M. Dolan <jmd@turbogeek.org> 2001/01/28 10:15:59
294 - Added to by Crutcher Dunnavant <crutcher+kernel@datastacks.com>