[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2017-05-12 Thread Louis Bouchard 
** Changed in: makedumpfile (Ubuntu)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: makedumpfile (Ubuntu Wily)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [  238.873125] REGS: c00fe022f990 TRAP: 0300   Not tainted  
(4.3.0-5-generic)
  [  238.873200] MSR: 90009033   CR: 28004222  
XER: 2000
  [  238.873392] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c06475f8 c00fe022fc10 c155e400 0063 
  GPR04: c007fc648450 c007fc659cf0 c01fff83 0792 
  GPR08: 0007 0001  c01fff861780 
  GPR12: c0646500 c7b87d80   
  GPR16:     
  GPR20:   10009d88 0001 
  GPR24: 10009d88 3fffe7b210b0 c14a5cb0 0004 
  GPR28: c14a6070 0063 c1460de4  
  [  238.875062] NIP

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-02-09 Thread Launchpad Bug Tracker 
This bug was fixed in the package makedumpfile - 1:1.5.9-4

---
makedumpfile (1:1.5.9-4) sid; urgency=medium

  * Allow for symlinks to be created for vmlinux files : On Power8
architecture, systems are booting from a vmlinux file. The symlink
/var/lib/kdump/vmlinuz has to point to this file.  (LP: #1536904)

  * Add functionality to create symlinks for older kernels : If kdump
is installed on systems with more than one kernel package, the smaller
initrd.img file will only be created for the latest kernel. Adding the
'symlinks' functionality will allow for the creation of symlinks to
older kernels. If the smaller initrd.img file is missing in /var/lib/kdump
it will be created beforehand.  This will be preempted if kdump is already
loaded. (LP: #1537714)

  * Fix kdump-config manpage : add documentation for the propagate option.
(LP: #1538148)

  * Improve manpage for kdump-config

 -- Louis Bouchard   Tue, 26 Jan 2016
15:30:48 +0100

** Changed in: makedumpfile (Ubuntu)
   Status: In Progress => Fix Released

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-02-04 Thread bugproxy 
--- Comment From iranna.an...@in.ibm.com 2016-02-05 00:30 EDT---
(In reply to comment #21)
> Ok.. Let us close this bug as symlink issue is resolved.
> Please open a new bug to track the hang issue.
>
> Thanks
> Hari

Alright..Closing this bug.

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1604

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [  238.873125] REGS: c00fe022f990 TRAP: 0300   Not tainted  
(4.3.0-5-generic)
  [  238.873200] MSR: 90009033   CR: 28004222  
XER: 2000
  [  238.873392] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c06475f8 c00fe022fc10 c155e400 0063 
  GPR04: c007fc648450 c007fc659cf0 c01fff83 0792 
  GPR08: 0007 0001  c01fff861780 
  GPR12: c0646500 c7b87d80   
  GPR16:     
  GPR20:   10009d88 0001 
  GPR24: 10009d88 3fffe7b210b0

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-02-04 Thread bugproxy 
--- Comment From praveen.pan...@in.ibm.com 2016-02-04 04:14 EDT---
raised kdump bug :

https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588

** Bug watch added: bugzilla.linux.ibm.com/ #136588
   https://bugzilla.linux.ibm.com/show_bug.cgi?id=136588

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [  238.873125] REGS: c00fe022f990 TRAP: 0300   Not tainted  
(4.3.0-5-generic)
  [  238.873200] MSR: 90009033   CR: 28004222  
XER: 2000
  [  238.873392] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c06475f8 c00fe022fc10 c155e400 0063 
  GPR04: c007fc648450 c007fc659cf0 c01fff83 0792 
  GPR08: 0007 0001  c01fff861780 
  GPR12: c0646500 c7b87d80   
  GPR16:     
  GPR20:   10009d88 0001 
  GPR24: 10009d88 3fffe7b210b0 c14a5cb0 0004 
  GPR28: c14a6070 0063

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-01-29 Thread Louis Bouchard 
Hello,

You can find the upcoming version in the following PPA : ppa:louis-
bouchard/makedumpfile-tests. Here is the changelog :

  * Allow for symlinks to be created for vmlinux files : On Power8  
  
architecture, systems are booting from a vmlinux file. The symlink  
  
/var/lib/kdump/vmlinuz has to point to this file.  (LP: #1536904)   
  

  
  * Add functionality to create symlinks for older kernels : If kdump   
  
is installed on systems with more than one kernel package, the smaller  
  
initrd.img file will only be created for the latest kernel. Adding the  
  
'symlinks' functionality will allow for the creation of symlinks to 
  
older kernels. If the smaller initrd.img file is missing in /var/lib/kdump  
  
it will be created beforehand.  This will be preempted if kdump is already  
  
loaded. (LP: #1537714)  
  

  
  * Fix kdump-config manpage : add documentation for the propagate option.  
  
(LP: #1538148)  
  

  
  * Improve manpage for kdump-config

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-01-29 Thread Louis Bouchard 
Sorry for the formatting : the ppa is

ppa:louis-bouchard/makedumpfile-tests

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [  238.873125] REGS: c00fe022f990 TRAP: 0300   Not tainted  
(4.3.0-5-generic)
  [  238.873200] MSR: 90009033   CR: 28004222  
XER: 2000
  [  238.873392] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c06475f8 c00fe022fc10 c155e400 0063 
  GPR04: c007fc648450 c007fc659cf0 c01fff83 0792 
  GPR08: 0007 0001  c01fff861780 
  GPR12: c0646500 c7b87d80   
  GPR16:     
  GPR20:   10009d88 0001 
  GPR24: 10009d88 3fffe7b210b0 c14a5cb0 0004 
  GPR28: c14a6070 0063 c1460de4  
  [  238.875062] NIP [c0646534] sysrq_handle_crash+0x34/0x50
  [  238.875178] LR [c06475f8] __handle_sysrq+0xe8/0x280
  [

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-01-26 Thread Louis Bouchard 
Hello,

Sorry for the delay in replying.

This is definitively a regression following the implementation of
smaller initrd. I am currently working at fixing this. Your second
problem might be caused by not using smaller initrd so I would suggest
to wait to test the fix for this.

I can have a test package available quickly if you have the possibility
of testing from a PPA (according to a previous bug I think you do) so
let me know & I'll tell you where to find the PPA.

** Changed in: makedumpfile (Ubuntu)
   Status: Invalid => In Progress

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Louis Bouchard 
(louis-bouchard)

** Also affects: makedumpfile (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: makedumpfile (Ubuntu Wily)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu Wily)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [  238.873125] REGS:

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-01-25 Thread Louis Bouchard 
Hello,

I must admit that I am a bit puzzled by some of your statements :

  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools

Step 2 is not required : kdump-tools is a dependency of linux-crashdump
so it is installed automatically :

  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
This is not required. kdump-tools 1:1.5.9-3 does that automatically during 
installation and you should be prompted to accept it :

  ┌──┤ Configuring kdump-tools 
├──┐   
  │ 
  │   
  │ If you choose this option, the kdump-tools mechanism will be enabled. A 
reboot is still required in order to enable   │   
  │ the crashkernel kernel parameter.   
  │   
  │ 
  │   
  │ Should kdump-tools be enabled by default?   
  │   
  │ 
  │   
  │
  │   
  │ 
  │   
  
└───┘
   

  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load

This will fail with the following :

# kdump-config load
 * no crashkernel= parameter in the kernel cmdline

Which is normal as a reboot is required in order to have the crashkernel
parameter taken into account after the reboot.

  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

The hang following this command is normal : as previously stated, a
reboot is required otherwise kdump-tools is not loaded.

After the reboot, you should see the following in /var/log/syslog :

Jan 25 11:12:25 XenialS-crashdump kdump-tools[523]: Starting kdump-tools:  * 
Missing symlink : /var/lib/kdump/initrd.img
Jan 25 11:12:25 XenialS-crashdump kdump-tools[523]: * Creating symlink 
/var/lib/kdump/initrd.img
Jan 25 11:12:25 XenialS-crashdump kdump-tools[523]: * Missing symlink : 
/var/lib/kdump/vmlinuz
Jan 25 11:12:25 XenialS-crashdump kdump-tools[523]: * Creating symlink 
/var/lib/kdump/vmlinuz
Jan 25 11:12:26 XenialS-crashdump kdump-tools[523]: * loaded kdump kernel

To verify the status of kdump you can do :

# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x2c00
current state:ready to kdump

kexec command:
  /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-4.3.0-7-generic 
root=/dev/mapper/VividS--vg-root ro console=ttyS0,115200 irqpoll maxcpus=1 
nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

Your bug statement shows the following :

  /sbin/kexec -p --args-linux --command-
line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service"
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic

This : --initrd=/boot/initrd.img-4.3.0-5-generic
/boot/vmlinux-4.3.0-5-generic indicates that kdump-tools is not properly
configured and that your /etc/default/kdump-tools file is the one from a
previous version.  I suspect that kdump-tools was improperly configured
or that installation of the maintainer's version of the file was
refused.

Since 15.10 (Wily), /etc/default/kdump-tools has the following :

KDUMP_KERNEL=/var/lib/kdump/vmlinuz
KDUMP_INITRD=/var/lib/kdump/initrd.img

This was implemented to fix LP: #1496317 which might be the bug that you
are encountering.

I suggest that you verify your configuration and run the test again as
your description does not describe an actual bug but misconfiguration of
kdump-tools



** Changed in: makedumpfile (Ubuntu)
   Status: New => Invalid

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com,

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-01-22 Thread Steve Langasek 
** Package changed: ubuntu => makedumpfile (Ubuntu)

-- 
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/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [  238.873125] REGS: c00fe022f990 TRAP: 0300   Not tainted  
(4.3.0-5-generic)
  [  238.873200] MSR: 90009033   CR: 28004222  
XER: 2000
  [  238.873392] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c06475f8 c00fe022fc10 c155e400 0063 
  GPR04: c007fc648450 c007fc659cf0 c01fff83 0792 
  GPR08: 0007 0001  c01fff861780 
  GPR12: c0646500 c7b87d80   
  GPR16:     
  GPR20:   10009d88 0001 
  GPR24: 10009d88 3fffe7b210b0 c14a5cb0 0004 
  GPR28: c14a6070 0063 c1460de4  
  [  238.875062] NIP [c0646534] sysrq_handle_crash+0x34/0x50
  [  238.875178] LR [c06475f8] __handle_sysrq+0xe8/0x280
  [  238.875270] Call Trace:
  [  238.875322] [c00fe022fc10] [c0dc92a0]