Re: 2.6.25-rc1 panics on boot
On Thu, Feb 14, 2008 at 12:06:31PM +0530, Dhaval Giani wrote: > On Wed, Feb 13, 2008 at 10:32:02PM -0800, Yinghai Lu wrote: > > On Wed, Feb 13, 2008 at 10:20 PM, Dhaval Giani > > <[EMAIL PROTECTED]> wrote: > > > On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote: > > > > Dhaval Giani wrote: > > > >> I am getting the following oops on bootup on 2.6.25-rc1 > > > > ... > > > >> I am booting using kexec with maxcpus=1. It does not have any problems > > > >> with maxcpus=2 or higher. > > > > > > > > Sounds like another (the same?) kexec cpu numbering bug. Can you > > > post/link > > > > the entire dmesg from both a cold boot and a kexec boot so we can > > > compare? > > > > > > > > > > Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec > > > boot. > > > > how about without "[EMAIL PROTECTED] nmi_watchdog=2" > > > > also does intel cpu support nmi_watchdog=2? > > > > Yes it does. I've used it to get some useful debug information. I will try > that out. > Panics at same point. -- regards, Dhaval -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc1 panics on boot
On Wed, Feb 13, 2008 at 10:32:02PM -0800, Yinghai Lu wrote: > On Wed, Feb 13, 2008 at 10:20 PM, Dhaval Giani > <[EMAIL PROTECTED]> wrote: > > On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote: > > > Dhaval Giani wrote: > > >> I am getting the following oops on bootup on 2.6.25-rc1 > > > ... > > >> I am booting using kexec with maxcpus=1. It does not have any problems > > >> with maxcpus=2 or higher. > > > > > > Sounds like another (the same?) kexec cpu numbering bug. Can you > > post/link > > > the entire dmesg from both a cold boot and a kexec boot so we can > > compare? > > > > > > > Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec > > boot. > > how about without "[EMAIL PROTECTED] nmi_watchdog=2" > > also does intel cpu support nmi_watchdog=2? > Yes it does. I've used it to get some useful debug information. I will try that out. > YH -- regards, Dhaval -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc1 panics on boot
On Wed, Feb 13, 2008 at 10:20 PM, Dhaval Giani <[EMAIL PROTECTED]> wrote: > On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote: > > Dhaval Giani wrote: > >> I am getting the following oops on bootup on 2.6.25-rc1 > > ... > >> I am booting using kexec with maxcpus=1. It does not have any problems > >> with maxcpus=2 or higher. > > > > Sounds like another (the same?) kexec cpu numbering bug. Can you post/link > > the entire dmesg from both a cold boot and a kexec boot so we can compare? > > > > Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec > boot. how about without "[EMAIL PROTECTED] nmi_watchdog=2" also does intel cpu support nmi_watchdog=2? YH -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc1 panics on boot
On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote: > Dhaval Giani wrote: >> I am getting the following oops on bootup on 2.6.25-rc1 > ... >> I am booting using kexec with maxcpus=1. It does not have any problems >> with maxcpus=2 or higher. > > Sounds like another (the same?) kexec cpu numbering bug. Can you post/link > the entire dmesg from both a cold boot and a kexec boot so we can compare? > Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec boot. [0.00] Linux version 2.6.25-rc1 ([EMAIL PROTECTED]) (gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)) #5 SMP Thu Feb 14 06:46:02 IST 2008 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: 0100 - 0009dc00 (usable) [0.00] BIOS-e820: 0009dc00 - 000a (reserved) [0.00] BIOS-e820: 0010 - e97f5f00 (usable) [0.00] BIOS-e820: e97f5f00 - e97ff800 (ACPI data) [0.00] BIOS-e820: e97ff800 - e980 (reserved) [0.00] BIOS-e820: fec0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00014000 (usable) [0.00] 4224MB HIGHMEM available. [0.00] 896MB LOWMEM available. [0.00] Scan SMP from c000 for 1024 bytes. [0.00] Scan SMP from c009fc00 for 1024 bytes. [0.00] Scan SMP from c00f for 65536 bytes. [0.00] Scan SMP from c009dc00 for 1024 bytes. [0.00] found SMP MP-table at [c009dd40] 0009dd40 [0.00] Reserving 64MB of memory at 16MB for crashkernel (System RAM: 5111MB) [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] Normal 4096 -> 229376 [0.00] HighMem229376 -> 1310720 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 -> 1310720 [0.00] DMI 2.3 present. [0.00] Using APIC driver default [0.00] ACPI: RSDP 000FDD90, 0014 (r0 IBM ) [0.00] ACPI: RSDT E97FF780, 0030 (r1 IBMSERONYXP 1000 IBM 45444F43) [0.00] ACPI: FACP E97FF700, 0074 (r1 IBMSERONYXP 1000 IBM 45444F43) [0.00] ACPI: DSDT E97F5F00, 962E (r1 IBMSERAVATR 1000 MSFT 10B) [0.00] ACPI: FACS E97FF5C0, 0040 [0.00] ACPI: APIC E97FF600, 00CA (r1 IBMSERONYXP 1000 IBM 45444F43) [0.00] ACPI: ASF! E97FF540, 004B (r16 IBMSERONYXP1 IBM 45444F43) [0.00] ACPI: PM-Timer IO Port: 0x488 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] Processor #0 15:2 APIC version 20 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) [0.00] Processor #2 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [0.00] Processor #4 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) [0.00] Processor #6 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) [0.00] Processor #1 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) [0.00] Processor #3 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) [0.00] Processor #5 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) [0.00] Processor #7 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1]) [0.00] ACPI: IOAPIC (id[0x0e] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 14, version 17, address 0xfec0, GSI 0-15 [0.00] ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16]) [0.00] IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31 [0.00] ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32]) [0.00] IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47 [
Re: 2.6.25-rc1 panics on boot
Dhaval Giani wrote: I am getting the following oops on bootup on 2.6.25-rc1 ... I am booting using kexec with maxcpus=1. It does not have any problems with maxcpus=2 or higher. Sounds like another (the same?) kexec cpu numbering bug. Can you post/link the entire dmesg from both a cold boot and a kexec boot so we can compare? -- Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc1 panics on boot
Dhaval Giani wrote: I am getting the following oops on bootup on 2.6.25-rc1 ... I am booting using kexec with maxcpus=1. It does not have any problems with maxcpus=2 or higher. Sounds like another (the same?) kexec cpu numbering bug. Can you post/link the entire dmesg from both a cold boot and a kexec boot so we can compare? -- Chris -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc1 panics on boot
On Wed, Feb 13, 2008 at 10:20 PM, Dhaval Giani [EMAIL PROTECTED] wrote: On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote: Dhaval Giani wrote: I am getting the following oops on bootup on 2.6.25-rc1 ... I am booting using kexec with maxcpus=1. It does not have any problems with maxcpus=2 or higher. Sounds like another (the same?) kexec cpu numbering bug. Can you post/link the entire dmesg from both a cold boot and a kexec boot so we can compare? Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec boot. how about without [EMAIL PROTECTED] nmi_watchdog=2 also does intel cpu support nmi_watchdog=2? YH -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc1 panics on boot
On Wed, Feb 13, 2008 at 10:32:02PM -0800, Yinghai Lu wrote: On Wed, Feb 13, 2008 at 10:20 PM, Dhaval Giani [EMAIL PROTECTED] wrote: On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote: Dhaval Giani wrote: I am getting the following oops on bootup on 2.6.25-rc1 ... I am booting using kexec with maxcpus=1. It does not have any problems with maxcpus=2 or higher. Sounds like another (the same?) kexec cpu numbering bug. Can you post/link the entire dmesg from both a cold boot and a kexec boot so we can compare? Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec boot. how about without [EMAIL PROTECTED] nmi_watchdog=2 also does intel cpu support nmi_watchdog=2? Yes it does. I've used it to get some useful debug information. I will try that out. YH -- regards, Dhaval -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc1 panics on boot
On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote: Dhaval Giani wrote: I am getting the following oops on bootup on 2.6.25-rc1 ... I am booting using kexec with maxcpus=1. It does not have any problems with maxcpus=2 or higher. Sounds like another (the same?) kexec cpu numbering bug. Can you post/link the entire dmesg from both a cold boot and a kexec boot so we can compare? Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec boot. [0.00] Linux version 2.6.25-rc1 ([EMAIL PROTECTED]) (gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)) #5 SMP Thu Feb 14 06:46:02 IST 2008 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: 0100 - 0009dc00 (usable) [0.00] BIOS-e820: 0009dc00 - 000a (reserved) [0.00] BIOS-e820: 0010 - e97f5f00 (usable) [0.00] BIOS-e820: e97f5f00 - e97ff800 (ACPI data) [0.00] BIOS-e820: e97ff800 - e980 (reserved) [0.00] BIOS-e820: fec0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00014000 (usable) [0.00] 4224MB HIGHMEM available. [0.00] 896MB LOWMEM available. [0.00] Scan SMP from c000 for 1024 bytes. [0.00] Scan SMP from c009fc00 for 1024 bytes. [0.00] Scan SMP from c00f for 65536 bytes. [0.00] Scan SMP from c009dc00 for 1024 bytes. [0.00] found SMP MP-table at [c009dd40] 0009dd40 [0.00] Reserving 64MB of memory at 16MB for crashkernel (System RAM: 5111MB) [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] Normal 4096 - 229376 [0.00] HighMem229376 - 1310720 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 - 1310720 [0.00] DMI 2.3 present. [0.00] Using APIC driver default [0.00] ACPI: RSDP 000FDD90, 0014 (r0 IBM ) [0.00] ACPI: RSDT E97FF780, 0030 (r1 IBMSERONYXP 1000 IBM 45444F43) [0.00] ACPI: FACP E97FF700, 0074 (r1 IBMSERONYXP 1000 IBM 45444F43) [0.00] ACPI: DSDT E97F5F00, 962E (r1 IBMSERAVATR 1000 MSFT 10B) [0.00] ACPI: FACS E97FF5C0, 0040 [0.00] ACPI: APIC E97FF600, 00CA (r1 IBMSERONYXP 1000 IBM 45444F43) [0.00] ACPI: ASF! E97FF540, 004B (r16 IBMSERONYXP1 IBM 45444F43) [0.00] ACPI: PM-Timer IO Port: 0x488 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] Processor #0 15:2 APIC version 20 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) [0.00] Processor #2 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [0.00] Processor #4 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) [0.00] Processor #6 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) [0.00] Processor #1 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) [0.00] Processor #3 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) [0.00] Processor #5 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) [0.00] Processor #7 15:2 APIC version 20 [0.00] WARNING: maxcpus limit of 1 reached. Processor ignored. [0.00] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1]) [0.00] ACPI: IOAPIC (id[0x0e] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 14, version 17, address 0xfec0, GSI 0-15 [0.00] ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16]) [0.00] IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31 [0.00] ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32]) [0.00] IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47 [0.00] ACPI:
Re: 2.6.25-rc1 panics on boot
On Thu, Feb 14, 2008 at 12:06:31PM +0530, Dhaval Giani wrote: On Wed, Feb 13, 2008 at 10:32:02PM -0800, Yinghai Lu wrote: On Wed, Feb 13, 2008 at 10:20 PM, Dhaval Giani [EMAIL PROTECTED] wrote: On Wed, Feb 13, 2008 at 01:08:42PM -0500, Chris Snook wrote: Dhaval Giani wrote: I am getting the following oops on bootup on 2.6.25-rc1 ... I am booting using kexec with maxcpus=1. It does not have any problems with maxcpus=2 or higher. Sounds like another (the same?) kexec cpu numbering bug. Can you post/link the entire dmesg from both a cold boot and a kexec boot so we can compare? Don't think its a kexec bug. Get the same on cold boot. dmesg from kexec boot. how about without [EMAIL PROTECTED] nmi_watchdog=2 also does intel cpu support nmi_watchdog=2? Yes it does. I've used it to get some useful debug information. I will try that out. Panics at same point. -- regards, Dhaval -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
