------- Comment From pavra...@in.ibm.com 2018-02-26 00:13 EDT------- (In reply to comment #19) > Sorry, but that version number is not sufficient. It cannot distinguish > between package versions, which might contain patches? When you give a > makedumpfile version, can you use dpkg -s makedumpfile? > > Also, I need to know which kernel version you dumped with that. And if crash > could successfully load it. It might be that makedumpfile dumps (though > incorrectly) a newer kernel, but, then, crash won't be able to analyze it. > Can you test that? And, please, test the makedumpfile from the ppa. > > Thanks. > Cascardo.
Please find crash tool output below. -generic dump.201802210519 02210519# crash /usr/lib/debug/boot/vmlinux-4.15.0-10- crash 7.2.1 Copyright (C) 2002-2017 Red Hat, Inc. Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation Copyright (C) 1999-2006 Hewlett-Packard Co Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. Copyright (C) 2005, 2011 NEC Corporation Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. This program is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Enter "help copying" to see the conditions. This program has absolutely no warranty. Enter "help warranty" for details. GNU gdb (GDB) 7.6 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "powerpc64le-unknown-linux-gnu"... KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-10-generic DUMPFILE: dump.201802210519 [PARTIAL DUMP] CPUS: 1 DATE: Wed Feb 21 05:18:51 2018 UPTIME: 00:04:50 LOAD AVERAGE: 0.01, 0.08, 0.04 TASKS: 105 NODENAME: ubuntu RELEASE: 4.15.0-10-generic VERSION: #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 MACHINE: ppc64le (2250 Mhz) MEMORY: 2 GB PANIC: "sysrq: SysRq : Trigger a crash" PID: 1737 COMMAND: "bash" TASK: c00000007c44cf00 [THREAD_INFO: c00000007c47c000] CPU: 0 STATE: TASK_RUNNING (SYSRQ) crash> bt PID: 1737 TASK: c00000007c44cf00 CPU: 0 COMMAND: "bash" #0 [c00000007c47f850] crash_kexec at c0000000001e0930 #1 [c00000007c47f890] oops_end at c0000000000258e8 #2 [c00000007c47f910] bad_page_fault at c00000000006a1e0 #3 [c00000007c47f980] handle_page_fault at c00000000000a560 Data Access [300] exception frame: R0: c0000000007eb1a8 R1: c00000007c47fc70 R2: c0000000016ea600 R3: 0000000000000063 R4: c00000007fd4ce18 R5: c00000007fd64368 R6: 6967676572206120 R7: 63726173680d0a72 R8: 0000000000000007 R9: 0000000000000001 R10: 0000000000000000 R11: 0000000000000000 R12: c0000000007ea240 R13: c000000007a80000 R14: 000001f7efb34348 R15: 0000000000000000 R16: 000001f7ef96e9f0 R17: 000001f7efa01998 R18: 000001f7efa019d0 R19: 000001f7efa38204 R20: 0000000000000000 R21: 0000000000000001 R22: 0000000000000000 R23: 00007ffff78cdfe4 R24: 00007ffff78cdfe0 R25: 000001f7efa3afc4 R26: c0000000015e9930 R27: 0000000000000002 R28: 0000000000000063 R29: 0000000000000007 R30: c000000001572a9c R31: c0000000015e9cd0 NIP: c0000000007ea268 MSR: 8000000000009033 OR3: c0000000007eb1a4 CTR: c0000000007ea240 LR: c0000000007eb1a8 XER: 0000000020040000 CCR: 0000000028222222 MQ: 0000000000000001 DAR: 0000000000000000 DSISR: 0000000042000000 Syscall Result: 0000000000000000 #4 [c00000007c47fc70] sysrq_handle_crash at c0000000007ea268 [Link Register] [c00000007c47fc70] __handle_sysrq at c0000000007eb1a8 #5 [c00000007c47fd10] write_sysrq_trigger at c0000000007eb9b4 #6 [c00000007c47fd40] proc_reg_write at c00000000047c548 #7 [c00000007c47fd70] __vfs_write at c0000000003cf8dc #8 [c00000007c47fd90] vfs_write at c0000000003cfb38 #9 [c00000007c47fde0] sys_write at c0000000003cfe58 #10 [c00000007c47fe30] system_call at c00000000000b184 System Call [c01] exception frame: R0: 0000000000000004 R1: 00007ffff78cddf0 R2: 00007841f7ca7300 R3: 0000000000000001 R4: 000001f7efb41008 R5: 0000000000000002 R6: 0000000000000010 R7: ffffffffffffffff R8: 0000000000000000 R9: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: 00007841f7dcb0a0 NIP: 00007841f7bddca8 MSR: 800000000000f033 OR3: 0000000000000001 CTR: 0000000000000000 LR: 00007841f7b50418 XER: 0000000000000000 CCR: 0000000048222882 MQ: 0000000000000001 DAR: 000001f7efb73808 DSISR: 000000000a000000 Syscall Result: 0000000000000000 crash> Thanks, Pavithra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1746299 Title: update makedumpfile tool version to v1.6.3 Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Bug description: [Impact] New upstream kernel versions, as those in linux-hwe package, require a newer makedumpfile to be supported. Otherwise, all copies fallback to copying the entire memory. [Test case] kdump-tools has been installed, system rebooted, then crash trigerred and verified that a small dump file was present on /var/crash/. Tested on amd64 and ppc64le. [Regression potential] Many other bug fixes have been included in the latest version of the package. The changes are supposed to fix these bugs, and have been tested as well. However, as the total of changes is not trivial, there is impact of regression that has been minimized by the tests done. Regression potential of not supporting older kernels has been tested with the kernels shipped on xenial and artful as well. ==================================================================== == Comment: #0 - Hari Krishna Bathini <hbath...@in.ibm.com> - 2018-01-30 10:46:53 == ---Problem Description--- update makedumpfile to latest version v1.6.3 that officially supports up to kernel version 4.14.8. Since makedumpfile is inherently backward compatible, this would not break existing functionality.. Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Â makedumpfile reports ""The kernel version is not supported" while generating vmcore Also, there is a possibility of bogus address translations in makedumpfile tool with missing upstream patches. Can't be so sure without an exhaustive testing. Instead, it would be a good idea to go with the version which officially supports the kernel version in question. Userspace tool common name: makedumpfile The userspace tool has the following bit modes: 64-bit Userspace rpm: makedumpfile Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Hari Krishna Bathini <hbath...@in.ibm.com> - 2018-01-30 10:49:13 == With kernel version updated to 4.13.0, please update makedumpfile tool version to 1.6.3 which officially supports up to kernel version 4.14.8 [1]. Thanks Hari [1] http://lists.infradead.org/pipermail/kexec/2018-January/019853.html This needs to be tagged for both 16.04.4 & 18.04 releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
