>------- Comment From [email protected] 2018-03-05 09:46 EDT------- >Hi Cascardo, > >(In reply to comment #19) >> We are working on getting those fixes to 16.04, on the -updates repository. >> But it's not part of 16.04.4. > >I am not sure I understood the following statement. Do you mean that the fix >will be pushed to >-updates archive after the 16.04.4, thus, it will not make >the 16.04.4 cut date? > >If that is the case, that might cause some impacts, because we are making a >release that contains >some known regressions. Should we document it somewhere? > >Thank you, >Breno
Hi, Breno. >From my testing on xenial and hwe kernel, kexec still works and makedumpfile will fallback to cp. Then, one can copy that dump to a bionic system and use crash from bionic to analyze it. Can you test that such a produced dump can be analyzed by crash on bionic? I want to make sure we are still producing valid dumps on most cases, or identify when dumps are not valid. Some of the hwe kernels with kpti backports are not dumpable, but the next artful and hwe release, to be in -proposed by next week, should have that fixed in the kernel side. I am still investigating the possibility of getting all this into a better situation, but I want to make sure that the current situation is not that bad as you are saying. Thanks. Cascardo. -- 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: Triaged Status in crash package in Ubuntu: Fix Released Status in crash source package in Xenial: New Status in crash source package in Artful: In Progress Status in crash source package in Bionic: Fix Released Bug description: ---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 <[email protected]> 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. ([email protected]) 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 : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
