From: Keith Owens <kaos@ocs.com.au>
To: tegeran@home.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possibly unfreezable system?
Date: Sun, 05 Aug 2001 11:56:38 +1000 [thread overview]
Message-ID: <2314.996976598@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 04 Aug 2001 14:52:14 MST." <01080414521403.02694@c779218-a>
On Sat, 4 Aug 2001 14:52:14 -0700,
Nicholas Knight <tegeran@home.com> wrote:
>I've lately seen many complaints regarding the inability to even access a
>system that something (such as kswapd) is going crazy on.
>The solution, to me, seems simple, have the kernel reserve some extra RAM
>at boot (a few megs), and dictate that it get at least X amount of
>processor time, consistantly, to allow for the following:
>An alt-sysrq key that switches to a certain virtual console, kills
>whatever might already be running there, and allow a person to log in in
>order to kill whatever is causing the system to freeze, run out of
>memory, etc. The program(s) running here would run in that extra RAM the
>kernel reserved at boot.
It already exists and is called kdb.
ftp://oss.sgi.com/projects/kdb/download/ix86
prev parent reply other threads:[~2001-08-05 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-04 21:52 Possibly unfreezable system? Nicholas Knight
2001-08-05 1:56 ` Keith Owens [this message]
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=2314.996976598@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tegeran@home.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox