lkcd
[Top] [All Lists]

Re: lcrash with kdb

To: thomas graichen <tgr@xxxxxxxxxxx>
Subject: Re: lcrash with kdb
From: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>
Date: Tue, 24 Apr 2001 09:54:28 -0700
Cc: lkcd@xxxxxxxxxxx
Organization: Alacritech, Inc.
References: <3ADD5754.87D47267@xxxxxxxxx> <news2mail-20010421114441.6CF8D8B9.NOFFLE@xxxxxxxxxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
thomas graichen wrote:
> 
> Vivek Agarwal <agarwal.vivek@xxxxxxxxx> wrote:
> > This is a multi-part message in MIME format.
> > --------------94954E65DCD7152C87439C15
> > Content-Type: text/plain; charset=us-ascii
> > Content-Transfer-Encoding: 7bit
> 
> > Hi !
> 
> > Is it possible to have a kernel with both "kdb" and "lcrash".
> 
> > I have Linux 2.4.0 installed on my system with "kdb". But when I try to
> > patch
> > the existing kernel (having kdb) with the "lcrash" patch, If fails at
> > some places.
> > Please guide if this is possible or not.
> 
> i run a kernel with both of them in (to be correct it's the SGI XFS
> tree plus lkcd patched in) and it seems to work so far (but i never
> had the chance to see it on a real crash) - the conflicts are pretty
> easy to resolv manually (mail me if you have problems) ... the im-
> portant thing is - you should always only have one of the two enabled
> which will act in case of a panic (i usually have kdb off by default
> and crash dumps on ... and they worked)

Normally, KDB will be invoked first, and then when you exit KDB,
the system should panic.  They were intended (at least they were
two years ago) to be daisy chained, one after the other.  The
only issue is making sure KDB leaves the system in a decent state
so a system crash can occur.

There should be no issue in ordering, unless Keith changed something
in how KDB is invoked.

--Matt

> hope that helps
> 
> t
> 
> --
> thomas graichen <tgr@xxxxxxxxxxx> ... perfection is reached, not
> when there is no longer anything to add, but when there is no
> longer anything to take away. --- antoine de saint-exupery

<Prev in Thread] Current Thread [Next in Thread>