------- Comment From [email protected] 2018-02-26 13:57 EDT------- I tried reproducing this issue in a Firestone system our team owns with Ubuntu 18.04 and I couldn't reproduce the issue.
root@ltc-fire1:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" root@ltc-fire1:~# uname -r 4.15.0-10-generic root@ltc-fire1:~# ethtool -i enP1p1s0f0 | grep "driver\|firmware\|bus-info" driver: tg3 firmware-version: 5719-v1.38i bus-info: 0001:01:00.0 root@ltc-fire1:~# lspci -vmmnn -s 0001:01:00.0 Slot: 0001:01:00.0 Class: Ethernet controller [0200] Vendor: Broadcom Limited [14e4] Device: NetXtreme BCM5719 Gigabit Ethernet PCIe [1657] SVendor: IBM [1014] SDevice: NetXtreme BCM5719 Gigabit Ethernet PCIe (FC 5260/5899 4-port 1 GbE Adapter for Power) [0420] Rev: 01 NUMANode: 0 Here is a snippet of the kdump attempt to reproduce the issue: [ 129.602468] kdump-tools[1599]: Starting kdump-tools: * sending makedumpfile -c -d 31 -F /proc/vmcore to [email protected] : /var/crash/9.40.195.135-201802261141/dump-incomplete [ 129.719688] kdump-tools[1599]: The kernel version is not supported. [ 129.720035] kdump-tools[1599]: The makedumpfile operation may be incomplete. Copying data : [100.0 %] \ eta: 0s [ 144.173303] kdump-tools[1599]: The dumpfile is saved to STDOUT. [ 144.173531] kdump-tools[1599]: makedumpfile Completed. [ 144.184688] kdump-tools[1599]: 533781+259 records in [ 144.184975] kdump-tools[1599]: 533918+1 records out [ 144.185223] kdump-tools[1599]: 273366297 bytes (273 MB, 261 MiB) copied, 14.3426 s, 19.1 MB/s [ 144.419378] kdump-tools[1599]: * kdump-tools: saved vmcore in [email protected]:/var/crash/9.40.195.135-201802261141 [ 144.439183] kdump-tools[1599]: * running makedumpfile --dump-dmesg /proc/vmcore /tmp/dmesg.201802261141 [ 144.445902] kdump-tools[1599]: The kernel version is not supported. [ 144.446266] kdump-tools[1599]: The makedumpfile operation may be incomplete. [ 144.446557] kdump-tools[1599]: The dmesg log is saved to /tmp/dmesg.201802261141. [ 144.446844] kdump-tools[1599]: makedumpfile Completed. [ 144.717033] kdump-tools[1599]: * kdump-tools: saved dmesg content in [email protected]:/var/crash/9.40.195.135-201802261141 [ 144.718981] kdump-tools[1599]: Mon, 26 Feb 2018 11:42:11 -0700 [ 144.825931] kdump-tools[1599]: Rebooting. [ 144.950195] reboot: Restarting system Both dmesg and dump file were transferred to the peer under /var/crash/ root@ltc-zz4-lp2:~# ls /var/crash/9.40.195.135-201802261141 dmesg.201802261141 dump.201802261141 Pavithra, if you still have the system, could you attempt to reproduce this issue in your environment? ------- Comment From [email protected] 2018-02-28 01:46 EDT------- Issue is not observed on same machine with 17.10 and 18.04 on same machine. we can close the bug. 18.04 ======== Starting Kernel crash dump capture service... [ 29.664816] kdump-tools[1255]: Starting kdump-tools: * sending makedumpfile -c -d 31 -F /proc/vmcore to [email protected] : /var/crash/9.47.70.29-201802280145/dump-incomplete [ 29.732510] kdump-tools[1255]: The kernel version is not supported. [ 29.732618] kdump-tools[1255]: The makedumpfile operation may be incomplete. Copying data : [100.0 %] / eta: 0s [ 41.966840] kdump-tools[1255]: The dumpfile is saved to STDOUT. [ 41.966939] kdump-tools[1255]: makedumpfile Completed. [ 42.112371] kdump-tools[1255]: 247581+447 records in [ 42.112456] kdump-tools[1255]: 247802+1 records out [ 42.112557] kdump-tools[1255]: 126874775 bytes (127 MB) copied, 11.3072 s, 11.2 MB/s [ 43.275938] kdump-tools[1255]: * kdump-tools: saved vmcore in [email protected]:/var/crash/9.47.70.29-201802280145 [ 43.295066] kdump-tools[1255]: * running makedumpfile --dump-dmesg /proc/vmcore /tmp/dmesg.201802280145 [ 43.302493] kdump-tools[1255]: The kernel version is not supported. [ 43.302611] kdump-tools[1255]: The makedumpfile operation may be incomplete. [ 43.302694] kdump-tools[1255]: The dmesg log is saved to /tmp/dmesg.201802280145. [ 43.302804] kdump-tools[1255]: makedumpfile Completed. [ 44.711325] kdump-tools[1255]: * kdump-tools: saved dmesg content in [email protected]:/var/crash/9.47.70.29-201802280145 [ 44.713050] kdump-tools[1255]: Wed, 28 Feb 2018 01:45:29 -0500 [ 44.840303] kdump-tools[1255]: Rebooting. 17.10 ====== [root@lep8a crash]# ls 9.47.70.29-201802280052 [root@lep8a crash]# cd 9.47.70.29-201802280052 [root@lep8a 9.47.70.29-201802280052]# ls dmesg.201802280052 dump.201802280052 [root@lep8a 9.47.70.29-201802280052]# tail dmesg.201802280052 [ 1133.042160] Instruction dump: [ 1133.042192] 4bfff9f1 4bfffe50 3c4c00e6 384228e0 7c0802a6 60000000 39200001 3d42001d [ 1133.042410] 394adb30 912a0000 7c0004ac 39400000 <992a0000> 4e800020 3c4c00e6 384228b0 [ 1133.042625] ---[ end trace 0b7dd69083307793 ]--- [ 1133.104189] [ 1133.104349] Sending IPI to other CPUs [ 1133.104854] IPI complete [ 1133.106269] kexec: waiting for cpu 0 (physical 8) to enter OPAL [ 1133.109422] kexec: waiting for cpu 18 (physical 26) to enter OPAL [ 1134.705583] kexec: Starting switchover sequence. Thanks, Pavithra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
