From: Martin Pool <mbp@samba.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Dump driver module
Date: Wed, 14 May 2003 02:14:21 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705770@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705751@msgid-missing>
On 13 May 2003, Bruno Vidal <bruno_vidal@hp.com> wrote:
> Hi
> Sorry, but LKCD is really not usefull because it use the buffer
> to write on the device. So it just hang in case of data page fault for
> example (because interuption are masked), LKCD is also not working in case
> of buffer corruption, disk driver pb, etc.... so LKCD is not usable in
> lot's of case (and it happen really often to have data page fault).
There is also the netconsole/netdump system. This is supposed to rely
on only a very minimal network driver. As you say, writing to disk
when kernel memory may have been corrupted is a risky business, not
only because you might hang but also because you might write over the
wrong region. netdump doesn't do any disk IO for that reason. I seem
to recall that Linus liked this property.
Of course it's only useful if the machine is on a network where there
is another machine to catch the data, but I would expect that to be
the case for most ia64 machines.
http://www.redhat.com/support/wpapers/redhat/netdump/
--
Martin
next prev parent reply other threads:[~2003-05-14 2:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 7:02 [Linux-ia64] Dump driver module Bruno Vidal
2003-05-13 7:18 ` Stephane Eranian
2003-05-13 7:25 ` David Mosberger
2003-05-13 7:38 ` Bruno Vidal
2003-05-13 8:08 ` David Mosberger
2003-05-13 13:29 ` Howell, David P
2003-05-13 14:39 ` Bruno Vidal
2003-05-14 2:13 ` Keith Owens
2003-05-14 2:14 ` Martin Pool [this message]
2003-05-14 2:21 ` David Mosberger
2003-05-14 2:32 ` Martin Pool
2003-05-14 2:40 ` David Mosberger
2003-05-14 6:33 ` Grant Grundler
2003-05-14 6:50 ` Bruno Vidal
2003-05-14 13:29 ` Matthew Wilcox
2003-05-14 15:41 ` Grant Grundler
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=marc-linux-ia64-105590723705770@msgid-missing \
--to=mbp@samba.org \
--cc=linux-ia64@vger.kernel.org \
/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