Comment 12 for bug 1831899
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
------- Comment From <email address hidden> 2019-06-18 03:36 EDT-------
The dumps are not z/VM dumps. All can be analysed by Linux tools...
------- Comment From <email address hidden> 2019-06-18 03:38 EDT-------
The comend "z/VM took a VMDUMP and IPLd" is not from J. Brenneman
Update informaion:
Linux Kernel is abending with a kernel oops , and z/VM OpsManager watching the virual machine console automatically ran VMDUMP of the virtual machine to dump the whole Linux virtual machine memory to spool. I pulled the 2 large dumps out of spool with the linux 'vmur receive' command with the -c argument to convert VMDUMP format to Linux kdump format. those two large dumps are linux dumps and should be able to be processed with linux tools.
I later enabled linux kdump and that gathered a couple additional dumps on subsequent abends with the same symptom and I've added those to box as well, so both VMDUMP originated huge dumps and more reasonably sized Linux Kdumps are referenced in box links in the BZ.
There is no z/VM CP development based analysis required as far as I can tell - this is entirely a Linux kernel and glibc issue.