kernel-packages team mailing list archive

[Launchpad Bug Tracker <1546260@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

== Comment: #0 - Praveen K. Pandey <Praveen.Pandey@xxxxxxxxxx> - 2016-02-04 04:11:48 ==
Hi 

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


Reproducible Step:

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

Expected Result :

Able to generate kdump

Actual Result :

System halt on dump process , seems me having initrd issue

LOG:

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


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

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

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


root@ubuntu:~# echo c > /proc/sysrq-trigger
[  164.495349] sysrq: SysRq : Trigger a crash
[  164.495360] Unable to handle kernel paging request for data at address 0x00000000
[  164.495364] Faulting instruction address: 0xc000000000654db4
[  164.495368] Oops: Kernel access of bad area, sig: 11 [#1]
[  164.495370] SMP NR_CPUS=2048 NUMA pSeries
[  164.495374] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc uas usb_storage pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
[  164.495389] CPU: 0 PID: 1281 Comm: bash Not tainted 4.4.0-2-generic #16-Ubuntu
[  164.495393] task: c0000003f1f2a200 ti: c000000006ef8000 task.ti: c000000006ef8000
[  164.495396] NIP: c000000000654db4 LR: c000000000655e68 CTR: c000000000654d80
[  164.495399] REGS: c000000006efb990 TRAP: 0300   Not tainted  (4.4.0-2-generic)
[  164.495401] MSR: 8000000000009033 <SF,EE,ME,IR,DR,RI,LE>  CR: 28242222  XER: 00000001
[  164.495410] CFAR: c000000000008468 DAR: 0000000000000000 DSISR: 42000000 SOFTE: 1 
GPR00: c000000000655e68 c000000006efbc10 c000000001583800 0000000000000063 
GPR04: c0000003ff609c50 c0000003ff61b4f0 c0000003ffe6c200 000000000000015b 
GPR08: 0000000000000007 0000000000000001 0000000000000000 c0000003ffe72710 
GPR12: c000000000654d80 c000000007ae0000 ffffffffffffffff 0000000022000000 
GPR16: 0000000010170710 000001002c890608 00000000101406f0 00000000100c7100 
GPR20: 0000000000000000 000000001017df98 0000000010140588 0000000000000000 
GPR24: 0000000010153440 000000001017b848 c0000000014c8540 0000000000000004 
GPR28: c0000000014c8900 0000000000000063 c0000000014810bc 0000000000000000 
[  164.495451] NIP [c000000000654db4] sysrq_handle_crash+0x34/0x50
[  164.495454] LR [c000000000655e68] __handle_sysrq+0xe8/0x270
[  164.495456] Call Trace:
[  164.495460] [c000000006efbc10] [c000000000de3008] _fw_tigon_tg3_bin_name+0x2cc30/0x33d18 (unreliable)
[  164.495464] [c000000006efbc30] [c000000000655e68] __handle_sysrq+0xe8/0x270
[  164.495468] [c000000006efbcd0] [c000000000656608] write_sysrq_trigger+0x78/0xa0
[  164.495472] [c000000006efbd00] [c000000000374e70] proc_reg_write+0xb0/0x110
[  164.495476] [c000000006efbd50] [c0000000002dcabc] __vfs_write+0x6c/0xe0
[  164.495480] [c000000006efbd90] [c0000000002dd7f0] vfs_write+0xc0/0x230
[  164.495484] [c000000006efbde0] [c0000000002de82c] SyS_write+0x6c/0x110
[  164.495488] [c000000006efbe30] [c000000000009204] system_call+0x38/0xb4
[  164.495490] Instruction dump:
[  164.495493] 3842ea80 7c0802a6 f8010010 f821ffe1 60000000 60000000 3d220019 394956e4 
[  164.495499] 39200001 912a0000 7c0004ac 39400000 <992a0000> 38210020 e8010010 7c0803a6 
[  164.495506] ---[ end trace 5ddbc181c028cb6c ]---
[  164.497176] 
[  164.497180] Sending IPI

** Affects: kexec-tools (Ubuntu)
     Importance: Undecided
     Assignee: Taco Screen team (taco-screen-team)
         Status: Confirmed


** Tags: architecture-ppc64le bot-comment bugnameltc-136588 severity-critical targetmilestone-inin1604
-- 
kexec/kdump not working in ubuntu 16.04
https://bugs.launchpad.net/bugs/1546260
You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu.