![]() | |||||||||||||
Messages in this thread |
On Fri, 6 Jan 2006 08:06:12 +0100 (MET) 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. > Of course, this probably requires that the unlocking must not be done > with help of the standard page mappings. This is what kexec + kdump is. --- ~Randy - 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/ | ||||||||||||
| Last update: 2006-01-06 07:49 [from the cache] ©2003-2008 | |||||||||||||