Is OS_INFO_VMCOREINFO unimplemented?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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: pgpJW5vIxksXw.pgp
Description: Digitální podpis OpenPGP


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Kernel Development]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Info]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Linux Media]     [Device Mapper]

  Powered by Linux