public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
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 01:01:52 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205384@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
feature for larger systems.  I don't see it as being as useful on
a one or two proc system, but post-mortem analysis is typically
considered a major feature for people running departmental or
large servers (e.g. Lion sized).

Being only able to dump memory from inside of a dying kernel (a la
NT) seems like a bad idea on a big box.

Of course, if this is BIOS specific, people building larger machines
(e.g. 4 proc or larger) can hopefully avoid this problem (e.g. here
at IBM ;-).  It would be more useful though if this were a feature
of the standard Lion BIOS as well.

gerrit

> Hi John,
> 
> Big Sur initializes it's memory only on power on; it does not do so on a
> soft reboot.  The behavior you are seeing should continue on all build of
> our BIOS.
> 
> I am waiting for the answer on the Lion machine and do not know if Lion team
> can also enable this functionality.  I will respond again once I have the
> answer.  (By the way, my gut feelings says that they will not be able to
> enable this functionality.)
> 
> Thanks
> Sunil 
> 
> -----Original Message-----
> From: John Baboval [mailto:baboval@mclinux.com]
> Sent: Tuesday, August 22, 2000 11:50 AM
> To: linux-ia64@linuxia64.org
> Subject: [Linux-ia64] Memory clearing at reboot
> 
> 
> I have a small test program that I run at the EFI shell prompt to set an
> area of memory and then perform a warm reboot. After the reboot our BigSur
> still contains the values written, but the Lion is cleared to zero. (We
> check the contents with the mem command, and the ResetSystem() is called
> with the EfiResetWarm parameter.)
> 
> Does anyone know if there is a way to cause the Lion *not* to clear memory?
> Also, our Lion has newer firmware then the BigSur. Perhaps the newer
> firmware causes the reset? 
> 
> If someone out there has a BigSur with the latest firmware/CPU rev., could
> you run my program and tell me if your machine resets it's memory? The
> source code is attached, and you can build it with gnu-efi-0.9.
> 
> Basically, you run the program and write down the address, and then when the
> machine comes back up type 'mem <Address>' and see if the memory is zero or
> not.
> 
> Not reseting memory makes taking kernel core dumps with our in-memory core
> dump patches MUCH easier! Thanks for any help,
> 
> -- 
> --John
> jbaboval@missioncriticallinux.com
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 


  parent reply	other threads:[~2000-08-23  1:01 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 [this message]
2000-08-23 23:16 ` Gerrit.Huizenga

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-105590678205384@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