group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #09528
[Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.
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 <louis.bouchard@xxxxxxxxxx> 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 0x00000000
[ 50.733441] Faulting instruction address: 0xc0000000005af3f4
[ 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: c0000004f7906880 task.stack: c0000004f7898000
[ 50.733482] NIP: c0000000005af3f4 LR: c0000000005b04d8 CTR: c0000000005af3c0
[ 50.733485] REGS: c0000004f789b990 TRAP: 0300 Not tainted (4.8.0-11-generic)
[ 50.733488] MSR: 8000000000009033 <SF,EE,ME,IR,DR,RI,LE> CR: 28242422 XER: 00000001
[ 50.733496] CFAR: c0000000000087d0 DAR: 0000000000000000 DSISR: 42000000 SOFTE: 1
GPR00: c0000000005b04d8 c0000004f789bc10 c000000000f46700 0000000000000063
GPR04: c0000005ef78a9b8 c0000005ef79f7d8 c00000063fe82300 0000000000005970
GPR08: 0000000000000007 0000000000000001 0000000000000000 0000000000000001
GPR12: c0000000005af3c0 c000000007b31200 ffffffffffffffff 0000000022000000
GPR16: 0000000010170dc8 00000100111c0538 0000000010140f58 00000000100c7570
GPR20: 0000000000000000 000000001017dd58 0000000010153618 000000001017b608
GPR24: 00003ffff10b9624 0000000000000001 c000000000e9fd40 0000000000000004
GPR28: c000000000ea0100 0000000000000063 c000000000e528e8 0000000000000000
[ 50.733536] NIP [c0000000005af3f4] sysrq_handle_crash+0x34/0x50
[ 50.733539] LR [c0000000005b04d8] __handle_sysrq+0xe8/0x280
[ 50.733541] Call Trace:
[ 50.733544] [c0000004f789bc10] [c0000000009ff9e8] 0xc0000000009ff9e8 (unreliable)
[ 50.733548] [c0000004f789bc30] [c0000000005b04d8] __handle_sysrq+0xe8/0x280
[ 50.733552] [c0000004f789bcd0] [c0000000005b0c88] write_sysrq_trigger+0x78/0xa0
[ 50.733556] [c0000004f789bd00] [c0000000003a9a90] proc_reg_write+0xb0/0x110
[ 50.733560] [c0000004f789bd50] [c00000000030c27c] __vfs_write+0x6c/0xe0
[ 50.733564] [c0000004f789bd90] [c00000000030d784] vfs_write+0xd4/0x240
[ 50.733567] [c0000004f789bde0] [c00000000030f49c] SyS_write+0x6c/0x110
[ 50.733571] [c0000004f789be30] [c0000000000095e0] system_call+0x38/0x108
[ 50.733574] Instruction dump:
[ 50.733576] 38427340 7c0802a6 f8010010 f821ffe1 60000000 60000000 3d220019 3949cde0
[ 50.733582] 39200001 912a0000 7c0004ac 39400000 <992a0000> 38210020 e8010010 7c0803a6
[ 50.733589] ---[ end trace f58d72cacaada0df ]---
[ 50.735307]
[ 50.735313] Sending IPI to other CPUs
[ 50.736336] IPI complete
I'm in purgatory
-> smp_release_cpus()
spinning_secondaries = 8
<- smp_release_cpus()
[ 7.250999] sd 0:0:1:0: [sda] Assuming drive cache: write through
/dev/sda2: recovering journal
/dev/sda2: clean, 139510/1884160 files, 1253112/7531008 blocks
[ 8.263985] EXT4-fs (sda2): Cannot load crc32c driver.
mount: mounting /dev/sda2 on /root failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /run on /root/run failed: No such file or directory
run-init: current directory on the same filesystem as the root: error 0
Target filesystem doesn't have requested /sbin/init.
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
run-init: current directory on the same filesystem as the root: error 0
No init found. Try passing init= bootarg.
BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
(initramfs)
(initramfs)
(initramfs) exit
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
/init: line 338: can't open /root/dev/console: no such file
[ 381.386973] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 381.386973]
[ 381.386980] CPU: 0 PID: 1 Comm: init Not tainted 4.8.0-11-generic #12-Ubuntu
[ 381.386983] Call Trace:
[ 381.386988] [c000000026513c20] [c00000000888bb9c] dump_stack+0xb0/0xf0 (unreliable)
[ 381.386993] [c000000026513c60] [c00000000888832c] panic+0x144/0x308
[ 381.386997] [c000000026513cf0] [c0000000080ce298] do_exit+0xd08/0xd10
[ 381.387001] [c000000026513dc0] [c0000000080ce384] do_group_exit+0x64/0x100
[ 381.387005] [c000000026513e00] [c0000000080ce44c] SyS_exit_group+0x2c/0x30
[ 381.387008] [c000000026513e30] [c0000000080095e0] system_call+0x38/0x108
[ 381.390557] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 381.390557]
== Comment: #5 - Kevin W. Rudd - 2016-09-21 16:26:35 ==
This appears to be similar to the issue noted in the following discussion:
https://lists.debian.org/debian-kernel/2016/04/msg00013.html
(from the kdump dmesg info attached):
[ 9.115577] call_modprobe: crypto-crc32c 2
[ 9.116170] call_modprobe: crypto-crc32c-all 2
[ 9.116709] EXT4-fs (sda2): Cannot load crc32c driver.
Forcing the crc32c module by adding it to /etc/initramfs-tools/modules
got me past the initial EXT4-fs failure, but kdump then ran into a
regression with makedumpfile:
[ 12.331294] kdump-tools[1546]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201609211609/dump-incomplete
[ 12.391902] kdump-tools[1546]: get_mem_map: Can't distinguish the memory type.
[ 12.392406] kdump-tools[1546]: The kernel version is not supported.
[ 12.392715] kdump-tools[1546]: The makedumpfile operation may be incomplete.
[ 12.392997] kdump-tools[1546]: makedumpfile Failed.
[ 12.393309] kdump-tools[1546]: * kdump-tools: makedumpfile failed, falling back to 'cp'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1626269/+subscriptions
