[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-04-05 Thread Launchpad Bug Tracker 
This bug was fixed in the package kexec-tools - 1:2.0.10-1ubuntu2

---
kexec-tools (1:2.0.10-1ubuntu2) xenial; urgency=medium

  * [PowerPC64] Fix failure in purgatory when compiled with gcc5
Application of upstream fixes so kexec-tools work with gcc5 on PowerPC64

commit 4a2ae3a39c64dc43e9d094be9541253234ff4822,
1e423dc297d10eb7ff25c829d2856ef12fc81d77,
3debb8cf3272216119cb2e59a4963ce3c18fe8e3
[lp: #1546260]

 -- Louis Bouchard   Tue, 05 Apr 2016
11:14:18 +0200

** Changed in: kexec-tools (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0
  [  164.495480]

[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-04-05 Thread Louis Bouchard 
Hello,

Sorry for the missing build and missing answers, I was not subscribed to
the bug.

Following your tests, I have uploaded the fixed version to the archive
which is waiting for approval since we are under beta freeze.

Since this is bugfixing, it should be approved. I'll let you know once
it hits the archive.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0
  [  164.495480] [c6efbd90] [c02dd7f0] vfs_write+0xc0/0x230
  [  164.495484] [c6efbde0] [c02de82c] SyS_write+0x6c/0x110
  [  164.495488] [c6efbe30] [c0009204] system_call+0x38/0xb4
  [  164.495490] Instruction dump:
  [  164.495493] 3842ea80 7c0802a6

[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-03-29 Thread Breno Leitão 
Anyway, I just got the source package from ppa:louis-bouchard/kexec-
tools-test and built it on ppc64el and it seems to be working fine.

The dump files are being generated:

$ find
.
./kexec_cmd
./201603291535
./201603291535/dump.201603291535
./201603291535/dmesg.201603291535
./201603291717
./201603291717/dump.201603291717
./201603291717/dmesg.201603291717

I think we are good to have it on the main archive

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0
  [  164.495480] [c6efbd90] [c02dd7f0] vfs_write+0xc0/0x230
  [  164.495484] [c6efbde0] [c02de82c] SyS_write+0x6c/0x110
  [  164.495488] [c6efbe30] [c0009204] system_call+0x38/0xb4

[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-03-29 Thread Breno Leitão 
Hey Louis, thanks for the package.

> Now the kexec-tools fixes have been uploaded to a different PPA : ppa
:louis-bouchard/kexec-tools-test

It seems that this PPA is not enabled to build for ppc64el architecture.
Would you enable that, please?

Meanwhile, i can test with building from source.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0
  [  164.495480] [c6efbd90] [c02dd7f0] vfs_write+0xc0/0x230
  [  164.495484] [c6efbde0] [c02de82c] SyS_write+0x6c/0x110
  [  164.495488] [c6efbe30] [c0009204] system_call+0x38/0xb4
  [  164.495490] Instruction dump:
  [  164.495493] 3842ea80 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019

[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-03-29 Thread Louis Bouchard 
Hello,

I am sorry that my previous comment was unclear and a bit misleading.

The kdump package in the PPA (kdump 1:1.5.9-4~lp1536904) fixes
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1536904 as
you said. This is now in the official archive so you should no longer be
using the PPA. Please confirm that you will be using the official
archive so I can proceed to delete this PPA.

Now the kexec-tools fixes have been uploaded to a different PPA : ppa
:louis-bouchard/kexec-tools-test

Please verify that the new package do indeed fixes your issue. If this
is the case, I will see that it gets uploaded to the archive.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc]

[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-03-25 Thread Louis Bouchard 
Hello,

I have a new test package ready for testing if you are able to verify. I
included the three upstream commits. I haven't identified the changes
made to the purgatory/arch/ppc64/Makefile file (part of the rebase
tarfile) so those are not included.

Since you are already using the PPA that contains kdump-tools
1:1.5.9-4~lp1536904, I can make the test package available there so you
can test without having to add a new PPA.

You should be aware though that you should no longer use that PPA. The
modifications made to kexec-tools are now present in the public archive.
in the 1:1.5.9-5 package.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0
  [  164.495480] [c6efbd90]

[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-03-25 Thread Louis Bouchard 
** Also affects: kexec-tools (Ubuntu Xenial)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: Confirmed

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: Confirmed => In Progress

** No longer affects: kexec-tools (Ubuntu Xenial)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0
  [  164.495480] [c6efbd90] [c02dd7f0] vfs_write+0xc0/0x230
  [  164.495484] [c6efbde0] [c02de82c] SyS_write+0x6c/0x110
  [  164.495488] [c6efbe30] [c0009204] system_call+0x38/0xb4
  [  164.495490] Instruction dump:
  [  164.495493] 3842ea80 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
394956e4 
  [

[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-03-24 Thread Breno Leitão 
Good news! The patches were just accepted earlier today:

http://git.kernel.org/cgit/utils/kernel/kexec/kexec-tools.git/commit/?id=4a2ae3a39c64dc43e9d094be9541253234ff4822
http://git.kernel.org/cgit/utils/kernel/kexec/kexec-tools.git/commit/?id=1e423dc297d10eb7ff25c829d2856ef12fc81d77
http://git.kernel.org/cgit/utils/kernel/kexec/kexec-tools.git/commit/?id=3debb8cf3272216119cb2e59a4963ce3c18fe8e3

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0
  [  164.495480] [c6efbd90] [c02dd7f0] vfs_write+0xc0/0x230
  [  164.495484] [c6efbde0] [c02de82c] SyS_write+0x6c/0x110
  [  164.495488] [c6efbe30] [c0009204] system_call+0x38/0xb4
  [

[Kernel-packages] [Bug 1546260] Re: kexec/kdump not working in ubuntu 16.04

2016-03-22 Thread Breno Leitão 
** Changed in: ubuntu
   Status: New => Confirmed

** Package changed: ubuntu => kexec-tools (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546260

Title:
  kexec/kdump not working in ubuntu 16.04

Status in kexec-tools package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-02-04 
04:11:48 ==
  Hi 

I installed Ubuntu16.04 as PowerVM/KVM/PowerNV and setup kdump as
  well use PPA build to resolve sym link problem broken installed kdump-
  tools   1:1.5.9-4~lp1536904, and trigger kdump .While dumping process
  console hung not able to get vmcore.

  
  Reproducible Step:

  1- Installed Ubuntu16.04 
  2- Installed PPA build of Kdump mentioned in bug135822
  3- Start kdump service 
  4- Trigger a panic 

  Expected Result :

  Able to generate kdump

  Actual Result :

  System halt on dump process , seems me having initrd issue

  LOG:

  root@ubuntu:~# kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=9d1662d4-db2a-4a1a-b8d7-8b0d4e7872dd  ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156288K 
   * loaded kdump kernel


  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-2-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-2-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-2-generic 
root=UUID=2a78d070-4b73-4da6-b7eb-d41164c909fa ro splash quiet irqpoll 
maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:~# 
  root@ubuntu:~# kdump-config status
  current state   : ready to kdump
  root@ubuntu:~#

  root@ubuntu:~# echo 1 > /proc/sys/kernel/sysrq

  
  root@ubuntu:~# echo c > /proc/sysrq-trigger
  [  164.495349] sysrq: SysRq : Trigger a crash
  [  164.495360] Unable to handle kernel paging request for data at address 
0x
  [  164.495364] Faulting instruction address: 0xc0654db4
  [  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
  [  164.495370] SMP NR_CPUS=2048 NUMA pSeries
  [  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas 
usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic 
#16-Ubuntu
  [  164.495393] task: c003f1f2a200 ti: c6ef8000 task.ti: 
c6ef8000
  [  164.495396] NIP: c0654db4 LR: c0655e68 CTR: 
c0654d80
  [  164.495399] REGS: c6efb990 TRAP: 0300   Not tainted  
(4.4.0-2-generic)
  [  164.495401] MSR: 80009033   CR: 2824  
XER: 0001
  [  164.495410] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c0655e68 c6efbc10 c1583800 0063 
  GPR04: c003ff609c50 c003ff61b4f0 c003ffe6c200 015b 
  GPR08: 0007 0001  c003ffe72710 
  GPR12: c0654d80 c7ae  2200 
  GPR16: 10170710 01002c890608 101406f0 100c7100 
  GPR20:  1017df98 10140588  
  GPR24: 10153440 1017b848 c14c8540 0004 
  GPR28: c14c8900 0063 c14810bc  
  [  164.495451] NIP [c0654db4] sysrq_handle_crash+0x34/0x50
  [  164.495454] LR [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495456] Call Trace:
  [  164.495460] [c6efbc10] [c0de3008] 
_fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
  [  164.495464] [c6efbc30] [c0655e68] __handle_sysrq+0xe8/0x270
  [  164.495468] [c6efbcd0] [c0656608] 
write_sysrq_trigger+0x78/0xa0
  [  164.495472] [c6efbd00] [c0374e70] proc_reg_write+0xb0/0x110
  [  164.495476] [c6efbd50] [c02dcabc] __vfs_write+0x6c/0xe0
  [  164.495480] [c6efbd90] [c02dd7f0] vfs_write+0xc0/0x230
  [  164.495484] [c6efbde0] [c02de82c] SyS_write+0x6c/0x110
  [  164.495488] [c6efbe30] [c0009204] system_call+0x38/0xb4
  [  164.495490] Instruction dump:
  [  164.495493] 3842ea80 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
394956e4 
  [  164.495499] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6 
  [  164.495506] ---[ end trace 5ddbc181c028cb6c ]---
  [  164.497176] 
  [  164.497180]