- 1 Sysrq
- 1.1 What is the magic SysRq key?
- 1.2 How do I enable the magic SysRq key?
- 1.3 How do I use the magic SysRq key?
- 1.4 What are the 'command' keys?
- 1.5 Okay, so what can I use them for?
- 1.6 Troubleshooting
What is the magic SysRq key?
It is a 'magical' key combo you can hit which the kernel will respond to regardless of whatever else it is doing, unless it is completely locked up.
How do I enable the magic SysRq key?
You need to say "yes" to 'Magic SysRq key (CONFIG_MAGIC_SYSRQ)' when configuring the kernel. Stock Fedora and RHEL kernels do have this functionality enabled at compile-time, but the distributions disable it at boot time, by default, using sysctl.conf.
To re-enable it at boot time create config file in the
sysctl.d directory (e.g.
/etc/sysctl.d/90-sysrq.conf) with this line:
kernel.sysrq = 1
When running a kernel with SysRq compiled in, /proc/sys/kernel/sysrq controls the functions allowed to be invoked via the SysRq key. Here is the list of possible values in /proc/sys/kernel/sysrq:
- 0 - disable sysrq completely
- 1 - enable all functions of sysrq
- >1 - bitmask of allowed sysrq functions (see below for detailed function description):
- 2 - enable control of console logging level
- 4 - enable control of keyboard (SAK, unraw)
- 8 - enable debugging dumps of processes etc.
- 16 - enable sync command
- 32 - enable remount read-only
- 64 - enable signalling of processes (term, kill, oom-kill)
- 128 - allow reboot/poweroff
- 256 - allow nicing of all RT tasks
You can set the value in the file by the following command.
echo "number" >/proc/sys/kernel/sysrq
So to enable it would be.
echo "1" > /proc/sys/kernel/sysrq
Or also can enable it by doing.
sysctl -w kernel.sysrq=1
How do I use the magic SysRq key?
You press the key combo+ + .
You press+ +
Serial Console (PC style standard serial ports only )
You send a BREAK, then within 5 seconds a command key.
Press+ (or ) +
Write a character to /proc/sysrq-trigger:
echo t > /proc/sysrq-trigger
What are the 'command' keys?
b- Will immediately reboot the system without syncing or unmounting your disks.
c- Will perform a kexec reboot in order to take a crashdump.
d- Shows all locks that are held.
e- Send a SIGTERM to all processes, except for init.
f- Will call oom_kill to kill a memory hog process.
g- Used by kgdb on ppc and sh platforms.
h- Will display help (any key that is not listed here will bring forth help )
i- Send a SIGKILL to all processes, except for init.
k- Secure Access Key (SAK) Kills all programs on the current virtual terminal.
l- Shows a stack backtrace for all active CPUs.
m- Will dump current memory info to your console.
n- Used to make RT tasks nice-able
o- Will shut your system off (if configured and supported).
p- Will dump the current registers and flags to your console.
q- Will dump a list of all running timers.
r- Turns off keyboard raw mode and sets it to XLATE.
s- Will attempt to sync all mounted filesystems.
t- Will dump a list of current tasks and their information to your console.
u- Will attempt to remount all mounted filesystems read-only.
v- Dumps Voyager SMP processor info to your console.
w- Dumps tasks that are in uninterruptable (blocked) state.
x- Used by xmon interface on ppc/powerpc platforms.
9- Sets the console log level, controlling which kernel messages will be printed to your console. ('0', for example would make it so that only emergency messages like PANICs or OOPSes would make it to your console.)
Okay, so what can I use them for?
raw is very handy when your X server or a svgalib program crashes.
k (Secure Access Key) is useful when you want to be sure there is no trojan program running at console which could grab your password when you would try to login. It will kill all programs on given console, thus letting you make sure that the login prompt you see is actually the one from init, not some trojan program.
Others find it useful as (System Attention Key) which is useful when you want to exit a program that will not let you switch consoles. (For example, X or a svgalib program.)
boot is good when you're unable to shut down.
Crashdump can be used to manually trigger a
crashdump when the system is hung.
Sync is great when your system is locked up, it allows you to
sync your disks and will certainly lessen the chance of data loss and fscking.
Umount is basically useful in the same ways as
9 are useful when your console is being flooded with kernel messages you do not want to see. Selecting '0' will prevent all but the most urgent kernel messages from reaching your console.
erm and k
ill are useful if you have some sort of runaway process you are unable to kill any other way, especially if it's spawning other processes.
Hanging before initscripts get run
If the machine is hanging before the initscripts get to run, boot with
Sometimes SysRq seems to get 'stuck' after using it, what can I do?
Tapping, , and on both sides of the keyboard, and hitting an invalid sysrq sequence again will fix the problem. (i.e., something like + + ).
Switching to another virtual console (+ ) and then back again should also help.
I hit SysRq, but nothing seems to happen, what's wrong?
There are some keyboards that send different scancodes for SysRq than the pre-defined 0x54. So if SysRq doesn't work out of the box for a certain keyboard, run 'showkey -s' to find out the proper scancode sequence. Then use 'setkeycodes <sequence> 84' to define this sequence to the usual SysRq code (84 is decimal for 0x54). It's probably best to put this command in a boot script.
I want to add SysRQ key events to a module, how does it work?
In order to register a basic function with the table, you must first include the header 'include/linux/sysrq.h', this will define everything else you need. Next, you must create a sysrq_key_op struct, and populate it with...
- The key handler function you will use.
- A help_msg string, that will print when SysRQ prints help
- An action_msg string, that will print right before your handler is called. Your handler must conform to the prototype in 'sysrq.h'.
After the sysrq_key_op is created, you can call the kernel function register_sysrq_key(int key, struct sysrq_key_op *op_p); this will register the operation pointed to by 'op_p' at table key 'key', if that slot in the table is blank. At module unload time, you must call the function unregister_sysrq_key(int key, struct sysrq_key_op *op_p), which will remove the key op pointed to by 'op_p' from the key 'key', if and only if it is currently registered in that slot. This is in case the slot has been overwritten since you registered it.
The Magic SysRQ system works by registering key operations against a key op lookup table, which is defined in 'drivers/char/sysrq.c'. This key table has a number of operations registered into it at compile time, but is mutable, and 2 functions are exported for interface to it the register_sysrq_key and unregister_sysrq_key. Of course, never ever leave an invalid pointer in the table. I.e., when your module that called register_sysrq_key() exits, it must call unregister_sysrq_key() to clean up the sysrq key table entry that it used.
If for some reason you feel the need to call the handle_sysrq function from within a function called by handle_sysrq, you must be aware that you are in a lock (you are also in an interrupt handler, which means don't sleep!), so you must call __handle_sysrq_nolock instead.