------- Comment From hbath...@in.ibm.com 2018-08-11 08:48 EDT-------
After upgrading to kdump-tools_1.6.4-1~16.04.0cascardo2_ppc64el.deb package,
dump capture succeeds without any complaints:

The udev rules trigger kdump-tools service reload as can be seen below:
--
root@ubuntu:~# dpkg -l | grep kdump-tools
ii  kdump-tools                                   1:1.6.4-1~16.04.0cascardo2    
    ppc64el      scripts and tools for automating kdump (Linux crash dumps)
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~# systemctl status kdump-tools.service -l
? kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres
Active: active (exited) since Sat 2018-08-11 08:33:27 EDT; 2min 8s ago
Process: 25166 ExecStop=/etc/init.d/kdump-tools stop (code=exited, status=0/SU
Process: 25200 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/
Main PID: 25200 (code=exited, status=0/SUCCESS)

Aug 11 08:33:26 ubuntu systemd[1]: Starting Kernel crash dump capture service...
Aug 11 08:33:26 ubuntu kdump-tools[25200]: Starting kdump-tools:  * Creating sym
Aug 11 08:33:26 ubuntu kdump-tools[25200]:  * Creating symlink /var/lib/kdump/in
Aug 11 08:33:26 ubuntu kdump-tools[25200]: Modified cmdline:BOOT_IMAGE=/boot/vml
Aug 11 08:33:26 ubuntu kdump-tools[25200]:  * loaded kdump kernel
Aug 11 08:33:26 ubuntu kdump-tools[25248]: /sbin/kexec -p --command-line="BOOT_I
Aug 11 08:33:27 ubuntu kdump-tools[25249]: loaded kdump kernel
Aug 11 08:33:27 ubuntu systemd[1]: Started Kernel crash dump capture service.
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~# drmgr -c mem -r -q 1
Validating Memory DLPAR capability...yes.
[1459216.723209] pseries-hotplug-mem: Attempting to hot-remove 1 LMB(s)
[1459216.749014] Offlined Pages 4096
[1459193.925176] kdump-tools[25419]: Stopping kdump-tools:  * unloaded kdump 
kernel
[1459193.985143] kdump-tools[25453]: Starting kdump-tools:  * Creating symlink 
/var/lib/kdump/vmlinuz
[1459193.986120] kdump-tools[25453]:  * Creating symlink 
/var/lib/kdump/initrd.img
[1459194.024961] kdump-tools[25453]: Modified 
cmdline:BOOT_IMAGE=/boot/vmlinux-4.15.0-24-generic 
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro xmon=on nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb elfcorehdr=158144K
[1459217.005820] pseries-hotplug-mem: Memory at 40000000 was hot-removed
DR_TOTAL_RESOURCES=1
root@ubuntu:~# [1459194.297073] kdump-tools[25453]:  * loaded kdump kernel

root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~# systemctl status kdump-tools.service -l
? kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres
Active: active (exited) since Sat 2018-08-11 08:35:47 EDT; 12s ago
Process: 25419 ExecStop=/etc/init.d/kdump-tools stop (code=exited, status=0/SU
Process: 25453 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/
Main PID: 25453 (code=exited, status=0/SUCCESS)

Aug 11 08:35:47 ubuntu systemd[1]: Starting Kernel crash dump capture service...
Aug 11 08:35:47 ubuntu kdump-tools[25453]: Starting kdump-tools:  * Creating sym
Aug 11 08:35:47 ubuntu kdump-tools[25453]:  * Creating symlink /var/lib/kdump/in
Aug 11 08:35:47 ubuntu kdump-tools[25453]: Modified cmdline:BOOT_IMAGE=/boot/vml
Aug 11 08:35:47 ubuntu kdump-tools[25453]:  * loaded kdump kernel
Aug 11 08:35:47 ubuntu kdump-tools[25505]: /sbin/kexec -p --command-line="BOOT_I
Aug 11 08:35:47 ubuntu kdump-tools[25506]: loaded kdump kernel
Aug 11 08:35:47 ubuntu systemd[1]: Started Kernel crash dump capture service.
root@ubuntu:~#
--

and dump captured successfully after memory dlpar operation:

--
[  139.944700] kdump-tools[1278]: Starting kdump-tools:  * running makedumpfile 
-c -d 31 /proc/vmcore /var/crash/201808110838/dump-incomplete
Copying data                                      : [100.0 %] -           eta: 
0s
[  147.858420] kdump-tools[1278]: The kernel version is not supported.
[  147.858718] kdump-tools[1278]: The makedumpfile operation may be incomplete.
[  147.859002] kdump-tools[1278]: The dumpfile is saved to 
/var/crash/201808110838/dump-incomplete.
[  147.859260] kdump-tools[1278]: makedumpfile Completed.
[  147.899799] kdump-tools[1278]:  * kdump-tools: saved vmcore in 
/var/crash/201808110838
[  147.998442] kdump-tools[1278]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201808110838/dmesg.201808110838
[  148.008063] kdump-tools[1278]: The kernel version is not supported.
[  148.008436] kdump-tools[1278]: The makedumpfile operation may be incomplete.
[  148.008672] kdump-tools[1278]: The dmesg log is saved to 
/var/crash/201808110838/dmesg.201808110838.
[  148.008913] kdump-tools[1278]: makedumpfile Completed.
[  148.009135] kdump-tools[1278]:  * kdump-tools: saved dmesg content in 
/var/crash/201808110838
[  148.033105] kdump-tools[1278]: Sat, 11 Aug 2018 08:38:51 -0400
[  148.069165] kdump-tools[1278]: Rebooting.
[  148.276176] reboot: Restarting system
--

Thanks
Hari

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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:
  Incomplete
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han <pt...@cn.ibm.com> - 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/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---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/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan <brsri...@in.ibm.com> -
  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)

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     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to