public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Vidal <bruno_vidal@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Dump driver module
Date: Tue, 13 May 2003 14:39:30 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705758@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705751@msgid-missing>

	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).

Cheers.

Howell, David P wrote:
> Have you looked at the LKCD project? It supports ia64 and does about
> what you are doing on the dump side, and has dump analysis tools.
> 
> If you've already considered this just delete this.
> 
> Thanks,
> Dave Howell
> 
> 
> These are my opinions and not official opinions of Intel Corp.
> 
> David Howell
> Intel Corporation
> Telco Server Development
> Server Products Division
> Voice: (803) 461-6112  Fax: (803) 461-6292
> 
> Intel Corporation
> Columbia Design Center, CBA-2
> 250 Berryhill Road, Suite 100
> Columbia, SC 29210
> 
> david.p.howell@intel.com
> 
> 
> -----Original Message-----
> From: Bruno Vidal [mailto:bruno_vidal@hp.com] 
> Sent: Tuesday, May 13, 2003 3:03 AM
> To: linux-ia64@linuxia64.org
> Subject: [Linux-ia64] Dump driver module
> 
> 	Hi all.
> I've already wrote a dump modules driver for linux-parisc.
> This module goal is to create a memory image on a swap area, and
> at reboot time to save it to disk with all kernel modules, in
> order to analyze it after by "support" people with tools like
> gdb/p4. The problem while dumping is that the dump modules
> cannot trust anymore the system, so dumping means: no interruption,
> no disk driver, no buffer, nothing. The solution is to use low level
> call. For parisc I use the IODC calls, for ia64 I think I'll
> use the EFI calls. My questions:
> -do you think it is a "good" and realistic solution.
> -because I think "yes", does exist somewhere an example of
> reading/writing with EFI call on disk using BLOCK IO. I've already
> looked in elilo, but it seems that it use FS access.
> 
> 	Thanks.
> 


-- 
	Vidal Bruno, (770-4271)
         SSD-HA Team, HP-UX & LINUX Support
	bruno_vidal@hp.com



  parent reply	other threads:[~2003-05-13 14:39 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 [this message]
2003-05-14  2:13 ` Keith Owens
2003-05-14  2:14 ` Martin Pool
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-105590723705758@msgid-missing \
    --to=bruno_vidal@hp.com \
    --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