------- Comment From naveed...@in.ibm.com 2018-08-07 07:01 EDT------- we are able to analyse the kernel dump using crash on 4.4.0-131-generic kernel (Ubuntu 16.04.5). we can close this defect.
====console logs=== 0-131-generic dump.201808070540 08070540# crash /usr/lib/debug/boot/vmlinux-4.4.0 crash 7.1.4 Copyright (C) 2002-2015 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.4.0-131-generic DUMPFILE: dump.201808070540 [PARTIAL DUMP] CPUS: 160 DATE: Tue Aug 7 05:39:33 2018 UPTIME: 00:05:29 LOAD AVERAGE: 0.10, 0.29, 0.18 TASKS: 1364 NODENAME: ltc-briggs1 RELEASE: 4.4.0-131-generic VERSION: #157-Ubuntu SMP Thu Jul 12 15:47:54 UTC 2018 MACHINE: ppc64le (2926 Mhz) MEMORY: 256 GB PANIC: "sysrq: SysRq : Trigger a crash" PID: 3257 COMMAND: "bash" TASK: c000001f61bc93e0 [THREAD_INFO: c000001fa9f14000] CPU: 14 STATE: TASK_RUNNING (SYSRQ) crash> bt PID: 3257 TASK: c000001f61bc93e0 CPU: 14 COMMAND: "bash" #0 [c000001fa9f17680] crash_kexec at c0000000001776f4 #1 [c000001fa9f17820] die at c000000000020ed8 #2 [c000001fa9f178b0] bad_page_fault at c000000000051d98 #3 [c000001fa9f17920] handle_page_fault at c000000000008800 Data Access [300] exception frame: R0: c00000000067d8a8 R1: c000001fa9f17c10 R2: c00000000160aa00 R3: 0000000000000063 R4: c000001ff4b89c50 R5: c000001ff4b9b4e0 R6: c000003fff010000 R7: 0000000000000573 R8: 0000000000000007 R9: 0000000000000001 R10: 0000000000000000 R11: c000003fff030208 R12: c00000000067c7a0 R13: c000000007ae8c00 R14: ffffffffffffffff R15: 0000000022000000 R16: 0000000010170dd0 R17: 0000010015780298 R18: 0000000010140568 R19: 00000000100c7000 R20: 0000000000000000 R21: 000000001017dd78 R22: 0000000010140400 R23: 0000000000000000 R24: 00000000101532c0 R25: 000000001017b628 R26: c000000001549d18 R27: 0000000000000004 R28: c00000000154a0d8 R29: 0000000000000063 R30: c0000000015013bc R31: 0000000000000000 NIP: c00000000067c7d4 MSR: 9000000000009033 OR3: c000000000008498 CTR: c00000000067c7a0 LR: c00000000067d8a8 XER: 0000000020000000 CCR: 0000000028242222 MQ: 0000000000000001 DAR: 0000000000000000 DSISR: 0000000042000000 Syscall Result: 0000000000000000 #4 [c000001fa9f17c10] sysrq_handle_crash at c00000000067c7d4 [Link Register] [c000001fa9f17c10] __handle_sysrq at c00000000067d8a8 crash> crash> -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1746088 Title: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel Status in The Ubuntu-power-systems project: Fix Committed Status in crash package in Ubuntu: Fix Released Status in crash source package in Xenial: Fix Committed Status in crash source package in Artful: Won't Fix Status in crash source package in Bionic: Fix Released Bug description: [Impact] It won't be possible to analyze dumps produced by newer kernels (hwe on xenial, for example). [Test Case] Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) kernels. [Regression Potential] New crash versions may have bugs and some commands not work with older kernels. The smoke test helps a little, but more testing may be desirable. ---Problem Description--- Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel (Ubuntu 16.04.4) ---uname output--- Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8001-22C ---Steps to Reproduce--- This bug follow up bug of https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565 The steps to create dump is as follows Once you generate the kdump use crash to analyze the vmcore and we get this error ================console logs ========== root@ltc-briggs1:/var/crash/201801150227# ls dmesg.201801150227 vmcore.201801150227 .0-26-generic vmcore.2018011502271150227# crash /usr/lib/debug/boot/vmlinux-4.13. crash 7.1.4 Copyright (C) 2002-2015 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"... please wait... (gathering module symbol data) WARNING: cannot access vmalloc'd module memory crash: invalid structure member offset: thread_info_task FILE: task.c LINE: 598 FUNCTION: irqstacks_init() [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 => 100833e0 100833e0: (undetermined) 1017d220: OFFSET_verify+80 1011552c: task_init+5084 1008ade0: main_loop+336 == Comment from Hari Krishna Bathini == There are quite a few commits (all available upstream) that are needed for crash tool to work fine. I think the right thing to do here would be to use the latest crash tool version 7.2.0 to go with the kernel update. Also, the below commit would be needed on top of 7.2.0 crash utility: commit c8178eca9c74f81a7f803a58d339635cc152e8d9 Author: Dave Anderson <ander...@redhat.com> Date: Thu Nov 9 11:39:05 2017 -0500 Update for support of Linux 4.14 and later PPC64 kernels where the hash page table geometry accomodates a larger virtual address range. Without the patch, the virtual-to-physical translation of user space virtual addresses by "vm -p", "vtop", and "rd -u" may generate an invalid translation or otherwise fail. (hbath...@linux.vnet.ibm.com) Similar thing holds true for makedumpfile tool.. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+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
