Bug 813778

Summary: kdump hangs on dual Xeon E5530
Product: Red Hat Enterprise Linux 5 Reporter: alonph
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED WONTFIX QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.9CC: alonph, pm-rhel
Target Milestone: rc   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-03 12:25:59 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:

Description alonph 2012-04-18 12:20:57 UTC
Description of problem:
I have a dual Xeon E5520.
When I enable kdump, on crash the machine tries to boot the second kernel.
The second kernel starts booting but it hangs right after the line:
Kernel command line: ro pci=noacpi earlyprintk=serial,ttyS0,9600n8 root=/dev/mapper/vg_splat-lv_current vmalloc=256M panic=15 console=ttyS0 3 quiet  irqpoll maxcpus=1 memmap=exactmap memmap=640K@0K mK...

NOTE:
If I add to the first kernel the noapic flag the problem disappears.


Version-Release number of selected component (if applicable):
I am using:
kernel-2.6.18-92
kexec-tools-1.101-194
cmdline:
ro pci=noacpi earlyprintk=serial,ttyS0,9600n8 root=/dev/mapper/vg_splat-lv_current vmalloc=256M panic=15 console=ttyS0 3 quiet 

How reproducible:
Always

Steps to Reproduce:
1.enable kdump
2.echo c > /proc/sysreq-trigger
  
Actual results:
Hang

Expected results:
Reboot + vmcore created

Additional info:

SysRq : Trigger a crashdump

I'm in purgatory
Linux version 2.6.18-92 (xxx.com) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #8 SMP Mon Apr 16 09:39:46 IDT 2012
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000100 - 000000000009d800 (usable)
 BIOS-e820: 000000000009d800 - 00000000000a0000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bf7b0000 (usable)
 BIOS-e820: 00000000bf7b0000 - 00000000bf7be000 (ACPI data)
 BIOS-e820: 00000000bf7be000 - 00000000bf7d0000 (ACPI NVS)
 BIOS-e820: 00000000bf7d0000 - 00000000bf7e0000 (reserved)
 BIOS-e820: 00000000bf7ec000 - 00000000c0000000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffc00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 00000001c0000000 (usable)
user-defined physical RAM map:
 user: 0000000000000000 - 00000000000a0000 (usable)
 user: 0000000001000000 - 00000000014f1000 (usable)
 user: 0000000001591400 - 0000000005000000 (usable)
early console enabled
0MB HIGHMEM available.
80MB LOWMEM available.
found SMP MP-table at 000ff780
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
disabling kdump
NX (Execute Disable) protection: active
DMI present.
Using APIC driver default
  >>> ERROR: Invalid checksum
ACPI: PM-Timer IO Port: 0x808
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 7:10 APIC version 21
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Processor #2 7:10 APIC version 21
WARNING: maxcpus limit of 1 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
Processor #4 7:10 APIC version 21
WARNING: maxcpus limit of 1 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
Processor #6 7:10 APIC version 21
WARNING: maxcpus limit of 1 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x10] enabled)
Processor #16 7:10 APIC version 21
WARNING: maxcpus limit of 1 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x12] enabled)
Processor #18 7:10 APIC version 21
WARNING: maxcpus limit of 1 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x14] enabled)
Processor #20 7:10 APIC version 21
WARNING: maxcpus limit of 1 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x16] enabled)
Processor #22 7:10 APIC version 21
WARNING: maxcpus limit of 1 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled)
ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled)
ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled)
ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled)
ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x8c] disabled)
ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x8d] disabled)
ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x8e] disabled)
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x8f] disabled)
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x90] disabled)
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x91] disabled)
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x92] disabled)
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x93] disabled)
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x94] disabled)
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x95] disabled)
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x96] disabled)
ACPI: LAPIC (acpi_id[0x18] lapic_id[0x97] disabled)
Using ACPI for processor (LAPIC) configuration information
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: INTEL    Product ID: TYLERSBURG   APIC at: 0xFEE00000
I/O APIC #8 Version 32 at 0xFEC00000.
I/O APIC #9 Version 32 at 0xFEC8A000.
Enabling APIC mode:  Flat.  Using 2 I/O APICs
Processors: 1
Allocating PCI resources starting at 10000000 (gap: 05000000:fb000000)
Detected 2400.162 MHz processor.
Built 1 zonelists.  Total pages: 20480
Kernel command line: earlyprintk=serial,ttyS0,9600n8 ro pci=noacpi root=/dev/mapper/vg_splat-lv_current vmalloc=256M panic=15 console=ttyS0 3 quiet  irqpoll maxcpus=1 memmap=exactmap memmap=640K@0K memmap=5060K@16384K memmap=59835K@22085K elfcorehdr=22084K
Got stcuk here


Can BZ 462519 is related?
I can not access it. (Access denied)
Can you direct me to a patch for this issue.

Thanks in advance.

Comment 1 alonph 2012-04-19 15:26:03 UTC
I have also added some printouts and the second kernel get's stuck in
calibrate_delay.

Comment 3 RHEL Program Management 2014-03-07 13:35:37 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 4 RHEL Program Management 2014-06-03 12:25:59 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).