Kernel-hardening archive on lore.kernel.org
 help / color / Atom feed
From: Muni Sekhar <munisekharrms@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: How to get the crash dump if system hangs?
Date: Fri, 11 Oct 2019 19:33:38 +0530
Message-ID: <CAHhAz+hw251beDeaWRFV7oShngSQ_KAACXAzb45EZRBdZ3kbSg@mail.gmail.com> (raw)
In-Reply-To: <201910101106.9ACB5DB@keescook>

On Fri, Oct 11, 2019 at 12:01 AM Kees Cook <keescook@chromium.org> wrote:
>
> On Thu, Oct 10, 2019 at 10:45:21PM +0530, Muni Sekhar wrote:
> > I'm using Ubuntu distro, ran "reboot" command but after reboot
> > console-ramoops-0 is not present in /sys/fs/pstore
>
> Hmpf. Well, then, I guess your boot firmware is pretty aggressive about
> wiping RAM across boots. :(
>
> There was a patch set to store to disk, but I haven't seen a recent
> version of it, if you want to go that route[1].
>
> -Kees
>
> [1] https://lore.kernel.org/lkml/1551922630-27548-1-git-send-email-liaoweixiong@allwinnertech.com/
Thanks I will check it out.

While loading ramoops I see "persistent_ram: uncorrectable error in
header", is this harmful?

[  270.864969] ramoops: using module parameters
[  270.866651] persistent_ram: uncorrectable error in header
[  270.867252] persistent_ram: uncorrectable error in header
[  270.867728] persistent_ram: uncorrectable error in header
[  270.868067] persistent_ram: uncorrectable error in header
[  270.868492] persistent_ram: uncorrectable error in header
[  270.868839] persistent_ram: uncorrectable error in header
[  270.869209] persistent_ram: uncorrectable error in header
[  270.869681] persistent_ram: uncorrectable error in header
[  270.870026] persistent_ram: uncorrectable error in header
[  270.870430] persistent_ram: uncorrectable error in header
[  270.870774] persistent_ram: uncorrectable error in header
[  270.871110] persistent_ram: uncorrectable error in header
[  270.871687] persistent_ram: uncorrectable error in header
[  270.872055] persistent_ram: uncorrectable error in header
[  270.872567] persistent_ram: uncorrectable error in header
[  270.872910] persistent_ram: uncorrectable error in header
[  270.873243] persistent_ram: uncorrectable error in header
[  270.873592] persistent_ram: uncorrectable error in header
[  270.873932] persistent_ram: uncorrectable error in header
[  270.874267] persistent_ram: uncorrectable error in header
[  270.874614] persistent_ram: uncorrectable error in header
[  270.874958] persistent_ram: uncorrectable error in header
[  270.875300] persistent_ram: uncorrectable error in header
[  270.875686] persistent_ram: uncorrectable error in header
[  270.876028] persistent_ram: uncorrectable error in header
[  270.876462] persistent_ram: uncorrectable error in header
[  270.876808] persistent_ram: uncorrectable error in header
[  270.877144] persistent_ram: uncorrectable error in header
[  270.877519] persistent_ram: uncorrectable error in header
[  270.877860] persistent_ram: uncorrectable error in header
[  270.878199] persistent_ram: uncorrectable error in header
[  270.878565] persistent_ram: uncorrectable error in header
[  270.878916] persistent_ram: uncorrectable error in header
[  270.881129] console [pstore-1] enabled
[  270.884817] pstore: Registered ramoops as persistent store backend
[  270.885232] ramoops: attached 0x100000@0x3ff00000, ecc: 16/0

>
> --
> Kees Cook



-- 
Thanks,
Sekhar

      reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

Reply instructions:

You may reply publically 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=CAHhAz+hw251beDeaWRFV7oShngSQ_KAACXAzb45EZRBdZ3kbSg@mail.gmail.com \
    --to=munisekharrms@gmail.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.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

Kernel-hardening archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernel-hardening/0 kernel-hardening/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernel-hardening kernel-hardening/ https://lore.kernel.org/kernel-hardening \
		kernel-hardening@lists.openwall.com kernel-hardening@archiver.kernel.org
	public-inbox-index kernel-hardening

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.openwall.lists.kernel-hardening


AGPL code for this site: git clone https://public-inbox.org/ public-inbox