[Kernel-packages] [Bug 1626269] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2016-11-06 22:53 EDT--- *** Bug 147804 has been marked as a duplicate of this bug. *** -- 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/1626269 Title: Ubuntu 16.10: kdump is not working in 4.8 kernel. Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Confirmed 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/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 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 3949cde0 [ 50.733582] 3921 912a 7c0004ac 3940 <992a> 38210020 e8010010 7c0803a6 [
[Kernel-packages] [Bug 1626269] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2016-10-27 02:54 EDT--- (In reply to comment #42) > Hopefully, we should get an ACK for the upstream bug soon, so I can push a > new package to Debian. I will then proceed with the synchronization to Zesty > and SRU to the other stable releases. > > I hope that this clarifies the situation. > Thanks for clarifying that, Louis. That does help in appreciating the situation.. Regards, Hari -- 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/1626269 Title: Ubuntu 16.10: kdump is not working in 4.8 kernel. Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Confirmed 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/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/0x1
[Kernel-packages] [Bug 1626269] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2016-10-20 15:21 EDT--- (In reply to comment #38) > > Hello, Hello Loius, > > Not at the moment : simply adding this commit allow makedumpfile to run but > it generates many other error messages that are currently investigated. I couldn't reproduce it on powerpc. I tried on Ubuntu's 4.8.0-15 & 4.8.0-22 kernels. Maybe arch specific - in which case, it would be good to get an update for makedumpfile package with this fix first? Thanks Hari -- 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/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/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] [c004f789bd
[Kernel-packages] [Bug 1626269] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2016-10-19 14:44 EDT--- (In reply to comment #19) > Hello, > > Yes I have found that and included it into the upcoming makedumpfile > package. But there are more issues wollowing the addition of this commit > that I need to identify and fix. > > http://lists.infradead.org/pipermail/kexec/2016-September/017300.html Hi Louis, Any ETA for the updated makedumpfile package with fix commit 2c21d4656e8d3c2af2b1e14809d076941ae69e96 Thanks Hari -- 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/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/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]
[Kernel-packages] [Bug 1626269] Comment bridged from LTC Bugzilla
--- Comment From pavra...@in.ibm.com 2016-09-28 02:21 EDT--- Hi, Tested with "4.8.0-17-generic" kernel. After crash machine did not hang and 7.6G vmcore got captured. but dmesg.201609270619 is not generated. Logs === root@ubuntu:/var/crash/201609270619# uname -a Linux ubuntu 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu:/var/crash/201609270619# ls -lhrt total 2.0G -r 1 root root 7.6G Sep 27 06:20 vmcore.201609270619 # makedumpfile -l -d 31 /var/crash/201609270619/vmcore.201609270619 dump1 The kernel version is not supported. The makedumpfile operation may be incomplete. get_mem_map: Can't distinguish the memory type. makedumpfile Failed. With given makedump file # ./makedumpfile -l -d 31 /var/crash/201609270619/vmcore.201609270619 dump1 The kernel version is not supported. The makedumpfile operation may be incomplete. Copying data : [100.0 %] - The dumpfile is saved to dump1. makedumpfile Completed. -- 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/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+0x
[Kernel-packages] [Bug 1626269] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2016-09-24 08:25 EDT--- Dump filtering for kernels v4.7+ is failing because of kernel commit 0139aa7b7fa1 which changed _count to _refcount in struct page. The below makedumpfile tool commit fixes this: commit 2c21d4656e8d3c2af2b1e14809d076941ae69e96 Author: Vitaly Kuznetsov Date: Fri Jun 17 18:41:26 2016 +0900 [PATCH v2] Support _count -> _refcount rename in struct page _count member was renamed to _refcount in linux commit 0139aa7b7fa12 ("mm: rename _count, field of the struct page, to _refcount") and this broke makedumpfile. The reason for making the change was to find all users accessing it directly and not through the recommended API. I tried suggesting to revert the change but failed, I see no other choice than to start supporting both _count and _refcount in makedumpfile. Signed-off-by: Vitaly Kuznetsov -- Makedumpfile filtered dump successfully when the above commit is applied on top of makedumpfile_1.6.0-2 # ./makedumpfile -l -d 31 /var/crash/201609230347/vmcore.201609230347 dump The kernel version is not supported. The makedumpfile operation may be incomplete. Copying data : [100.0 %] / The dumpfile is saved to dump. makedumpfile Completed. # -- Thanks Hari -- 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/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 000
[Kernel-packages] [Bug 1626269] Comment bridged from LTC Bugzilla
--- Comment From ru...@us.ibm.com 2016-09-23 13:47 EDT--- We are still seeing the crc32c issue with the 4.8.0-15, so I mirrored over a related bug to keep the two issues separate. The crc32c issue is being tracked in Bug 146645 / LP Bug 1627126 -- 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/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/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 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019
[Kernel-packages] [Bug 1626269] Comment bridged from LTC Bugzilla
--- Comment From ru...@us.ibm.com 2016-09-22 09:12 EDT--- Hi Louis. We are getting other bug reports against the missing crc32c module for ppc64le. Would it be better to open up a different LP for that specific issue to keep the missing module and makedumpfile issues separate? -- 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/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/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 7c0802a6 f8010010 f82