This has been blocked because we need to get changes on the development release first, and recent changes on testing has caused ppc64el testing failures. Those changes allowed tests to be run on VMs with more memory, which allow the test to run instead of being skipped. So now we are detecting a failure, though I couldn't be able to reproduce it so far, which is what is blocking progress here.
I will try other approaches to try to reproduce and investigate. Cascardo. -- 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/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in makedumpfile source package in Xenial: New Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Fix Released Bug description: [Impact] After a DLPAR memory/CPU add/remove operation, kdump tools need to be restarted or else kdump tools will fail to capture the crash. [Test] == Comment: #0 - Ping Tian Han <[email protected]> - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/[email protected] Carrie Mitsuyoshi/[email protected] ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/[email protected] Carrie Mitsuyoshi/[email protected]: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan <[email protected]> - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [ 0.000000] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) [Regression Potential] The fix applies to makedumpfile, and could impact dump capture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+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
