From: Dave Jones <davej@redhat.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: oops pauser.
Date: Fri, 6 Jan 2006 03:58:31 -0500 [thread overview]
Message-ID: <20060106085831.GC4595@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0601060804100.22809@yvahk01.tjqt.qr>
On Fri, Jan 06, 2006 at 08:06:12AM +0100, Jan Engelhardt wrote:
> >> After an oops, we can't really rely on anything. What if the
> >> oops came from the console layer, or a framebuffer driver?
>
> How about this?:
>
> Put an "emergency kernel" into a memory location that is being protected in
> some way (i.e. writing there even from kernel space generates an oops).
> Upon oops, it gets unlocked and we do some sort of kexec() to it.
You just reinvented 'kdump' :)
There's been ongoing work in this area for a while.
Dave
next prev parent reply other threads:[~2006-01-06 8:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5rvok-5Sr-1@gated-at.bofh.it>
[not found] ` <5ryvR-2aN-5@gated-at.bofh.it>
[not found] ` <5rAHn-5kc-9@gated-at.bofh.it>
2006-01-06 5:52 ` oops pauser Robert Hancock
2006-01-06 7:06 ` Jan Engelhardt
2006-01-06 7:47 ` Randy.Dunlap
2006-01-06 8:58 ` Dave Jones [this message]
[not found] ` <5tagc-6AZ-25@gated-at.bofh.it>
2006-01-15 16:48 ` Console debugging wishlist was: " Bodo Eggert
2006-01-15 17:13 ` Andi Kleen
2006-01-15 20:51 ` Jan Engelhardt
2006-01-05 4:52 Dave Jones
2006-01-05 8:15 ` Jan Engelhardt
2006-01-05 10:33 ` Dave Jones
2006-01-05 11:05 ` Jan Engelhardt
2006-01-05 12:05 ` Keith Owens
2006-01-05 15:17 ` Jesper Juhl
2006-01-05 13:46 ` Kurt Wall
2006-01-06 1:24 ` David Lang
2006-01-06 1:41 ` Josef Sipek
2006-01-08 13:38 ` Ville Herva
2006-01-08 13:53 ` Randy.Dunlap
2006-01-08 19:35 ` Jan Engelhardt
2006-01-09 1:43 ` Randy.Dunlap
2006-01-08 19:40 ` Grant Coady
2006-01-09 1:45 ` Randy.Dunlap
2006-01-09 16:15 ` Jan Engelhardt
2006-01-09 16:25 ` Ville Herva
2006-01-09 16:39 ` Randy.Dunlap
2006-01-05 13:37 ` Alan Cox
2006-01-05 20:52 ` Dave Jones
2006-01-06 13:31 ` Alan Cox
2006-01-06 20:33 ` Dave Jones
2006-01-06 15:22 ` Pavel Machek
2006-01-06 19:06 ` Jan Engelhardt
2006-01-06 22:34 ` Pavel Machek
2006-01-06 22:48 ` Dave Jones
2006-01-05 13:58 ` Avishay Traeger
2006-01-05 20:54 ` Dave Jones
2006-01-06 0:19 ` Josef Sipek
2006-01-06 1:12 ` Bernd Eckenfels
2006-01-06 1:35 ` Josef Sipek
2006-01-06 2:21 ` Bernd Eckenfels
2006-01-05 14:39 ` Kyle McMartin
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=20060106085831.GC4595@redhat.com \
--to=davej@redhat.com \
--cc=hancockr@shaw.ca \
--cc=jengelh@linux01.gwdg.de \
--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.