From: Gerrit.Huizenga@us.ibm.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Memory clearing at reboot
Date: Wed, 23 Aug 2000 23:16:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205386@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205378@msgid-missing>
> > Having an ability to dump system memory to disk from an application
> > other than the kernel that just crashed is a major serviceability
>
> Patrick O'Rourke said...
>
> Do you mean the equivalent of 'dd if=/dev/mem of=<some file>? The problem
> with dumping memory from an application is that the kernel is still active,
Not at all what I'm referring to - I mean instead it should be possible
for, say, an EFI app to read system memory after the kernel has
panic'd/shut down, and then copy that image to a disk for later kernel
or hardware fault isolation. In larger sites and larger systems (where
Itanium will more likely fit in its first couple of years) customers
expect that the machine will be back in operation ASAP and the system
can not afford to be down while people run diagnostics or try things to
see if they can figure out what caused a kernel to crash.
On smaller systems, yes, debugging is also important; however, those
systems can be typically co-opted for HW or SW debugging. The users
are more tolerant of someone saying "Oh, try that again" or "Here's
a debug kernel, see what happens". A large database customer running
their business on a 16 processor machine is much less tolerant of
such impact to their systems. Hence, being able to take a snapshot
of the machine state at the time of failure and sending that information
elsewhere for out of band debugging simplifies everyone's life.
Most operating systems tend to try to write an image to disk after the
system has failed. As a result, a system with already corrupt memory
is trying to set up DMA or programmed IO of all of memory to some
disk subsystem, which tends to be a recipe for failure. It's like
giving an accident victim the responsibility for self-diagnosis.
As far as which memory to dump, usually only kernel pages need to
be dumped; however, that takes a slightly more sophisticated dump
program and crash dump analyzer. Not impossible, but usually not
a first generation choice (we've done exactly that with Sequent NUMA
systems several years back).
gerrit
prev parent reply other threads:[~2000-08-23 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-22 18:49 [Linux-ia64] Memory clearing at reboot John Baboval
2000-08-23 0:37 ` Saxena, Sunil
2000-08-23 1:01 ` Gerrit.Huizenga
2000-08-23 23:16 ` Gerrit.Huizenga [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=marc-linux-ia64-105590678205386@msgid-missing \
--to=gerrit.huizenga@us.ibm.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