Bug 815785
| Summary: | kdump fails with lapic error in xen hvm guest | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Qixiang Wan <qwan> | ||||||
| Component: | kernel | Assignee: | Don Zickus <dzickus> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.3 | CC: | drjones, kzhang, leiwang, moli, qguan, yuzhou | ||||||
| Target Milestone: | rc | Keywords: | Regression, TestBlocker | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | xen | ||||||||
| Fixed In Version: | kernel-2.6.32-269.el6 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-06-20 13:59:07 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 653816 | ||||||||
| Attachments: |
|
||||||||
|
Description
Qixiang Wan
2012-04-24 13:56:58 UTC
Created attachment 579867 [details]
second kernel call trace with LAPIC error
This error is more reproducible if trigger the crash while scping data from guest
Created attachment 579868 [details]
second kernel call trace and continue, then reboot after "lost interrupt" error
Guest has a chance (if don't scp data from guest when trigger the crash) to continue boot after the call trace, but it will reboot after "lost interrupt" error later.
I've started a brew build here https://brewweb.devel.redhat.com/taskinfo?taskID=4334583 that has 0a267f9 reverted for testing. (In reply to comment #3) > I've started a brew build here > > https://brewweb.devel.redhat.com/taskinfo?taskID=4334583 > > that has 0a267f9 reverted for testing. Tested this build, kdump works well without any call trace. Thanks for the testing qwan! I'll start chatting with dzickus about this. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This brew build has the patch (hack) below to try and keep 0a267f9 https://brewweb.devel.redhat.com/taskinfo?taskID=4336690 I'm not sure if we want to do this, but I guess we can test it to see if it even works for starters. diff --git a/arch/x86/kernel/crash.c b/arch/x86/kernel/crash.c index c1b0780..1ec6287 100644 --- a/arch/x86/kernel/crash.c +++ b/arch/x86/kernel/crash.c @@ -30,6 +30,8 @@ #include <asm/virtext.h> #include <asm/iommu.h> +#include <xen/xen.h> + int in_crash_kexec; @@ -103,6 +105,10 @@ void native_machine_crash_shutdown(struct pt_regs *regs) cpu_emergency_svm_disable(); lapic_shutdown(); +#if defined(CONFIG_X86_IO_APIC) + if (xen_hvm_domain()) + disable_IO_APIC(); +#endif if (mcp55_rewrite) { u32 cfg; printk(KERN_CRIT "REWRITING MCP55 CFG REG\n"); (In reply to comment #7) > This brew build has the patch (hack) below to try and keep 0a267f9 > > https://brewweb.devel.redhat.com/taskinfo?taskID=4336690 > > I'm not sure if we want to do this, but I guess we can test it to see if it > even works for starters. It works in the same environment. Don posted a 'revert 0a267f9' patch with under this BZ, so kicking it to POST. He'll revisit the issue for 6.4. Patch(es) available on kernel-2.6.32-269.el6 Verified with kernel-2.6.32-269.el6. With this build, kdump service can start successfully and works well in xen HVM guest. The latest build contains the following fixes: Bug 810222 - Revert "[virt] xen: mask MTRR feature from guest BZ#750758" (fix in -262) Bug 811815 - [FJ6.2 Bug]: kdump service fails with the message "Kdump is unsupported on this kernel" (fix in -266) Bug 815785 - kdump fails with lapic error in xen hvm guest (fix in -269). With all of the above three fixes integrated, kdump in RHEL6.3 xen hvm guest works well now. So verify these 3 bugs together. Test steps: [1] Add the kernel command line parameter xen_emul_unplug=never to the kernel's command line and boot. [2] Start the kdump service. [3] Blacklist the drivers used for xen emulated device by adding the following tree lines to /etc/modprobe.d/blacklist.conf: blacklist ata_piix blacklist 8139too blacklist 8139cp [4] Remove the xen_emul_unplug=never kernel command line parameter added in step 1 and add the kernel command line xen_emul_unplug=unnecessary, then reboot. [5] Ensure that the kdump service has started. [6] Run echo c >/proc/sysrq-trigger to force a crash that should invoke kdump Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0862.html |