All of lore.kernel.org
 help / color / mirror / Atom feed
From: youling 257 <youling257@gmail.com>
To: Lukas Odzioba <lukas.odzioba@gmail.com>
Cc: keescook@chromium.org, kernel-hardening@lists.openwall.com,
	 munisekharrms@gmail.com
Subject: Re: How to get the crash dump if system hangs?
Date: Mon, 21 Oct 2019 18:22:02 +0800	[thread overview]
Message-ID: <CAOzgRdbFc_WJDaOg5vdq5Y=nL+vyApCDCGFb-AUo6f=GRSDQWQ@mail.gmail.com> (raw)
In-Reply-To: <CABob6iq_N8He+ORZuRVqdDhBCuymSwVyRHCsW8GAzXcM8+_tuA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 707 bytes --]

When add cmdline memmap=1M!2047M, the iomem will be 7ef00001-7fefffff : RAM
buffer 7ff00000-7fffffff : Persistent Memory (legacy) 7ff00000-7ff00fff :
MSFT0101:00,
so ramoops.mem_address=0x7ff00000.

Lukas Odzioba <lukas.odzioba@gmail.com> 于 2019年10月21日周一 下午4:39写道：

> youling257 <youling257@gmail.com> wrote:
> >
> > I don't know my ramoops.mem_address, please help me.
> >
> > what is ramoops.mem_address?
>
> It is a Linux kernel parameter, see documentation below:
> https://www.kernel.org/doc/Documentation/admin-guide/ramoops.rst
>
> It requires memory which can hold data between reboots, so i'm not
> sure how it will suit your case.
>
> Thanks,
> Lukas
>

[-- Attachment #2: Type: text/html, Size: 1282 bytes --]

  reply	other threads:[~2019-10-21 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20 19:01 How to get the crash dump if system hangs? youling257
2019-10-21  8:39 ` Lukas Odzioba
2019-10-21 10:22   ` youling 257 [this message]
2019-11-02  5:42     ` youling 257
  -- strict thread matches above, loose matches on Subject: below --
2019-10-20 19:31 youling257
2019-09-25 20:17 Muni Sekhar
2019-09-30 23:51 ` Kees Cook
2019-10-03 16:48   ` Muni Sekhar
2019-10-03 21:36     ` Kees Cook
2019-10-10 15:49       ` Muni Sekhar
2019-10-10 16:56         ` Kees Cook
2019-10-10 17:15           ` Muni Sekhar
2019-10-10 18:31             ` Kees Cook
2019-10-11 14:03               ` Muni Sekhar
2019-10-25  2:10                 ` Muni Sekhar
2019-10-28 19:22                   ` Kees Cook

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='CAOzgRdbFc_WJDaOg5vdq5Y=nL+vyApCDCGFb-AUo6f=GRSDQWQ@mail.gmail.com' \
    --to=youling257@gmail.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=lukas.odzioba@gmail.com \
    --cc=munisekharrms@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.