Messages in this thread | | | Date | Fri, 6 Jan 2006 03:58:31 -0500 | From | Dave Jones <> | Subject | Re: oops pauser. |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |