Hi,
A possibly useful feature would be for the Linux KDB to support a
command to initiate a system dump (i haven't looked at the latest
version though so please excuse if this is already supported). A lot of
times when a system appears hung doing an insmod would just not be
feasible and rather than tweak the kernel to panic and thereby force the
system to dump it may just be better for KDB itself to support say a
"sysdump" command that would take a dump of the system image before
reboot.
Also how about having a "live dump" feature for Linux ?? If testing lkcd
is all that you want to do then why go all over panic'ing and dumping
the system why not just do a live dump of the system to the dump device
and use the saved dump.
Govindan
Tom Morano wrote:
>
> You could of course do that. The code included in the FAQ is an
> example of how you COULD force a dump. I know from my own experience,
> that a module approach may not always work. I'm currently building
> ia64 kernels on one system and then booting them on another (without
> module support configured). Thanks for this alternative suggestion
> though.
>
> Tom
>
> Andi Kleen wrote:
> >
> > On Fri, Nov 03, 2000 at 02:08:11PM -0800, Tom Morano wrote:
> > > It contains an example of how you to modify the sys_setpriority()
> > > function so that, it causes either a panic or a SEGV trap. There is
> > > also a sample program that calls setpriority() to initiate the dump.
> >
> > That sounds rather complicated. Why don't you just load a small kernel
> > module for it ?
> >
> > #include <linux/module.h>
> > int init_module(void)
> > {
> > panic("Dump");
> > }
> >
> > gcc -O2 -DMODULE -c module.c
> > insmod module.o
> >
> > -Andi
|