From: John Richard Moser <nigelenki@comcast.net>
To: Jason Baron <jbaron@redhat.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix altsysrq deadlock
Date: Tue, 26 Oct 2004 13:43:32 -0400 [thread overview]
Message-ID: <417E8CC4.4010706@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0410261325120.12088-100000@dhcp83-105.boston.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jason Baron wrote:
| hi,
|
HI! ^_^
[...]
| An
| altsyrq that produces no output might seem troublesome, but it is
| primarily used as a debugging tool, so trying it again seems reasonable.
Actually, I use sysrq as if it's just another feature. It should (I
think it does. . . not sure) only work on the console directly, for
security reasons; but it's great when things like X misbehave, or when
I've damaged something and the system doesn't want to shut down. AS-E
AS-I AS-U AS-S AS-O. :) I actually tried making an N sysrq, for
"semi-Normal shutdown." It would send TERM, wait 5S, send KILL, wait
5S, unmount, sync, reboot.
Just thought it might be interesting to point out that magic-sysrq can
be a helpful feature for someone not hacking the kernel.
[...]
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBfozEhDd4aOud5P8RAo/xAJ9sumPFUpGkwIf4ipR2+6g0bmwUYQCdGQ+U
SPvEFbVzUCx+8zdNQqnT8F8=
=OQrV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-10-26 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 17:27 [PATCH] fix altsysrq deadlock Jason Baron
2004-10-26 17:43 ` John Richard Moser [this message]
2004-10-26 18:22 ` Jason Baron
2004-10-26 18:33 ` John Richard Moser
[not found] <Pine.LNX.4.44.0410261311590.12088-100000@dhcp83-105.boston.redhat.com>
2004-10-27 2:40 ` Andrew Morton
2004-10-27 19:05 ` Jason Baron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=417E8CC4.4010706@comcast.net \
--to=nigelenki@comcast.net \
--cc=akpm@osdl.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.