linux-kernel - efi-pstore: Crash logs not written

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 12 Sep 2019 14:51:53 +0200
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Kees Cook <keescook@...omium.org>,
        Anton Vorontsov <anton@...msg.org>,
        Colin Cross <ccross@...roid.com>,
        Tony Luck <tony.luck@...el.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: efi-pstore: Crash logs not written

Dear Linux folks,

On a Dell OptiPlex 5040 with Linux 5.3-rc8, I’ll try to get
efi-pstore working.

```
$ lsmod | grep efi
efi_pstore             16384  0
pstore                 28672  1 efi_pstore
efivarfs               16384  1
$ dmesg | grep pstore
[ 2569.826541] pstore: Using crash dump compression: deflate
[ 2569.826542] pstore: Registered efi as persistent store backend
```

Triggering a crash with `echo c | sudo tee /proc/sysrq-trigger`,
there is nothing in `/sys/fs/pstore` after the reboot.

Please note, that there is also a crash kernel configured, so
there are actually to reboots, but that should not conflict,
right?

Hints on how to debug that would be appreciated. Please find the
Linux messages attached.

Kind regards,

Paul

View attachment "linux-5.3-rc8-messages.txt" of type "text/plain" (53493 bytes)

View attachment "config-5.3.0-rc8.mx64.289" of type "text/plain" (137146 bytes)

Download attachment "smime.p7s" of type "application/pkcs7-signature" (5174 bytes)