From: Petr Tesarik <ptesarik@suse.cz>
To: linux-s390@vger.kernel.org
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Subject: Is OS_INFO_VMCOREINFO unimplemented?
Date: Tue, 13 Oct 2020 14:53:03 +0200 [thread overview]
Message-ID: <20201013145303.6f99fe89@ezekiel.suse.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Hi all,
I've been looking into kernel crash dump analysis for some time now,
and I've noticed that none of my sample dumps for z/Architecture sets
OS_INFO_VMCOREINFO.
Commit 4857d4bbe9821c8d732cb84455e18e12b3d79add suggests that the
"os_info" structure should contain vmcoreinfo, but it seems that the
corresponding fields are always zero, and a quick grep for
OS_INFO_VMCOREINFO finds only code that tries to read this entry in the
panic kernel, but no code that would initialize it in the old (crashed)
kernel.
In short, the panic kernel always prints an informational message that
entry 0 is not available and falls back to get_vmcoreinfo_old().
Is this a bug, or is this interface used by a non-Linux operating
system that I'm not aware of?
TIA,
Petr Tesarik
SUSE HW Enablement
[-- Attachment #2: =?unknown-8bit?q?Digit=C3=A1ln=C3=AD?= podpis OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-10-13 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 12:53 Petr Tesarik [this message]
2020-10-16 14:11 ` Is OS_INFO_VMCOREINFO unimplemented? Philipp Rudo
2020-10-16 15:24 ` Petr Tesarik
2020-10-19 10:18 ` Philipp Rudo
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=20201013145303.6f99fe89@ezekiel.suse.cz \
--to=ptesarik@suse.cz \
--cc=holzheu@linux.vnet.ibm.com \
--cc=linux-s390@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