Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

[Gaëtan Trellu]

I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

kdump-tools 1:1.5.9-5ubuntu0.4
makedumpfile 1:1.5.9-5ubuntu0.4
linux-image-4.8.0-46-generic 4.8.0-46.49~16.04.1

# kdump-config show

DUMP_MODE: kdump
USE_KDUMP: 1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR: /var/crash
crashkernel addr: 0x2b000000
   /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
kdump initrd:
   /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic
current state: ready to kdump

kexec command:
  /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

The kernel trace

[ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0000000000000088
[ 10.740946] IP: [<ffffffff88e1afc2>] hswep_uncore_cpu_init+0x52/0xa0
[ 10.743571] PGD 0
[ 10.744482] Oops: 0000 [#1] SMP
[ 10.745615] Modules linked in:
[ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu
[ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
[ 10.752574] task: ffff8f16b2938ec0 task.stack: ffff8f16b2940000
[ 10.754892] RIP: 0010:[<ffffffff88e1afc2>] [<ffffffff88e1afc2>] hswep_uncore_cpu_init+0x52/0xa0
[ 10.758371] RSP: 0018:ffff8f16b2943e40 EFLAGS: 00010206
[ 10.760337] RAX: 0000000000000050 RBX: 0000000000000000 RCX: 000000000000238a
[ 10.762787] RDX: ffff8f16b01f47e0 RSI: ffff8f16b2c1c700 RDI: 0000000000000000
[ 10.765289] RBP: ffff8f16b2943e50 R08: 000000000001c700 R09: ffffffff89231a97
[ 10.767968] R10: ffffea0000c07000 R11: 0000000000000000 R12: ffffffff89c1a030
[ 10.770399] R13: ffffffff89ea7760 R14: ffffffff89c0daf8 R15: ffff8f16b2c19300
[ 10.772894] FS: 0000000000000000(0000) GS:ffff8f16b2c00000(0000) knlGS:0000000000000000
[ 10.775945] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 10.777935] CR2: 0000000000000088 CR3: 000000002d806000 CR4: 00000000001406f0
[ 10.780398] Stack:
[ 10.781154] ffff8f16b2943e50 00000000df388e ffff8f16b2943e88 ffffffff89d8b292
[ 10.884602] 0000000000000000 0000000000000105 ffffffff89d8b196 ffffffff89c0daf8
[ 10.887394] ffff8f16b2c19300 ffff8f16b2943f08 ffffffff88e02190 ffffffff88ea377f
[ 10.890699] Call Trace:
[ 10.891596] [<ffffffff89d8b292>] intel_uncore_init+0xfc/0x2d6
[ 10.893587] [<f? uncore_type_init+0x15f/0x15f
[ 11.395474] [<ffffffff88e02190>] do_one_initcall+0x50/0x1a0
[ 11.397431] [<ffffffff88ea377f>] ? parse_args+0x2cf/0x490
[ 11.399313] [<ffffffff89d86175>] kernel_init_freeable+0x178/0x217
[ 11.402112] [<ffffffff8968d2ce>] kernel_init+0xe/0x100
[ 11.404013] [<ffffffff8969aa1f>] ret_from_fork+0x1f/0x40
[ 11.405895] [<ffffffff8968d2c0>] ? rest_init+0x80/0x80
[ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
[ 11.422367] RIP [<ffffffff88e1afc2>] hswep_uncore_cpu_init+0x52/0xa0
[ 11.425174] RSP <ffff8f16b2943e40>
[ 11.426588] CR2: 0000000000000088
[ 11.427978] ---[ end trace d8adbfe4355f5160 ]---
[ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[ 11.430006]
[ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[ 11.433354]

Please find the full kernel trace

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Louis Bouchard (louis)]

Re-targetting the bug to the linux kernel as this is not a makedumpfile issue

[Gaëtan Trellu (goldyfruit)]

@Louis, thanks.

[Joseph Salisbury (jsalisbury)]

I built a Xenial test kernel with a pick of commit 6d6daa20945f. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1687779/

Can you test this kernel and see if it resolves this bug?

[Gaëtan Trellu (goldyfruit)]

I'm able to boot this OS with this kernel I got a kernel panic.

[Joseph Salisbury (jsalisbury)]

So you still hit the bug with the test kernel posted in comment #6?

[Gaëtan Trellu (goldyfruit)]

I'm even not able to boot the operating system with the kernel in comment #6.

[Joseph Salisbury (jsalisbury)]

Hmm, I just tried to boot that kernel and it came up fine. Can you post a screen shot or digital picture of the error you are getting?

[Gaëtan Trellu (goldyfruit)]

Sorry for the late answer.
Please find the log in attachment.

[Joseph Salisbury (jsalisbury)]

I built a v2 of the test kernel. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1687779/

Can you test this kernel and see if it resolves this bug?

[Gaëtan Trellu (goldyfruit)]

Same issue.

[Gaëtan Trellu (goldyfruit)]

Do you have an update about this bug ?

[Joseph Salisbury (jsalisbury)]

Yakkety is actually going to be EOL this week. It might be best to see if this bug exists in current and newer releases. Do you know if this bug happens with the Zesty kernel?

[Gaëtan Trellu (goldyfruit)]

@Joseph, I don't know, we are just using the Ubuntu LTS versions.
You point is valid, maybe it's better to check if Zesty has this issue.

Thanks for the follow up!

[Andy Whitcroft (apw)]

This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]