[Kernel-packages] [Bug 1771537] [NEW] Kexec -p Seems load kernel failed, and doesn't reboot after a panic
Public bug reported: After install linux-crashdump, everything seems successfully. But when I trigger an panic over: echo c > /proc/sysrq-trigger , kernel panics and hungs, and doesn't reboot. even if i do the following: echo 10 > /proc/sys/kernel/panic And it is reproducible on my system. Here is my system information: rs@ubuntuDev$ uname -a Linux ubuntuDev 3.19.0-80-generic #88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux And it is the lsb info: rs@ubuntuDev$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty rs@ubuntuDev$ Here is result of kdump-config show before i trigger an panic: rs@ubuntuDev$ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2d00 current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic rs@ubuntuDev$ And I have successfully solved this problem by these steps after the above kdump-config show: 1: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic 2: echo c > /proc/sysrq-trigger And this time, system successfully rebooted into the secondary kernel whiout crashkernel param, and the vmcore is dumpped successfully. So, It seems we should strip out the BOOT_IMAGE string from result of `cat /proc/cmdline`. As a result, we need change kdump-config script from: # Assemble the --commmand-line: if [ -z "$KDUMP_CMDLINE" ] ; then KDUMP_CMDLINE=`cat /proc/cmdline | \ sed -r -e 's/(^| )crashkernel=[^ ]*//g' \ -e 's/(^| )hugepages=[^ ]*//g' \ -e 's/(^| )hugepagesz=[^ ]*//g' \ -e 's/(^| )abm=[^ ]*//g'` fi into: # Assemble the --commmand-line: if [ -z "$KDUMP_CMDLINE" ] ; then KDUMP_CMDLINE=`cat /proc/cmdline | \ sed -r -e 's/(^| )crashkernel=[^ ]*//g' \ -e 's/(^| )hugepages=[^ ]*//g' \ -e 's/(^| )hugepagesz=[^ ]*//g' \ -e 's/(^| )abm=[^ ]*//g'` \ -e 's/(^| )BOOT_IMAGE=[^ ]*//g' fi Could you guys re-check this bug? I can provide other information with pleasure, if needed. ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1771537 Title: Kexec -p Seems load kernel failed, and doesn't reboot after a panic Status in kexec-tools package in Ubuntu: New Bug description: After install linux-crashdump, everything seems successfully. But when I trigger an panic over: echo c > /proc/sysrq-trigger , kernel panics and hungs, and doesn't reboot. even if i do the following: echo 10 > /proc/sys/kernel/panic And it is reproducible on my system. Here is my system information: rs@ubuntuDev$ uname -a Linux ubuntuDev 3.19.0-80-generic #88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux And it is the lsb info: rs@ubuntuDev$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty rs@ubuntuDev$ Here is result of kdump-config show before i trigger an panic: rs@ubuntuDev$ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2d00 current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic rs@ubuntuDev$ And I have successfully solved this problem by these steps after the above kdump-config show: 1: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic 2: echo c > /proc/sysrq-trigger And this time, system successfully rebooted into the secondary kernel whiout crashkernel param, and the vmcore is dumpped successfully. So, It seems we should strip out the BOOT_IMAGE string from result
[Kernel-packages] [Bug 1771546] [NEW] WARNING: setup_local_APIC+0x27f/0x340
Public bug reported: when load kernel with kexec: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic and then, triggers a panic: echo c > /proc/sysrq-trigger and now we got reboot into secondary kernel, but at this process, we will got this call trace with 100% reproducible: [14257.863168] Initializing cgroup subsys net_prio [14257.864506] Initializing cgroup subsys hugetlb [14257.865898] CPU: Physical Processor ID: 0 [14257.867035] CPU: Processor Core ID: 0 [14257.869296] mce: CPU supports 0 MCE banks [14257.870495] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [14257.870495] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [14257.901734] ftrace: allocating 30063 entries in 118 pages [14258.976524] [ cut here ] [14258.983143] WARNING: CPU: 0 PID: 1 at /build/linux-lts-vivid-PmeBs4/linux-lts-vivid-3.19.0/arch/x86/kernel/apic/apic.c:1400 setup_local_APIC+0x27f/0x340() [14259.005863] Modules linked in: [14259.009221] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-80-generic #88~14.04.1-Ubuntu [14259.015315] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [14259.021134] 88003191fe18 817b63c3 [14259.036605] 81a8b9d0 88003191fe58 81075d6a 88003191fdfc [14259.055284] 0001 00f0 [14259.061414] Call Trace: [14259.063414] [] dump_stack+0x63/0x81 [14259.067742] [] warn_slowpath_common+0x8a/0xc0 [14259.076934] [] warn_slowpath_null+0x1a/0x20 [14259.085878] [] setup_local_APIC+0x27f/0x340 [14259.101292] [] native_smp_prepare_cpus+0x2f2/0x3af [14259.111873] [] kernel_init_freeable+0xaf/0x1f9 [14259.114495] [] ? rest_init+0x80/0x80 [14259.116783] [] kernel_init+0xe/0xf0 [14259.118990] [] ret_from_fork+0x58/0x90 [14259.121292] [] ? rest_init+0x80/0x80 [14259.123341] ---[ end trace 7384fc8d5897e3f0 ]--- [14259.130738] Spurious LAPIC timer interrupt on cpu 0 [14259.153429] do_IRQ: 0.145 No irq handler for vector (irq -1) [14259.157634] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [14259.161002] smpboot: CPU0: Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (fam: 06, model: 4e, stepping: 03) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771546 Title: WARNING: setup_local_APIC+0x27f/0x340 Status in linux package in Ubuntu: New Bug description: when load kernel with kexec: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic and then, triggers a panic: echo c > /proc/sysrq-trigger and now we got reboot into secondary kernel, but at this process, we will got this call trace with 100% reproducible: [14257.863168] Initializing cgroup subsys net_prio [14257.864506] Initializing cgroup subsys hugetlb [14257.865898] CPU: Physical Processor ID: 0 [14257.867035] CPU: Processor Core ID: 0 [14257.869296] mce: CPU supports 0 MCE banks [14257.870495] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [14257.870495] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [14257.901734] ftrace: allocating 30063 entries in 118 pages [14258.976524] [ cut here ] [14258.983143] WARNING: CPU: 0 PID: 1 at /build/linux-lts-vivid-PmeBs4/linux-lts-vivid-3.19.0/arch/x86/kernel/apic/apic.c:1400 setup_local_APIC+0x27f/0x340() [14259.005863] Modules linked in: [14259.009221] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-80-generic #88~14.04.1-Ubuntu [14259.015315] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [14259.021134] 88003191fe18 817b63c3 [14259.036605] 81a8b9d0 88003191fe58 81075d6a 88003191fdfc [14259.055284] 0001 00f0 [14259.061414] Call Trace: [14259.063414] [] dump_stack+0x63/0x81 [14259.067742] [] warn_slowpath_common+0x8a/0xc0 [14259.076934] [] warn_slowpath_null+0x1a/0x20 [14259.085878] [] setup_local_APIC+0x27f/0x340 [14259.101292] [] native_smp_prepare_cpus+0x2f2/0x3af [14259.111873] [] kernel_init_freeable+0xaf/0x1f9 [14259.114495] [] ? rest_init+0x80/0x80 [14259.116783] [] kernel_init+0xe/0xf0 [14259.118990] [] ret_from_fork+0x58/0x90 [14259.121292] [] ? rest_init+0x80/0x80 [14259.123341] ---[ end trace 7384fc8d5897e3f0 ]--- [14259.130738] Spurious LAPIC timer interrupt on cpu 0 [14259.153429] do_IRQ: 0.145 No irq handler for
