From: Vivek Goyal <vgoyal@in.ibm.com>
To: noboru.obata.ar@hitachi.com
Cc: fastboot@osdl.org, linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [Fastboot] [KDUMP] pending interrupts problem
Date: Tue, 8 Nov 2005 13:47:58 +0530 [thread overview]
Message-ID: <20051108081758.GA2231@in.ibm.com> (raw)
In-Reply-To: <m1d5lk8uue.fsf@ebiederm.dsl.xmission.com>
On Tue, Nov 01, 2005 at 04:34:49AM -0700, Eric W. Biederman wrote:
> OBATA Noboru <noboru.obata.ar@hitachi.com> writes:
>
[..]
> > I think we need more test cases, especially the cases that focus
> > on "status" of hardware, to make kdump more reliable. Kdump
> > should recover from all possible status of supported hardware.
>
> Given that part of all possible status is broken hardware,
> that isn't necessarily possible. Still attempting to recover
> from all possible status is a sound plan.
>
> > Is anyone working on developing such test cases for kdump?
>
> Not to my knowledge. The big push until just lately has simply
> been to get the core working. Vivek Goyal would be the most
> likely suspect. But feel free to work on pathological scenarios.
>
Currently I am trying to focus on fixing the already reported issues and
have not looked into special scenarios where kdump might fail. But your
effort in this direction is very much appreciated. We need to dig up such
corner cases to make kdump more reliable and robust.
Thanks
Vivek
next prev parent reply other threads:[~2005-11-08 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 7:50 OBATA Noboru
2005-10-27 15:18 ` [Fastboot] " Eric W. Biederman
2005-11-01 9:13 ` OBATA Noboru
2005-11-01 11:34 ` Eric W. Biederman
2005-11-08 8:17 ` Vivek Goyal [this message]
2005-10-27 15:40 ` [PATCH] " Eric W. Biederman
2005-10-27 16:06 ` Alex Lyashkov
2005-10-28 0:08 ` [Fastboot] " Eric W. Biederman
2005-11-01 9:12 ` OBATA Noboru
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=20051108081758.GA2231@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noboru.obata.ar@hitachi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome