Re: [PATCH] Documentation: Update path to sysrq.txt
On Fri, 24 Feb 2017 10:42:14 +0200
Krzysztof Kozlowski <k...@kernel.org> wrote:
> Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
> sysrq.txt leaving old paths in the kernel docs.
Applied to the docs tree, thanks.
jon
Re: [PATCH] Documentation: Update path to sysrq.txt
On Fri, 24 Feb 2017 10:42:14 +0200
Krzysztof Kozlowski wrote:
> Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
> sysrq.txt leaving old paths in the kernel docs.
Applied to the docs tree, thanks.
jon
Re: [PATCH] Documentation: Update path to sysrq.txt
Em Fri, 24 Feb 2017 10:42:14 +0200
Krzysztof Kozlowski <k...@kernel.org> escreveu:
> Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
> sysrq.txt leaving old paths in the kernel docs.
>
> Signed-off-by: Krzysztof Kozlowski <k...@kernel.org>
Reviewed-by: Mauro Carvalho Chehab <mche...@s-opensource.com>
> ---
> Documentation/media/v4l-drivers/bttv.rst | 2 +-
> Documentation/s390/Debugging390.txt | 2 +-
> Documentation/sysctl/kernel.txt | 2 +-
> Documentation/virtual/uml/UserModeLinux-HOWTO.txt | 6 +++---
> 4 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/media/v4l-drivers/bttv.rst
> b/Documentation/media/v4l-drivers/bttv.rst
> index bc63b12efafd..195ccaac2816 100644
> --- a/Documentation/media/v4l-drivers/bttv.rst
> +++ b/Documentation/media/v4l-drivers/bttv.rst
> @@ -312,7 +312,7 @@ information out of a register+stack dump printed by the
> kernel on
> protection faults (so-called "kernel oops").
>
> If you run into some kind of deadlock, you can try to dump a call trace
> -for each process using sysrq-t (see Documentation/sysrq.txt).
> +for each process using sysrq-t (see Documentation/admin-guide/sysrq.rst).
> This way it is possible to figure where *exactly* some process in "D"
> state is stuck.
>
> diff --git a/Documentation/s390/Debugging390.txt
> b/Documentation/s390/Debugging390.txt
> index 3df8babcdc41..5ae7f868a007 100644
> --- a/Documentation/s390/Debugging390.txt
> +++ b/Documentation/s390/Debugging390.txt
> @@ -2116,7 +2116,7 @@ The sysrq key reading is very picky ( I have to type
> the keys in an
> This is particularly useful for syncing disks unmounting & rebooting
> if the machine gets partially hung.
>
> -Read Documentation/sysrq.txt for more info
> +Read Documentation/admin-guide/sysrq.rst for more info
>
> References:
> ===
> diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
> index a32b4b748644..bac23c198360 100644
> --- a/Documentation/sysctl/kernel.txt
> +++ b/Documentation/sysctl/kernel.txt
> @@ -85,7 +85,7 @@ show up in /proc/sys/kernel:
> - softlockup_all_cpu_backtrace
> - soft_watchdog
> - stop-a [ SPARC only ]
> -- sysrq ==> Documentation/sysrq.txt
> +- sysrq ==> Documentation/admin-guide/sysrq.rst
> - sysctl_writes_strict
> - tainted
> - threads-max
> diff --git a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> index f4099ca6b483..87b80f589e1c 100644
> --- a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> +++ b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> @@ -2401,9 +2401,9 @@
>
>This takes one argument, which is a single letter. It calls the
>generic kernel's SysRq driver, which does whatever is called for by
> - that argument. See the SysRq documentation in Documentation/sysrq.txt
> - in your favorite kernel tree to see what letters are valid and what
> - they do.
> + that argument. See the SysRq documentation in
> + Documentation/admin-guide/sysrq.rst in your favorite kernel tree to
> + see what letters are valid and what they do.
>
>
>
Thanks,
Mauro
Re: [PATCH] Documentation: Update path to sysrq.txt
Em Fri, 24 Feb 2017 10:42:14 +0200
Krzysztof Kozlowski escreveu:
> Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
> sysrq.txt leaving old paths in the kernel docs.
>
> Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Mauro Carvalho Chehab
> ---
> Documentation/media/v4l-drivers/bttv.rst | 2 +-
> Documentation/s390/Debugging390.txt | 2 +-
> Documentation/sysctl/kernel.txt | 2 +-
> Documentation/virtual/uml/UserModeLinux-HOWTO.txt | 6 +++---
> 4 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/media/v4l-drivers/bttv.rst
> b/Documentation/media/v4l-drivers/bttv.rst
> index bc63b12efafd..195ccaac2816 100644
> --- a/Documentation/media/v4l-drivers/bttv.rst
> +++ b/Documentation/media/v4l-drivers/bttv.rst
> @@ -312,7 +312,7 @@ information out of a register+stack dump printed by the
> kernel on
> protection faults (so-called "kernel oops").
>
> If you run into some kind of deadlock, you can try to dump a call trace
> -for each process using sysrq-t (see Documentation/sysrq.txt).
> +for each process using sysrq-t (see Documentation/admin-guide/sysrq.rst).
> This way it is possible to figure where *exactly* some process in "D"
> state is stuck.
>
> diff --git a/Documentation/s390/Debugging390.txt
> b/Documentation/s390/Debugging390.txt
> index 3df8babcdc41..5ae7f868a007 100644
> --- a/Documentation/s390/Debugging390.txt
> +++ b/Documentation/s390/Debugging390.txt
> @@ -2116,7 +2116,7 @@ The sysrq key reading is very picky ( I have to type
> the keys in an
> This is particularly useful for syncing disks unmounting & rebooting
> if the machine gets partially hung.
>
> -Read Documentation/sysrq.txt for more info
> +Read Documentation/admin-guide/sysrq.rst for more info
>
> References:
> ===
> diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
> index a32b4b748644..bac23c198360 100644
> --- a/Documentation/sysctl/kernel.txt
> +++ b/Documentation/sysctl/kernel.txt
> @@ -85,7 +85,7 @@ show up in /proc/sys/kernel:
> - softlockup_all_cpu_backtrace
> - soft_watchdog
> - stop-a [ SPARC only ]
> -- sysrq ==> Documentation/sysrq.txt
> +- sysrq ==> Documentation/admin-guide/sysrq.rst
> - sysctl_writes_strict
> - tainted
> - threads-max
> diff --git a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> index f4099ca6b483..87b80f589e1c 100644
> --- a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> +++ b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> @@ -2401,9 +2401,9 @@
>
>This takes one argument, which is a single letter. It calls the
>generic kernel's SysRq driver, which does whatever is called for by
> - that argument. See the SysRq documentation in Documentation/sysrq.txt
> - in your favorite kernel tree to see what letters are valid and what
> - they do.
> + that argument. See the SysRq documentation in
> + Documentation/admin-guide/sysrq.rst in your favorite kernel tree to
> + see what letters are valid and what they do.
>
>
>
Thanks,
Mauro
[PATCH] Documentation: Update path to sysrq.txt
Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
sysrq.txt leaving old paths in the kernel docs.
Signed-off-by: Krzysztof Kozlowski <k...@kernel.org>
---
Documentation/media/v4l-drivers/bttv.rst | 2 +-
Documentation/s390/Debugging390.txt | 2 +-
Documentation/sysctl/kernel.txt | 2 +-
Documentation/virtual/uml/UserModeLinux-HOWTO.txt | 6 +++---
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/media/v4l-drivers/bttv.rst
b/Documentation/media/v4l-drivers/bttv.rst
index bc63b12efafd..195ccaac2816 100644
--- a/Documentation/media/v4l-drivers/bttv.rst
+++ b/Documentation/media/v4l-drivers/bttv.rst
@@ -312,7 +312,7 @@ information out of a register+stack dump printed by the
kernel on
protection faults (so-called "kernel oops").
If you run into some kind of deadlock, you can try to dump a call trace
-for each process using sysrq-t (see Documentation/sysrq.txt).
+for each process using sysrq-t (see Documentation/admin-guide/sysrq.rst).
This way it is possible to figure where *exactly* some process in "D"
state is stuck.
diff --git a/Documentation/s390/Debugging390.txt
b/Documentation/s390/Debugging390.txt
index 3df8babcdc41..5ae7f868a007 100644
--- a/Documentation/s390/Debugging390.txt
+++ b/Documentation/s390/Debugging390.txt
@@ -2116,7 +2116,7 @@ The sysrq key reading is very picky ( I have to type the
keys in an
This is particularly useful for syncing disks unmounting & rebooting
if the machine gets partially hung.
-Read Documentation/sysrq.txt for more info
+Read Documentation/admin-guide/sysrq.rst for more info
References:
===
diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
index a32b4b748644..bac23c198360 100644
--- a/Documentation/sysctl/kernel.txt
+++ b/Documentation/sysctl/kernel.txt
@@ -85,7 +85,7 @@ show up in /proc/sys/kernel:
- softlockup_all_cpu_backtrace
- soft_watchdog
- stop-a [ SPARC only ]
-- sysrq ==> Documentation/sysrq.txt
+- sysrq ==> Documentation/admin-guide/sysrq.rst
- sysctl_writes_strict
- tainted
- threads-max
diff --git a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
index f4099ca6b483..87b80f589e1c 100644
--- a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
+++ b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
@@ -2401,9 +2401,9 @@
This takes one argument, which is a single letter. It calls the
generic kernel's SysRq driver, which does whatever is called for by
- that argument. See the SysRq documentation in Documentation/sysrq.txt
- in your favorite kernel tree to see what letters are valid and what
- they do.
+ that argument. See the SysRq documentation in
+ Documentation/admin-guide/sysrq.rst in your favorite kernel tree to
+ see what letters are valid and what they do.
--
2.9.3
[PATCH] Documentation: Update path to sysrq.txt
Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
sysrq.txt leaving old paths in the kernel docs.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/media/v4l-drivers/bttv.rst | 2 +-
Documentation/s390/Debugging390.txt | 2 +-
Documentation/sysctl/kernel.txt | 2 +-
Documentation/virtual/uml/UserModeLinux-HOWTO.txt | 6 +++---
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/media/v4l-drivers/bttv.rst
b/Documentation/media/v4l-drivers/bttv.rst
index bc63b12efafd..195ccaac2816 100644
--- a/Documentation/media/v4l-drivers/bttv.rst
+++ b/Documentation/media/v4l-drivers/bttv.rst
@@ -312,7 +312,7 @@ information out of a register+stack dump printed by the
kernel on
protection faults (so-called "kernel oops").
If you run into some kind of deadlock, you can try to dump a call trace
-for each process using sysrq-t (see Documentation/sysrq.txt).
+for each process using sysrq-t (see Documentation/admin-guide/sysrq.rst).
This way it is possible to figure where *exactly* some process in "D"
state is stuck.
diff --git a/Documentation/s390/Debugging390.txt
b/Documentation/s390/Debugging390.txt
index 3df8babcdc41..5ae7f868a007 100644
--- a/Documentation/s390/Debugging390.txt
+++ b/Documentation/s390/Debugging390.txt
@@ -2116,7 +2116,7 @@ The sysrq key reading is very picky ( I have to type the
keys in an
This is particularly useful for syncing disks unmounting & rebooting
if the machine gets partially hung.
-Read Documentation/sysrq.txt for more info
+Read Documentation/admin-guide/sysrq.rst for more info
References:
===
diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
index a32b4b748644..bac23c198360 100644
--- a/Documentation/sysctl/kernel.txt
+++ b/Documentation/sysctl/kernel.txt
@@ -85,7 +85,7 @@ show up in /proc/sys/kernel:
- softlockup_all_cpu_backtrace
- soft_watchdog
- stop-a [ SPARC only ]
-- sysrq ==> Documentation/sysrq.txt
+- sysrq ==> Documentation/admin-guide/sysrq.rst
- sysctl_writes_strict
- tainted
- threads-max
diff --git a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
index f4099ca6b483..87b80f589e1c 100644
--- a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
+++ b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
@@ -2401,9 +2401,9 @@
This takes one argument, which is a single letter. It calls the
generic kernel's SysRq driver, which does whatever is called for by
- that argument. See the SysRq documentation in Documentation/sysrq.txt
- in your favorite kernel tree to see what letters are valid and what
- they do.
+ that argument. See the SysRq documentation in
+ Documentation/admin-guide/sysrq.rst in your favorite kernel tree to
+ see what letters are valid and what they do.
--
2.9.3
[PATCH 28/32] Documentation/sysrq.txt: convert to ReST markup
- Fix document title; - use a table for the valid commands; - use quote blocks where needed; - use monotonic fonts for config options and file names; - adjust whitespaces and blank lines; - add it to the user's book. Signed-off-by: Mauro Carvalho Chehab <mche...@s-opensource.com> --- Documentation/sysrq.txt | 266 --- Documentation/user/index.rst | 1 + Documentation/user/sysrq.rst | 1 + 3 files changed, 151 insertions(+), 117 deletions(-) create mode 12 Documentation/user/sysrq.rst diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt index 3a3b30ac2a75..d1712ea2d314 100644 --- a/Documentation/sysrq.txt +++ b/Documentation/sysrq.txt @@ -1,23 +1,29 @@ Linux Magic System Request Key Hacks + + Documentation for sysrq.c -* What is the magic SysRq key? -~~~ +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? -~~~ +How do I enable the magic SysRq key? + + You need to say "yes" to 'Magic SysRq key (CONFIG_MAGIC_SYSRQ)' when configuring the kernel. When running a kernel with SysRq compiled in, /proc/sys/kernel/sysrq controls the functions allowed to be invoked via the SysRq key. The default value in this file is set by the CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE config symbol, which itself defaults to 1. 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): + + - 0 - disable sysrq completely + - 1 - enable all functions of sysrq + - >1 - bitmask of allowed sysrq functions (see below for detailed function + description):: + 2 = 0x2 - enable control of console logging level 4 = 0x4 - enable control of keyboard (SAK, unraw) 8 = 0x8 - enable debugging dumps of processes etc. @@ -27,112 +33,126 @@ to 1. Here is the list of possible values in /proc/sys/kernel/sysrq: 128 = 0x80 - allow reboot/poweroff 256 = 0x100 - allow nicing of all RT tasks -You can set the value in the file by the following command: +You can set the value in the file by the following command:: + echo "number" >/proc/sys/kernel/sysrq The number may be written here either as decimal or as hexadecimal with the 0x prefix. CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE must always be written in hexadecimal. -Note that the value of /proc/sys/kernel/sysrq influences only the invocation -via a keyboard. Invocation of any operation via /proc/sysrq-trigger is always -allowed (by a user with admin privileges). +Note that the value of ``/proc/sys/kernel/sysrq`` influences only the invocation +via a keyboard. Invocation of any operation via ``/proc/sysrq-trigger`` is +always allowed (by a user with admin privileges). -* How do I use the magic SysRq key? - -On x86 - You press the key combo 'ALT-SysRq-'. Note - Some +How do I use the magic SysRq key? +~ + +On x86 - You press the key combo :kbd:`ALT-SysRq-`. + +.. note:: + Some keyboards may not have a key labeled 'SysRq'. The 'SysRq' key is also known as the 'Print Screen' key. Also some keyboards cannot handle so many keys being pressed at the same time, so you might - have better luck with "press Alt", "press SysRq", "release SysRq", - "press ", release everything. + have better luck with press :kbd:`Alt`, press :kbd:`SysRq`, + release :kbd:`SysRq`, press :kbd:``, release everything. -On SPARC - You press 'ALT-STOP-', I believe. +On SPARC - You press :kbd:`ALT-STOP-`, I believe. -On the serial console (PC style standard serial ports only) - - You send a BREAK, then within 5 seconds a command key. Sending - BREAK twice is interpreted as a normal BREAK. +On the serial console (PC style standard serial ports only) +You send a ``BREAK``, then within 5 seconds a command key. Sending +``BREAK`` twice is interpreted as a normal BREAK. -On PowerPC - Press 'ALT - Print Screen (or F13) - , - Print Screen (or F13) - may suffice. +On PowerPC + Press :kbd:`ALT - Print Screen` (or :kbd:`F13`) - :kbd:``, +:kbd:`Print Screen` (or :kbd:`F13`) - :kbd:`` may suffice. -On other - If you know of the key combos for other architectures, please - let me know so I can add them to this section. +On other + If you know of the key combos for other architectures, please
[PATCH 28/32] Documentation/sysrq.txt: convert to ReST markup
- Fix document title; - use a table for the valid commands; - use quote blocks where needed; - use monotonic fonts for config options and file names; - adjust whitespaces and blank lines; - add it to the user's book. Signed-off-by: Mauro Carvalho Chehab --- Documentation/sysrq.txt | 266 --- Documentation/user/index.rst | 1 + Documentation/user/sysrq.rst | 1 + 3 files changed, 151 insertions(+), 117 deletions(-) create mode 12 Documentation/user/sysrq.rst diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt index 3a3b30ac2a75..d1712ea2d314 100644 --- a/Documentation/sysrq.txt +++ b/Documentation/sysrq.txt @@ -1,23 +1,29 @@ Linux Magic System Request Key Hacks + + Documentation for sysrq.c -* What is the magic SysRq key? -~~~ +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? -~~~ +How do I enable the magic SysRq key? + + You need to say "yes" to 'Magic SysRq key (CONFIG_MAGIC_SYSRQ)' when configuring the kernel. When running a kernel with SysRq compiled in, /proc/sys/kernel/sysrq controls the functions allowed to be invoked via the SysRq key. The default value in this file is set by the CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE config symbol, which itself defaults to 1. 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): + + - 0 - disable sysrq completely + - 1 - enable all functions of sysrq + - >1 - bitmask of allowed sysrq functions (see below for detailed function + description):: + 2 = 0x2 - enable control of console logging level 4 = 0x4 - enable control of keyboard (SAK, unraw) 8 = 0x8 - enable debugging dumps of processes etc. @@ -27,112 +33,126 @@ to 1. Here is the list of possible values in /proc/sys/kernel/sysrq: 128 = 0x80 - allow reboot/poweroff 256 = 0x100 - allow nicing of all RT tasks -You can set the value in the file by the following command: +You can set the value in the file by the following command:: + echo "number" >/proc/sys/kernel/sysrq The number may be written here either as decimal or as hexadecimal with the 0x prefix. CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE must always be written in hexadecimal. -Note that the value of /proc/sys/kernel/sysrq influences only the invocation -via a keyboard. Invocation of any operation via /proc/sysrq-trigger is always -allowed (by a user with admin privileges). +Note that the value of ``/proc/sys/kernel/sysrq`` influences only the invocation +via a keyboard. Invocation of any operation via ``/proc/sysrq-trigger`` is +always allowed (by a user with admin privileges). -* How do I use the magic SysRq key? - -On x86 - You press the key combo 'ALT-SysRq-'. Note - Some +How do I use the magic SysRq key? +~ + +On x86 - You press the key combo :kbd:`ALT-SysRq-`. + +.. note:: + Some keyboards may not have a key labeled 'SysRq'. The 'SysRq' key is also known as the 'Print Screen' key. Also some keyboards cannot handle so many keys being pressed at the same time, so you might - have better luck with "press Alt", "press SysRq", "release SysRq", - "press ", release everything. + have better luck with press :kbd:`Alt`, press :kbd:`SysRq`, + release :kbd:`SysRq`, press :kbd:``, release everything. -On SPARC - You press 'ALT-STOP-', I believe. +On SPARC - You press :kbd:`ALT-STOP-`, I believe. -On the serial console (PC style standard serial ports only) - - You send a BREAK, then within 5 seconds a command key. Sending - BREAK twice is interpreted as a normal BREAK. +On the serial console (PC style standard serial ports only) +You send a ``BREAK``, then within 5 seconds a command key. Sending +``BREAK`` twice is interpreted as a normal BREAK. -On PowerPC - Press 'ALT - Print Screen (or F13) - , - Print Screen (or F13) - may suffice. +On PowerPC + Press :kbd:`ALT - Print Screen` (or :kbd:`F13`) - :kbd:``, +:kbd:`Print Screen` (or :kbd:`F13`) - :kbd:`` may suffice. -On other - If you know of the key combos for other architectures, please - let me know so I can add them to this section. +On other + If you know of the key combos for other architectures, please +let me know so I can ad
[PATCH] Documentation/sysrq.txt: added short description for 'Q' (timerlist)
Hi, I added the 'Q' to list. A short description in the `Ok, so what can I use them for'-section, on when or why to use it would be nice! Signed-off-by: Johannes Weiner <[EMAIL PROTECTED]> diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt index 452c0f1..d43aa9d 100644 --- a/Documentation/sysrq.txt +++ b/Documentation/sysrq.txt @@ -93,6 +93,8 @@ On all - write a character to /proc/sysrq-trigger. e.g.: '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.
[PATCH] Documentation/sysrq.txt: added short description for 'Q' (timerlist)
Hi, I added the 'Q' to list. A short description in the `Ok, so what can I use them for'-section, on when or why to use it would be nice! Signed-off-by: Johannes Weiner [EMAIL PROTECTED] diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt index 452c0f1..d43aa9d 100644 --- a/Documentation/sysrq.txt +++ b/Documentation/sysrq.txt @@ -93,6 +93,8 @@ On all - write a character to /proc/sysrq-trigger. e.g.: '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.
Re: sysrq.txt
> > Well, as there is no keyboard combo that works on every Mac, I think we should >> list every known to be working combo. >> >> Like: >> >> On PowerPC - Press 'ALT - Print Screen (or F13) - , >> Print Screen (or F13) - may suffice. > >Sounds good. > >> Maybe it's a good idea to include F13's keycode, which I don't know. > >Nah. I think we should try and fix this sometime tho. Perhaps the round >powerbutton on the keyboard could do 'F13' (and add this to the list..) FWIW, the F9 key on a G3 PowerBook is labeled "prt screen", and you get that function with the "fn" key, not the "alt" key (which is a secondary label on the "opt" key). -- /Jonathan Lundell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Tue, Mar 20, 2001 at 02:07:13AM +0100, J. Michael Kolbe wrote: [snip] > Well, as there is no keyboard combo that works on every Mac, I think we should > list every known to be working combo. > > Like: > > On PowerPC - Press 'ALT - Print Screen (or F13) - , > Print Screen (or F13) - may suffice. Sounds good. > Maybe it's a good idea to include F13's keycode, which I don't know. Nah. I think we should try and fix this sometime tho. Perhaps the round powerbutton on the keyboard could do 'F13' (and add this to the list..) -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Tue, Mar 20, 2001 at 01:00:53AM +0100, J. Michael Kolbe wrote: > Hi. > > On Mon, Mar 19, 2001 at 04:21:35PM -0700, Tom Rini wrote: > > On Mon, Mar 19, 2001 at 11:14:03PM +, Andrew Morton wrote: > > > > > I included Mr Kolbe's one-liner in the SAK patch which I put > > > out on Sunday. Now my head is spinning. > > > > > > What *should* the change to sysrq.txt say? > > > > Well, I think: > > > > On PowerPC - You press 'ALT-Print Screen (or F13)- > > > > Which is what 2.2 says, but mentions F13 directly (incase print screen isn't > > on the key.). The above even makes sense for 2 of my machines which have > > working sysrq and keyboards. > > Well, I've just found an old USB Keyboard, none of the mentioned > Keyboard combos work, as there is neither F13 nor PrintScreen. Yes, as SysRq quite possibly doesn't work on (since none of the keys on it send the right keycode.) > > Btw, I'm using an old Newworld G3, the one with ADB. The old one. :) > I'd say sysrq.txt should say: > > On PowerPC - Press 'ALT - Print Screen (or F13) - > On Newworld PPC - You press 'Keypad+ - Print Screen (or F13) - > > I'm still trying to figure out how to do it with the F13-less Keyboard.. Er, I thought you just said you did? What keycodes are you using? Most "Newworld" only have the F13-less keyboard. Which sort of raises the question of how 'Keypad +' worked instead of the "ALT" key (either option/alt or the scroll key, whichever changes VC). Which sounds more like a fluke then anything else. Which keyboard worked with 'Keypad +' ? The ADB one? After some quick playing with my oldworld machine, Just F13 - is sufficient. I'm not sure about PReP tho (so it's probably not worth saying you don't need "ALT"). -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Mon, Mar 19, 2001 at 11:56:19PM +0100, J. Michael Kolbe wrote: > On Mon, Mar 19, 2001 at 01:46:53PM -0700, Tom Rini wrote: > > On Mon, Mar 19, 2001 at 08:37:00PM +0100, J. Michael Kolbe wrote: > > > On Mon, Mar 19, 2001 at 09:15:59AM -0700, Tom Rini wrote: > > > > Speaking of reversed, there's a slightly "nicer" one in 2.2.18+: > > > > On PowerPC - You press 'ALT-Print Screen-'. > > > > > > > > (And yes, all the apple keyboards I've seen w/ F13 have Print Screen > > > > right below it). Tho I'm also rather sure this didn't get into > > > > Linus' tree until after the 2.3 split.. > > > > > > > Well, my Apple Keyboard doesn't. It's F13. And it doesn't work with 'ALT'. > > > I suppose that's why it didn't get into the mainstream tree. > > > > But anyways. My objects were it's not just "macs". And not all keyboards > > have "F13" written on them as well as Print Screen. Which is why I think > > what 2.2 has is what 2.4 should have. Or if yours doesn't say Print Screen: > > > > On PowerPC - You press 'ALT-Print Screen (or F13)- > > > > As to weather or not it's the key which says "ALT" on it or not, it is the > > key which provides the ALT keycode in linux. Or it very well should be, for > > consistencys sake. > > > Keypad'+''s keycode is 69, while ALT's keycode is 58. Err, so? The sysrq code is triggered by "ALT" (which on PPC can be any number of things, depending on keyboard and other stuff) and the SYSRQ key. It's either 0x69 or 0x54, which is "F13" in either translated keycodes or ADB respectivly. > Besides, I have never seen an Apple Keyboard without an F13 Key. All of the USB keyboards, up until recently. > So, it's "Keypad'+'-F13 (or Print Screen)-". > Any objection? Well, where does that work? My PReP works fine w/ ALT-printscrn-key My old pmac is ALT-printscrn-key, and I don't have F13 on my other keyboard. So yes, I object because I'm not sure where your sugjestion works. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Mon, Mar 19, 2001 at 08:37:00PM +0100, J. Michael Kolbe wrote: > On Mon, Mar 19, 2001 at 09:15:59AM -0700, Tom Rini wrote: > > Speaking of reversed, there's a slightly "nicer" one in 2.2.18+: > > On PowerPC - You press 'ALT-Print Screen-'. > > > > (And yes, all the apple keyboards I've seen w/ F13 have Print Screen > > right below it). Tho I'm also rather sure this didn't get into > > Linus' tree until after the 2.3 split.. > > > Well, my Apple Keyboard doesn't. It's F13. And it doesn't work with 'ALT'. > I suppose that's why it didn't get into the mainstream tree. But anyways. My objects were it's not just "macs". And not all keyboards have "F13" written on them as well as Print Screen. Which is why I think what 2.2 has is what 2.4 should have. Or if yours doesn't say Print Screen: On PowerPC - You press 'ALT-Print Screen (or F13)- As to weather or not it's the key which says "ALT" on it or not, it is the key which provides the ALT keycode in linux. Or it very well should be, for consistencys sake. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Mon, Mar 19, 2001 at 08:37:00PM +0100, J. Michael Kolbe wrote: > On Mon, Mar 19, 2001 at 09:15:59AM -0700, Tom Rini wrote: > > Speaking of reversed, there's a slightly "nicer" one in 2.2.18+: > > On PowerPC - You press 'ALT-Print Screen-'. > > > > (And yes, all the apple keyboards I've seen w/ F13 have Print Screen > > right below it). Tho I'm also rather sure this didn't get into > > Linus' tree until after the 2.3 split.. > > > Well, my Apple Keyboard doesn't. It's F13. And it doesn't work with 'ALT'. Which? And it should indeed work with the "alt" key (ie the one for changing VCs). > I suppose that's why it didn't get into the mainstream tree. Er, 2.2 is mainstream. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Sun, Mar 18, 2001 at 11:39:55PM +0100, Pavel Machek wrote: > Hi! > > > I've found that the Sysrq Keys on Apple Computers > > are 'Keypad+-F13-', maybe it would > > be a good idea to include that in Documentation/sysrq.txt. > > > > The Patch: > > This patch is reversed, but otherwise looks okay. Generate > non-reversed one and mail it to linus, possibly saying I agree. Speaking of reversed, there's a slightly "nicer" one in 2.2.18+: On PowerPC - You press 'ALT-Print Screen-'. (And yes, all the apple keyboards I've seen w/ F13 have Print Screen right below it). Tho I'm also rather sure this didn't get into Linus' tree until after the 2.3 split.. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Sun, Mar 18, 2001 at 11:39:55PM +0100, Pavel Machek wrote: Hi! I've found that the Sysrq Keys on Apple Computers are 'Keypad+-F13-command key', maybe it would be a good idea to include that in Documentation/sysrq.txt. The Patch: This patch is reversed, but otherwise looks okay. Generate non-reversed one and mail it to linus, possibly saying I agree. Speaking of reversed, there's a slightly "nicer" one in 2.2.18+: On PowerPC - You press 'ALT-Print Screen-command key'. (And yes, all the apple keyboards I've seen w/ F13 have Print Screen right below it). Tho I'm also rather sure this didn't get into Linus' tree until after the 2.3 split.. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Mon, Mar 19, 2001 at 08:37:00PM +0100, J. Michael Kolbe wrote: On Mon, Mar 19, 2001 at 09:15:59AM -0700, Tom Rini wrote: Speaking of reversed, there's a slightly "nicer" one in 2.2.18+: On PowerPC - You press 'ALT-Print Screen-command key'. (And yes, all the apple keyboards I've seen w/ F13 have Print Screen right below it). Tho I'm also rather sure this didn't get into Linus' tree until after the 2.3 split.. Well, my Apple Keyboard doesn't. It's F13. And it doesn't work with 'ALT'. Which? And it should indeed work with the "alt" key (ie the one for changing VCs). I suppose that's why it didn't get into the mainstream tree. Er, 2.2 is mainstream. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
On Mon, Mar 19, 2001 at 08:37:00PM +0100, J. Michael Kolbe wrote: On Mon, Mar 19, 2001 at 09:15:59AM -0700, Tom Rini wrote: Speaking of reversed, there's a slightly "nicer" one in 2.2.18+: On PowerPC - You press 'ALT-Print Screen-command key'. (And yes, all the apple keyboards I've seen w/ F13 have Print Screen right below it). Tho I'm also rather sure this didn't get into Linus' tree until after the 2.3 split.. Well, my Apple Keyboard doesn't. It's F13. And it doesn't work with 'ALT'. I suppose that's why it didn't get into the mainstream tree. But anyways. My objects were it's not just "macs". And not all keyboards have "F13" written on them as well as Print Screen. Which is why I think what 2.2 has is what 2.4 should have. Or if yours doesn't say Print Screen: On PowerPC - You press 'ALT-Print Screen (or F13)-command key As to weather or not it's the key which says "ALT" on it or not, it is the key which provides the ALT keycode in linux. Or it very well should be, for consistencys sake. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
Well, as there is no keyboard combo that works on every Mac, I think we should list every known to be working combo. Like: On PowerPC - Press 'ALT - Print Screen (or F13) - command key, Print Screen (or F13) - command key may suffice. Sounds good. Maybe it's a good idea to include F13's keycode, which I don't know. Nah. I think we should try and fix this sometime tho. Perhaps the round powerbutton on the keyboard could do 'F13' (and add this to the list..) FWIW, the F9 key on a G3 PowerBook is labeled "prt screen", and you get that function with the "fn" key, not the "alt" key (which is a secondary label on the "opt" key). -- /Jonathan Lundell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
Hi!
> I've found that the Sysrq Keys on Apple Computers
> are 'Keypad+-F13-', maybe it would
> be a good idea to include that in Documentation/sysrq.txt.
>
> The Patch:
This patch is reversed, but otherwise looks okay. Generate
non-reversed one and mail it to linus, possibly saying I agree.
Pavel
> +++ sysrq.txt Tue Dec 12 20:46:38 2000
> @@ -29,8 +29,6 @@
> You send a BREAK, then within 5 seconds a command key. Sending
> BREAK twice is interpreted as a normal BREAK.
>
> -On Mac - Press 'Keypad+-F13-'
> -
> On other - If you know of the key combos for other architectures, please
> let me know so I can add them to this section.
>
>
> regards,
> jmk
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: sysrq.txt
Hi! I've found that the Sysrq Keys on Apple Computers are 'Keypad+-F13-command key', maybe it would be a good idea to include that in Documentation/sysrq.txt. The Patch: This patch is reversed, but otherwise looks okay. Generate non-reversed one and mail it to linus, possibly saying I agree. Pavel +++ sysrq.txt Tue Dec 12 20:46:38 2000 @@ -29,8 +29,6 @@ You send a BREAK, then within 5 seconds a command key. Sending BREAK twice is interpreted as a normal BREAK. -On Mac - Press 'Keypad+-F13-command key' - On other - If you know of the key combos for other architectures, please let me know so I can add them to this section. regards, jmk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
sysrq.txt
Hello, I've found that the Sysrq Keys on Apple Computers are 'Keypad+-F13-', maybe it would be a good idea to include that in Documentation/sysrq.txt. The Patch: +++ sysrq.txt Tue Dec 12 20:46:38 2000 @@ -29,8 +29,6 @@ You send a BREAK, then within 5 seconds a command key. Sending BREAK twice is interpreted as a normal BREAK. -On Mac - Press 'Keypad+-F13-' - On other - If you know of the key combos for other architectures, please let me know so I can add them to this section. regards, jmk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
sysrq.txt
Hello, I've found that the Sysrq Keys on Apple Computers are 'Keypad+-F13-command key', maybe it would be a good idea to include that in Documentation/sysrq.txt. The Patch: +++ sysrq.txt Tue Dec 12 20:46:38 2000 @@ -29,8 +29,6 @@ You send a BREAK, then within 5 seconds a command key. Sending BREAK twice is interpreted as a normal BREAK. -On Mac - Press 'Keypad+-F13-command key' - On other - If you know of the key combos for other architectures, please let me know so I can add them to this section. regards, jmk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
Alan Cox wrote: > > > AFAIK, this hasn't ever been true. I have never had to specifically > > > enable it at run time. > > > > I was suspicious of that in the old doc but thought I'd leave it in... > > Should have asked for feedback on it, but you caught it anyway, thanks! > > > > Here's a patch against the first that simply removes the lines. > > Its true in 2.2 At what point in 2.2 did it become true? I rarely used 2.2, I went from 2.1 to 2.3 and I don't recall having to ever enable it. Once it was compiled in it was on. -d -- There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
> > AFAIK, this hasn't ever been true. I have never had to specifically > > enable it at run time. > > I was suspicious of that in the old doc but thought I'd leave it in... > Should have asked for feedback on it, but you caught it anyway, thanks! > > Here's a patch against the first that simply removes the lines. Its true in 2.2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
AFAIK, this hasn't ever been true. I have never had to specifically enable it at run time. I was suspicious of that in the old doc but thought I'd leave it in... Should have asked for feedback on it, but you caught it anyway, thanks! Here's a patch against the first that simply removes the lines. Its true in 2.2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
Alan Cox wrote: AFAIK, this hasn't ever been true. I have never had to specifically enable it at run time. I was suspicious of that in the old doc but thought I'd leave it in... Should have asked for feedback on it, but you caught it anyway, thanks! Here's a patch against the first that simply removes the lines. Its true in 2.2 At what point in 2.2 did it become true? I rarely used 2.2, I went from 2.1 to 2.3 and I don't recall having to ever enable it. Once it was compiled in it was on. -d -- There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
Jonathan Earle wrote: > > On Sun, 28 Jan 2001 11:35:50 +, David Ford wrote: > > > AFAIK, this hasn't ever been true. I have never had to specifically > > > enable it at run time. > > > > I was suspicious of that in the old doc but thought I'd leave it in... > > Should have asked for feedback on it, but you caught it > > anyway, thanks! > > > > Here's a patch against the first that simply removes the lines. > > I'd suggest leaving those lines in; I've never had it enabled by default. > I've run Debian and Redhat systems, and both had to have the option > specifically turned ON via startup script - simply compiling it into a > kernel did not enable it. > > Jon I suggest compiling it in and booting with init=/bin/bash, mounting /proc and checking the value. It is enabled by default. A few distributions have a boot script that enables or disables it based on the sysconfig. -d -- There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: [PATCH] doc update/fixes for sysrq.txt
> On Sun, 28 Jan 2001 11:35:50 +, David Ford wrote: > > AFAIK, this hasn't ever been true. I have never had to specifically > > enable it at run time. > > I was suspicious of that in the old doc but thought I'd leave it in... > Should have asked for feedback on it, but you caught it > anyway, thanks! > > Here's a patch against the first that simply removes the lines. I'd suggest leaving those lines in; I've never had it enabled by default. I've run Debian and Redhat systems, and both had to have the option specifically turned ON via startup script - simply compiling it into a kernel did not enable it. Jon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: [PATCH] doc update/fixes for sysrq.txt
On Sun, 28 Jan 2001 11:35:50 +, David Ford wrote: AFAIK, this hasn't ever been true. I have never had to specifically enable it at run time. I was suspicious of that in the old doc but thought I'd leave it in... Should have asked for feedback on it, but you caught it anyway, thanks! Here's a patch against the first that simply removes the lines. I'd suggest leaving those lines in; I've never had it enabled by default. I've run Debian and Redhat systems, and both had to have the option specifically turned ON via startup script - simply compiling it into a kernel did not enable it. Jon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
Jonathan Earle wrote: On Sun, 28 Jan 2001 11:35:50 +, David Ford wrote: AFAIK, this hasn't ever been true. I have never had to specifically enable it at run time. I was suspicious of that in the old doc but thought I'd leave it in... Should have asked for feedback on it, but you caught it anyway, thanks! Here's a patch against the first that simply removes the lines. I'd suggest leaving those lines in; I've never had it enabled by default. I've run Debian and Redhat systems, and both had to have the option specifically turned ON via startup script - simply compiling it into a kernel did not enable it. Jon I suggest compiling it in and booting with init=/bin/bash, mounting /proc and checking the value. It is enabled by default. A few distributions have a boot script that enables or disables it based on the sysconfig. -d -- There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
On Sun, 28 Jan 2001 11:35:50 +, David Ford wrote: > AFAIK, this hasn't ever been true. I have never had to specifically > enable it at run time. I was suspicious of that in the old doc but thought I'd leave it in... Should have asked for feedback on it, but you caught it anyway, thanks! Here's a patch against the first that simply removes the lines. /jmd --- Documentation/sysrq.txt~Sun Jan 28 14:41:44 2001 +++ Documentation/sysrq.txt Sun Jan 28 14:41:52 2001 @@ -15,9 +15,6 @@ echo "0" > /proc/sys/kernel/sysrq -Note that previous versions disabled sysrq by default, and you were required -to specifically enable it at run-time. That is not the case any longer. - * How do I use the magic SysRq key? On x86 - You press the key combo 'ALT-SysRq-'. Note - Some - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
"Jeremy M. Dolan" wrote: > +Note that previous versions disabled sysrq by default, and you were required > +to specifically enable it at run-time. That is not the case any longer. AFAIK, this hasn't ever been true. I have never had to specifically enable it at run time. There are certain distributions which disabled it by default but this is distribution specific, not by way of the kernel. -d -- There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[PATCH] doc update/fixes for sysrq.txt
Updates Documentation/sysrq.txt for 2.4's behavior and cleans up a bit. /jmd --- linux-2.4.0-ac12/Documentation/sysrq.txtFri Jul 28 14:50:52 2000 +++ linux-2.4.0-ac12-jmd/Documentation/sysrq.txtSun Jan 28 04:15:59 2001 @@ -1,26 +1,27 @@ +Linux Magic System Request Key Hacks +Documentation for sysrq.c version 1.15 +Last update: $Date: 2001/01/28 10:15:59 $ - MAGIC SYSRQ KEY DOCUMENTATION v1.32 - -[Sat Apr 8 22:15:03 CEST 2000] - -* What is the magic SysRQ key? +* What is the magic SysRq key? ~~~ -It is a 'magical' key combo you can hit which kernel will respond to +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? +* How do I enable the magic SysRq key? ~~~ You need to say "yes" to 'Magic SysRq key (CONFIG_MAGIC_SYSRQ)' when -configuring the kernel. This option is only available in 2.1.x or later -kernels. Once you boot the new kernel, you need to enable it manually -using following command: +configuring the kernel. When running on a kernel with SysRq compiled in, it +may be DISABLED at run-time using following command: + +echo "0" > /proc/sys/kernel/sysrq -echo "1" > /proc/sys/kernel/sysrq +Note that previous versions disabled sysrq by default, and you were required +to specifically enable it at run-time. That is not the case any longer. -* How do I use the magic SysRQ key? +* How do I use the magic SysRq key? -On x86 - You press the key combo 'ALT-SysRQ-'. Note - Some - (older?) may not have a key labeled 'SysRQ'. The 'SysRQ' key is +On x86 - You press the key combo 'ALT-SysRq-'. Note - Some + keyboards may not have a key labeled 'SysRq'. The 'SysRq' key is also known as the 'Print Screen' key. On SPARC - You press 'ALT-STOP-', I believe. @@ -30,14 +31,14 @@ BREAK twice is interpreted as a normal BREAK. On other - If you know of the key combos for other architectures, please - let me know so I can add them to this section. + let me know so I can add them to this section. * What are the 'command' keys? ~~~ 'r' - Turns off keyboard raw mode and sets it to XLATE. -'k' - Secure Access Key (SAK) Kills all programs on the current virtual - console. NOTE: See important comments below in SAK section. +'k' - Secure Access Key (SAK) Kills all programs on the current virtual + console. NOTE: See important comments below in SAK section. 'b' - Will immediately reboot the system without syncing or unmounting your disks. @@ -67,8 +68,8 @@ 'l' - Send a SIGKILL to all processes, INCLUDING init. (Your system will be non-functional after this.) -'h'- Will display help ( actually any other key than those listed - above will display help. but 'h' is easy to remember :-) +'h' - Will display help ( actually any other key than those listed + above will display help. but 'h' is easy to remember :-) * Okay, so what can I use them for? @@ -80,8 +81,8 @@ and thus letting you make sure that the login prompt you see is actually the one from init, not some trojan program. IMPORTANT:In its true form it is not a true SAK like the one in :IMPORTANT -IMPORTATN:c2 compliant systems, and it should be mistook as such. :IMPORTANT - It seems other find it useful as (System Attention Key) which is +IMPORTANT:c2 compliant systems, and it should be mistook as such. :IMPORTANT + It seems other 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.) @@ -90,7 +91,7 @@ 'S'ync 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. Note -that the sync hasn't taken place until you see the "OK" and "Done" appear +that the sync hasn't taken place until you see the "OK" and "Done" appear on the screen. (If the kernel is really in strife, you may not ever get the OK or Done message...) @@ -108,30 +109,31 @@ are unable to kill any other way, especially if it's spawning other processes. -* Sometimes SysRQ seems to get 'stuck' after using it, what can I do? +* Sometimes SysRq seems to get 'stuck' after using it, what can I do? ~~ That happens to me, also. I've found that tapping shift, alt, and control on both sides of the keyboard, and hitting an invalid sysrq seque
[PATCH] doc update/fixes for sysrq.txt
Updates Documentation/sysrq.txt for 2.4's behavior and cleans up a bit. /jmd --- linux-2.4.0-ac12/Documentation/sysrq.txtFri Jul 28 14:50:52 2000 +++ linux-2.4.0-ac12-jmd/Documentation/sysrq.txtSun Jan 28 04:15:59 2001 @@ -1,26 +1,27 @@ +Linux Magic System Request Key Hacks +Documentation for sysrq.c version 1.15 +Last update: $Date: 2001/01/28 10:15:59 $ - MAGIC SYSRQ KEY DOCUMENTATION v1.32 - -[Sat Apr 8 22:15:03 CEST 2000] - -* What is the magic SysRQ key? +* What is the magic SysRq key? ~~~ -It is a 'magical' key combo you can hit which kernel will respond to +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? +* How do I enable the magic SysRq key? ~~~ You need to say "yes" to 'Magic SysRq key (CONFIG_MAGIC_SYSRQ)' when -configuring the kernel. This option is only available in 2.1.x or later -kernels. Once you boot the new kernel, you need to enable it manually -using following command: +configuring the kernel. When running on a kernel with SysRq compiled in, it +may be DISABLED at run-time using following command: + +echo "0" /proc/sys/kernel/sysrq -echo "1" /proc/sys/kernel/sysrq +Note that previous versions disabled sysrq by default, and you were required +to specifically enable it at run-time. That is not the case any longer. -* How do I use the magic SysRQ key? +* How do I use the magic SysRq key? -On x86 - You press the key combo 'ALT-SysRQ-command key'. Note - Some - (older?) may not have a key labeled 'SysRQ'. The 'SysRQ' key is +On x86 - You press the key combo 'ALT-SysRq-command key'. Note - Some + keyboards may not have a key labeled 'SysRq'. The 'SysRq' key is also known as the 'Print Screen' key. On SPARC - You press 'ALT-STOP-command key', I believe. @@ -30,14 +31,14 @@ BREAK twice is interpreted as a normal BREAK. On other - If you know of the key combos for other architectures, please - let me know so I can add them to this section. + let me know so I can add them to this section. * What are the 'command' keys? ~~~ 'r' - Turns off keyboard raw mode and sets it to XLATE. -'k' - Secure Access Key (SAK) Kills all programs on the current virtual - console. NOTE: See important comments below in SAK section. +'k' - Secure Access Key (SAK) Kills all programs on the current virtual + console. NOTE: See important comments below in SAK section. 'b' - Will immediately reboot the system without syncing or unmounting your disks. @@ -67,8 +68,8 @@ 'l' - Send a SIGKILL to all processes, INCLUDING init. (Your system will be non-functional after this.) -'h'- Will display help ( actually any other key than those listed - above will display help. but 'h' is easy to remember :-) +'h' - Will display help ( actually any other key than those listed + above will display help. but 'h' is easy to remember :-) * Okay, so what can I use them for? @@ -80,8 +81,8 @@ and thus letting you make sure that the login prompt you see is actually the one from init, not some trojan program. IMPORTANT:In its true form it is not a true SAK like the one in :IMPORTANT -IMPORTATN:c2 compliant systems, and it should be mistook as such. :IMPORTANT - It seems other find it useful as (System Attention Key) which is +IMPORTANT:c2 compliant systems, and it should be mistook as such. :IMPORTANT + It seems other 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.) @@ -90,7 +91,7 @@ 'S'ync 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. Note -that the sync hasn't taken place until you see the "OK" and "Done" appear +that the sync hasn't taken place until you see the "OK" and "Done" appear on the screen. (If the kernel is really in strife, you may not ever get the OK or Done message...) @@ -108,30 +109,31 @@ are unable to kill any other way, especially if it's spawning other processes. -* Sometimes SysRQ seems to get 'stuck' after using it, what can I do? +* Sometimes SysRq seems to get 'stuck' after using it, what can I do? ~~ That happens to me, also. I've found that tapping shift, alt, and control on both sides of the keyboard,
Re: [PATCH] doc update/fixes for sysrq.txt
"Jeremy M. Dolan" wrote: +Note that previous versions disabled sysrq by default, and you were required +to specifically enable it at run-time. That is not the case any longer. AFAIK, this hasn't ever been true. I have never had to specifically enable it at run time. There are certain distributions which disabled it by default but this is distribution specific, not by way of the kernel. -d -- There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] doc update/fixes for sysrq.txt
On Sun, 28 Jan 2001 11:35:50 +, David Ford wrote: AFAIK, this hasn't ever been true. I have never had to specifically enable it at run time. I was suspicious of that in the old doc but thought I'd leave it in... Should have asked for feedback on it, but you caught it anyway, thanks! Here's a patch against the first that simply removes the lines. /jmd --- Documentation/sysrq.txt~Sun Jan 28 14:41:44 2001 +++ Documentation/sysrq.txt Sun Jan 28 14:41:52 2001 @@ -15,9 +15,6 @@ echo "0" /proc/sys/kernel/sysrq -Note that previous versions disabled sysrq by default, and you were required -to specifically enable it at run-time. That is not the case any longer. - * How do I use the magic SysRq key? On x86 - You press the key combo 'ALT-SysRq-command key'. Note - Some - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[PATCH] Documentation/sysrq.txt: How to scroll back on console.
Hi, This might be useful to add to Documentation/sysrq.txt. Regards, Nick --- sysrq.txt.orig Wed Nov 29 17:13:18 2000 +++ sysrq.txt Wed Nov 29 17:23:33 2000 @@ -21,7 +21,10 @@ On x86 - You press the key combo 'ALT-SysRQ-'. Note - Some (older?) may not have a key labeled 'SysRQ'. The 'SysRQ' key is - also known as the 'Print Screen' key. + also known as the 'Print Screen' key. To scroll back (as + you often need to do to view all of the output of some + SysRQ commands), simply press shift-pageup. (I only know + this to work on x86. It might work elsewhere as well.) On SPARC - You press 'ALT-STOP-', I believe. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[PATCH] Documentation/sysrq.txt: How to scroll back on console.
Hi, This might be useful to add to Documentation/sysrq.txt. Regards, Nick --- sysrq.txt.orig Wed Nov 29 17:13:18 2000 +++ sysrq.txt Wed Nov 29 17:23:33 2000 @@ -21,7 +21,10 @@ On x86 - You press the key combo 'ALT-SysRQ-command key'. Note - Some (older?) may not have a key labeled 'SysRQ'. The 'SysRQ' key is - also known as the 'Print Screen' key. + also known as the 'Print Screen' key. To scroll back (as + you often need to do to view all of the output of some + SysRQ commands), simply press shift-pageup. (I only know + this to work on x86. It might work elsewhere as well.) On SPARC - You press 'ALT-STOP-command key', I believe. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
