[Group.of.nepali.translators] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

2016-12-08 Thread Launchpad Bug Tracker
This bug was fixed in the package makedumpfile - 1:1.6.0-2ubuntu1.2

---
makedumpfile (1:1.6.0-2ubuntu1.2) yakkety; urgency=medium

  * d/p/0003-PATCH-v2-Support-_count-_refcount-rename-in-struct-p.patch,
d/p/0004-fix-readpage_elf-attempt-to-read-non-existent-page.patch
Fix makedumpfile failure on 4.8 kernels.
 - Makedumpfile will exit on error with the following message :
   get_mem_map: Can't distinguish the memory type. (LP: #1626269)
 - Fix readpage_elf: Attempt to read non-existent page errors after
   previous patch is applied

  [ Rinat ]
  * Fix double-quote handling in /proc/cmdline
Parsing of the cmdline would fail if double-quotes are encountered
in /proc/cmdine (i.e. like when things like "acpi_osi=!Windows 2012"
are found in the cmdline). (LP: #1644771)

  * Fix spelling error in debian/control

 -- Louis Bouchard   Thu, 10 Nov 2016
16:46:39 +0100

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1626269

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  makedumpfile fails to execute if executed on a 4.8 kernel

  [Impact]
  Unable to generate compressed kernel dumps on those platform

  [Fix]
  Backport commits 2c21d4656e8d3c2af2b1e14809d076941ae69e96 and 
  0c9dd01d8ee2e4ec1821a11f5e174fdba56012b8.

  The second commit is required since, once the initial issue is fixed,
  it triggers a second issue fixed on Debian by https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=842019

  [Test Case]
  - Install kernel 4.8 along with the linux-crashdump metapackage
  - Reboot to enable kdump
  - Trigger a kernel panic with "echo c > /proc/sysrq-trigger"

  Without the patch, the following message will appear and makedumpfile
  will fail :

   get_mem_map: Can't distinguish the memory type.

  With the fix, makedumpfile completes correctly.

  [Regression]
  None expected. The modification keeps the initial structure when kernels 
before 4.8 are used.

  [Original description of the problem]

  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@ubuntu:/home/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.8.0-11-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [  

[Group.of.nepali.translators] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

2016-12-08 Thread Launchpad Bug Tracker
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.3

---
makedumpfile (1:1.5.9-5ubuntu0.3) xenial; urgency=medium

  * d/p/0003-PATCH-v2-Support-_count-_refcount-rename-in-struct-p.patch,
d/p/0004-fix-readpage_elf-attempt-to-read-non-existent-page.patch
Fix makedumpfile failure on 4.8 kernels.
 - Makedumpfile will exit on error with the following message :
   get_mem_map: Can't distinguish the memory type. (LP: #1626269)
 - Fix readpage_elf: Attempt to read non-existent page errors after
   previous patch is applied

  [ Rinat ]
  * Fix double-quote handling in /proc/cmdline
Parsing of the cmdline would fail if double-quotes are encountered
in /proc/cmdine (i.e. like when things like "acpi_osi=!Windows 2012"
are found in the cmdline). (LP: #1644771)

  * Fix spelling error in debian/control

 -- Chris J Arges   Wed, 19 Oct 2016 07:41:36
-0500

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1626269

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  makedumpfile fails to execute if executed on a 4.8 kernel

  [Impact]
  Unable to generate compressed kernel dumps on those platform

  [Fix]
  Backport commits 2c21d4656e8d3c2af2b1e14809d076941ae69e96 and 
  0c9dd01d8ee2e4ec1821a11f5e174fdba56012b8.

  The second commit is required since, once the initial issue is fixed,
  it triggers a second issue fixed on Debian by https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=842019

  [Test Case]
  - Install kernel 4.8 along with the linux-crashdump metapackage
  - Reboot to enable kdump
  - Trigger a kernel panic with "echo c > /proc/sysrq-trigger"

  Without the patch, the following message will appear and makedumpfile
  will fail :

   get_mem_map: Can't distinguish the memory type.

  With the fix, makedumpfile completes correctly.

  [Regression]
  None expected. The modification keeps the initial structure when kernels 
before 4.8 are used.

  [Original description of the problem]

  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@ubuntu:/home/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.8.0-11-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50

[Group.of.nepali.translators] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

2016-11-07 Thread Louis Bouchard
** Changed in: makedumpfile (Ubuntu)
   Status: In Progress => Fix Released

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1626269

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  
  root@ubuntu:/home/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.8.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50.733485] REGS: c004f789b990 TRAP: 0300   Not tainted  
(4.8.0-11-generic)
  [   50.733488] MSR: 80009033   CR: 28242422  
XER: 0001
  [   50.733496] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c05b04d8 c004f789bc10 c0f46700 0063 
  GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970 
  GPR08: 0007 0001  0001 
  GPR12: c05af3c0 c7b31200  2200 
  GPR16: 10170dc8 0100111c0538 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 310b9624 0001 c0e9fd40 0004 
  GPR28: c0ea0100 0063 c0e528e8  
  [   50.733536] NIP [c05af3f4] sysrq_handle_crash+0x34/0x50
  [   50.733539] LR [c05b04d8] __handle_sysrq+0xe8/0x280
  [   50.733541] Call Trace:
  [   50.733544] [c004f789bc10] [c09ff9e8] 0xc09ff9e8 
(unreliable)
  [   50.733548] [c004f789bc30] [c05b04d8] __handle_sysrq+0xe8/0x280
  [   50.733552] [c004f789bcd0] [c05b0c88] 
write_sysrq_trigger+0x78/0xa0
  [   50.733556] [c004f789bd00] [c03a9a90] proc_reg_write+0xb0/0x110
  [   50.733560] [c004f789bd50] [c030c27c] __vfs_write+0x6c/0xe0
  [   50.733564] [c004f789bd90] [c030d784] vfs_write+0xd4/0x240
  [   50.733567] [c004f789bde0] [c030f49c] SyS_write+0x6c/0x110
  [   50.733571] [c004f789be30] [c00095e0] system_call+0x38/0x108
  [   50.733574] Instruction dump:
  [   50.733576] 38427340

[Group.of.nepali.translators] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

2016-09-22 Thread Louis Bouchard
Hello,

I can confirm the issue with makedumpfile on amd64. However, the crc32c
module issue does not appear on amd64 and the module is indeed present
in the smaller initrd created for kdump (present in
/var/lib/kdump/initrd.img-4.8.0-11-generic).

I will investigate the makedumpfile issue with 4.8 kernels.

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

** Also affects: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

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

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

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

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1626269

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  
  root@ubuntu:/home/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.8.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50.733485] REGS: c004f789b990 TRAP: 0300   Not tainted  
(4.8.0-11-generic)
  [   50.733488] MSR: 80009033   CR: 28242422  
XER: 0001
  [   50.733496] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c05b04d8 c004f789bc10 c0f46700 0063 
  GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970 
  GPR08: 0007 0001  0001 
  GPR12: c05af3c0 c7b31200  2200 
  GPR16: 10170dc8 0100111c0538 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 310b9624 0001 c0e9fd40 0004 
  GPR28: c0ea0100 0063 c0e528e8  
  [   50.733536] NIP [c05af3f4] sysrq_handle_crash+0x34/0x50
  [   50.733539] LR [c05b04d8] __handle_sysrq+0xe8/0