[lkml]   [2002]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: writing OOPS/panic info to nvram?
On Wed, 04 Sep 2002 20:02:40 +0530, Alan Cox wrote:

> On Wed, 2002-09-04 at 15:08, J.A. Magallon wrote:
>> Instead of swap, let user specify a partition to raw dump there. If a
>> user wants crash dumps, he has to leave some small disk space free and
>> give an option like "dump=/dev/hda7".
> With what will you write it - not the linux block layer thats for sure.
> Ingo has patches for doing network dumps which are kind of neat
> -

LKCD for 2.5 (WIP) has a dump driver interface through which different
target types can be plugged in. For example Ingo's polled network dump
code been integrated as one such dump driver target (generic type),
block layer based i/o is available as another target (for those
who chose to use it for their raw partition).Down the line specific
dump drivers suited for the hardware concerned, e.g Rusty's polled
IDE driver, could be plugged in as dump target too, as could NECs
work on converting dump block i/o to polled mode.

Conceivably, one may perhaps have alternate targets available on the
same system and failover to the suitable one based on the situation.
(If the network interface code is the one in trouble, try to
dump to the dedicated raw disk or vice versa).

And then, a little later there could be the option of memory save
option abstracted as another driver target, to be followed
by a soft-reboot (w/o clearing memory) for performing actual dump i/o
to persistent storage on architectures where this option works out.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.113 / U:5.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site