------- Comment From [email protected] 2017-09-14 01:58 EDT------- Increased the crashkernel to 512MB and triggered crash. Console logs shows multipath: error getting device. But I see dump is collected under /var/crash
I'm in purgatory -> smp_release_cpus() spinning_secondaries = 47 <- smp_release_cpus() [ 0.184883] pci 002b:50:00.0: of_irq_parse_pci() failed with rc=-22 /dev/sdc2: recovering journal /dev/sdc2: clean, 88120/2514944 files, 892667/10046464 blocks [ 11.676763] device-mapper: table: 253:2: multipath: error getting device [ 11.689487] device-mapper: table: 253:2: multipath: error getting device Complete console log is below: root@talclp3:~# dmesg | grep crash [ 0.000000] Reserving 512MB of memory at 32MB for crashkernel (System RAM: 6144MB) [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinux-4.8.0-59-generic root=UUID=30629c5d-7ff0-48db-b2ca-7c2255d0fa18 ro splash quiet crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M maxcpus=1 root@talclp3:/var/crash# echo c > /proc/sysrq-trigger [ 93.923245] sysrq: SysRq : Trigger a crash [ 93.923263] Unable to handle kernel paging request for data at address 0x00000000 [ 93.923266] Faulting instruction address: 0xc0000000006a2428 [ 93.923269] Oops: Kernel access of bad area, sig: 11 [#1] [ 93.923271] SMP NR_CPUS=2048 NUMA pSeries [ 93.923275] Modules linked in: nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) mlx4_ib(OE) pseries_rng ib_core(OE) vmx_crypto binfmt_misc dm_round_robin sunrpc knem(OE) dm_multipath ip_tables x_tables autofs4 btrfs xor raid6_pq mlx4_en(OE) ibmvfc scsi_transport_fc ibmvscsi bnx2x mlx4_core(OE) devlink mlx_compat(OE) mdio libcrc32c be2net crc32c_vpmsum [ 93.923307] CPU: 0 PID: 2665 Comm: bash Tainted: G OE 4.8.0-59-generic #64-Ubuntu [ 93.923310] task: c0000000b3a5ce00 task.stack: c0000000b6c08000 [ 93.923313] NIP: c0000000006a2428 LR: c0000000006a3478 CTR: c0000000006a2400 [ 93.923316] REGS: c0000000b6c0b9f0 TRAP: 0300 Tainted: G OE (4.8.0-59-generic) [ 93.923318] MSR: 8000000000009033 <SF,EE,ME,IR,DR,RI,LE> CR: 28222222 XER: 00000001 [ 93.923326] CFAR: c000000000008750 DAR: 0000000000000000 DSISR: 42000000 SOFTE: 1 GPR00: c0000000006a3478 c0000000b6c0bc70 c000000001467500 0000000000000063 GPR04: c0000000bd00aca0 c0000000bd01fb40 c00000017fd2e300 000000000000b040 GPR08: 0000000000000007 0000000000000001 0000000000000000 0000000000000001 GPR12: c0000000006a2400 c000000001b30000 0000000000000000 0000000022000000 GPR16: 0000000010170dc8 0000010033a96e18 0000000010140528 00000000100c6f60 GPR20: 0000000000000000 000000001017dd58 0000000010152bf0 000000001017b608 GPR24: 00003ffff7d5f954 00003ffff7d5f950 c00000000137e6e0 0000000000000004 GPR28: c00000000137eaa0 0000000000000063 c000000001332590 0000000000000000 [ 93.923365] NIP [c0000000006a2428] sysrq_handle_crash+0x28/0x30 [ 93.923368] LR [c0000000006a3478] __handle_sysrq+0xe8/0x280 [ 93.923370] Call Trace: [ 93.923372] [c0000000b6c0bc70] [c0000000006a3458] __handle_sysrq+0xc8/0x280 (unreliable) [ 93.923376] [c0000000b6c0bd10] [c0000000006a3bcc] write_sysrq_trigger+0x6c/0x90 [ 93.923380] [c0000000b6c0bd40] [c0000000003adb48] proc_reg_write+0x88/0xd0 [ 93.923384] [c0000000b6c0bd70] [c0000000003105ac] __vfs_write+0x3c/0x70 [ 93.923387] [c0000000b6c0bd90] [c000000000311814] vfs_write+0xd4/0x240 [ 93.923390] [c0000000b6c0bde0] [c000000000313368] SyS_write+0x68/0x110 [ 93.923394] [c0000000b6c0be30] [c000000000009584] system_call+0x38/0xec [ 93.923396] Instruction dump: [ 93.923398] 60000000 60000000 3c4c00dc 38425100 7c0802a6 60000000 3d22001a 3949bc60 [ 93.923404] 39200001 912a0000 7c0004ac 39400000 <992a0000> 4e800020 3c4c00dc 384250d0 [ 93.923411] ---[ end trace b285782082a8e490 ]--- [ 93.926214] [ 93.926226] Sending IPI to other CPUs [ 93.926229] IPI complete I'm in purgatory -> smp_release_cpus() spinning_secondaries = 47 <- smp_release_cpus() [ 0.184883] pci 002b:50:00.0: of_irq_parse_pci() failed with rc=-22 /dev/sdc2: recovering journal /dev/sdc2: clean, 88120/2514944 files, 892667/10046464 blocks [ 11.676763] device-mapper: table: 253:2: multipath: error getting device [ 11.689487] device-mapper: table: 253:2: multipath: error getting device root@talclp3:/var/crash# ls 201709140049 kexec_cmd linux-image-4.8.0-59-generic-201709140049.crash root@talclp3:/var/crash# ls 201709140049/ dmesg.201709140049 dump.201709140049 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu16.10:talclp1: Kdump failed with multipath disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1635597/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
