From: Arun Dharankar <ADharankar@ATTBI.Com>
To: Piet Delaney <piet@www.piet.net>
Cc: piet <piet@www.piet.net>,
"Matt D. Robinson" <yakker@alacritech.com>,
linux-kernel@vger.kernel.org, Dave Anderson <anderson@redhat.com>
Subject: Re: Linux kernel crash dumps (LKCD) and PowerPC ports.
Date: Wed, 9 Apr 2003 08:26:36 -0400 [thread overview]
Message-ID: <200304090826.36304.ADharankar@ATTBI.Com> (raw)
In-Reply-To: <1049875702.22212.6634.camel@www.piet.net>
Piet, thanks for the reply!
Some of the points that I found attractive (among other points):
- Overall a smaller time to reboot and save the dump, and bring the
system back to working state.
- Does not require local disk to save the dump on the way down during
a panic - works on a diskless system.
- No need for a dump/swap device.
Looking at the MCLX site, the last patch is on 2.4.17 only. Also, the
PowerPC port is a bit broken. Is anyone maintaining this part of the
MCLX scheme, and is available else where?
Best regards,
-Arun.
> > Looking at those sites, it appears that the development at
> > "http://lists.insecure.org/lists/linux-kernel/2003/Feb/0987.html."
> > which I had pointed is based on the SGI's dump scheme. Same
> > for the one you pointed to.
> >
> > The other scheme I poinited to (from Mission Critical Linux/MCLX)
> > seems to have some strong points too. Any pointers to discussions
> > about why the LKCD work seems to more active than the
> > MCLX one?
>
> I don't think there has been such a discussion. The Mission Critical
> hackers were hired by RedHat and Dave Anderson continues to work on
> crash and making it available at:
>
> ftp://people.redhat.com/anderson
>
> He's had about a release per month. I thought MCLX crash has some
> strong points also. After I enhanced LKCD to support the ia64 I
> fixed MCLX crash so it could read the new LKCD crash dumps which
> are no longer monotonically increasing in memory. I did this to
> support NUMA systems which can have more memory than swap space.
> This way the most important memory can be saved first.
>
> If you read the lkcd-devel mailing list you can read our discussion
> on maintaining MLCX crash on the lkcd cvs tree.
>
>
> "And imnsho, debugging the kernel on a source
> level is the way to do it."
> Linus
>
> -piet
>
> > Best regards,
> > -Arun.
> >
> > On Tuesday 08 April 2003 07:14 pm, Matt D. Robinson wrote:
> > > Please look at the lkcd-devel mailing archives. There is
> > > at least one group working on a PPC port of LKCD
> > >
> > > http://sourceforge.net/mail/?group_id=2726
> > >
> > > --Matt
prev parent reply other threads:[~2003-04-09 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 20:47 Linux kernel crash dumps (LKCD) and PowerPC ports Arun Dharankar
2003-04-08 23:14 ` Matt D. Robinson
2003-04-09 3:49 ` Arun Dharankar
2003-04-09 8:08 ` Piet Delaney
2003-04-09 12:26 ` Arun Dharankar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200304090826.36304.ADharankar@ATTBI.Com \
--to=adharankar@attbi.com \
--cc=anderson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piet@www.piet.net \
--cc=yakker@alacritech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.