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/
2.6.25-rc1 panics on boot
Hi, I am getting the following oops on bootup on 2.6.25-rc1 [2.376187] BUG: unable to handle kernel NULL pointer dereference at 010c [2.388180] IP: [] sysfs_remove_link+0x1/0xd [2.396182] *pdpt = 005fd001 *pde = [2.404751] Oops: [#1] SMP [2.408179] Modules linked in: [2.408179] [2.408179] Pid: 1, comm: swapper Not tainted (2.6.25-rc1 #3) [2.408179] EIP: 0060:[] EFLAGS: 00010206 CPU: 0 [2.408179] EIP is at sysfs_remove_link+0x1/0xd [2.408179] EAX: 00f0 EBX: f7202cc8 ECX: f789eaf0 EDX: c0533e87 [2.408179] ESI: f793c970 EDI: ffed EBP: f78a1ea0 ESP: f78a1e90 [2.408179] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 [2.408179] Process swapper (pid: 1, ti=f78a task=f789eaf0 task.ti=f78a) [2.408179] Stack: f78a1ea0 c02709e4 c0568920 f793c970 f78a1eb4 c0269fb5 f793c970 f793cb7c [2.408179]c0568920 f78a1ecc c0269b25 f793cb7c c05689f0 f78a1ee0 [2.408179]c02b6460 c05689f0 f793cb7c f78a1ef4 c02b6528 f793cb7c f78c332c [2.408179] Call Trace: [2.408179] [] ? acpi_processor_remove+0x82/0xb4 [2.408179] [] ? acpi_start_single_object+0x3a/0x41 [2.408179] [] ? acpi_device_probe+0x3b/0x79 [2.408179] [] ? really_probe+0x74/0xf2 [2.408179] [] ? driver_probe_device+0x37/0x40 [2.408179] [] ? __driver_attach+0x76/0xaf [2.408179] [] ? bus_for_each_dev+0x38/0x5d [2.408179] [] ? kobject_init_and_add+0x20/0x22 [2.408179] [] ? driver_attach+0x14/0x16 [2.408179] [] ? __driver_attach+0x0/0xaf [2.408179] [] ? bus_add_driver+0x99/0x149 [2.408179] [] ? driver_register+0x43/0x69 [2.408179] [] ? acpi_bus_register_driver+0x3a/0x3c [2.408179] [] ? acpi_processor_init+0x70/0xa6 [2.408179] [] ? kernel_init+0x0/0x88 [2.408179] [] ? do_initcalls+0x75/0x18d [2.408179] [] ? create_proc_entry+0x67/0x7b [2.408179] [] ? register_irq_proc+0xa4/0xba [2.408179] [] ? pagemap_read+0x13a/0x1c2 [2.408179] [] ? kernel_init+0x0/0x88 [2.408179] [] ? do_basic_setup+0x1c/0x1e [2.408179] [] ? kernel_init+0x4d/0x88 [2.408179] [] ? kernel_thread_helper+0x7/0x10 [2.408179] === [2.408179] Code: c0 74 07 89 f0 e8 57 f4 ff ff 85 ff 74 11 90 ff 0f 0f 94 c0 84 c0 74 07 89 f8 e8 42 f4 ff ff 8b 45 d8 83 c4 1c 5b 5e 5f 5d c3 55 <8b> 40 1c 89 e5 e8 c [2.408179] EIP: [] sysfs_remove_link+0x1/0xd SS:ESP 0068:f78a1e90 [2.408191] ---[ end trace 778e504de7e3b1e3 ]--- [2.412183] Kernel panic - not syncing: Attempted to kill init! I am booting using kexec with maxcpus=1. It does not have any problems with maxcpus=2 or higher. config # # Automatically generated make config: don't edit # Linux kernel version: 2.6.25-rc1 # Wed Feb 13 17:30:43 2008 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y # CONFIG_GENERIC_LOCKBREAK is not set CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y # CONFIG_GENERIC_GPIO is not set CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_AOUT=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_X86_SMP=y CONFIG_X86_32_SMP=y CONFIG_X86_HT=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_TREE=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=16 CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set # CONFIG_CGROUP_NS is not set # CONFIG_CPUSETS is not set CONFIG_FAIR_GROUP_SCHED=y CONFIG_FAIR_USER_SCHED=y # CONFIG_FAIR_CGROUP_SCHED is not set # CONFIG_CGROUP_CPUACCT is not set # CONFIG_RESOURCE_COUNTERS is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_RELAY=y
2.6.25-rc1 panics on boot
Hi, I am getting the following oops on bootup on 2.6.25-rc1 [2.376187] BUG: unable to handle kernel NULL pointer dereference at 010c [2.388180] IP: [c01a9105] sysfs_remove_link+0x1/0xd [2.396182] *pdpt = 005fd001 *pde = [2.404751] Oops: [#1] SMP [2.408179] Modules linked in: [2.408179] [2.408179] Pid: 1, comm: swapper Not tainted (2.6.25-rc1 #3) [2.408179] EIP: 0060:[c01a9105] EFLAGS: 00010206 CPU: 0 [2.408179] EIP is at sysfs_remove_link+0x1/0xd [2.408179] EAX: 00f0 EBX: f7202cc8 ECX: f789eaf0 EDX: c0533e87 [2.408179] ESI: f793c970 EDI: ffed EBP: f78a1ea0 ESP: f78a1e90 [2.408179] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 [2.408179] Process swapper (pid: 1, ti=f78a task=f789eaf0 task.ti=f78a) [2.408179] Stack: f78a1ea0 c02709e4 c0568920 f793c970 f78a1eb4 c0269fb5 f793c970 f793cb7c [2.408179]c0568920 f78a1ecc c0269b25 f793cb7c c05689f0 f78a1ee0 [2.408179]c02b6460 c05689f0 f793cb7c f78a1ef4 c02b6528 f793cb7c f78c332c [2.408179] Call Trace: [2.408179] [c02709e4] ? acpi_processor_remove+0x82/0xb4 [2.408179] [c0269fb5] ? acpi_start_single_object+0x3a/0x41 [2.408179] [c0269b25] ? acpi_device_probe+0x3b/0x79 [2.408179] [c02b6460] ? really_probe+0x74/0xf2 [2.408179] [c02b6528] ? driver_probe_device+0x37/0x40 [2.408179] [c02b6639] ? __driver_attach+0x76/0xaf [2.408179] [c02b5825] ? bus_for_each_dev+0x38/0x5d [2.408179] [c0238906] ? kobject_init_and_add+0x20/0x22 [2.408179] [c02b6686] ? driver_attach+0x14/0x16 [2.408179] [c02b65c3] ? __driver_attach+0x0/0xaf [2.408179] [c02b5e04] ? bus_add_driver+0x99/0x149 [2.408179] [c02b6a68] ? driver_register+0x43/0x69 [2.408179] [c0269ff6] ? acpi_bus_register_driver+0x3a/0x3c [2.408179] [c05cf8dc] ? acpi_processor_init+0x70/0xa6 [2.408179] [c05ba8e0] ? kernel_init+0x0/0x88 [2.408179] [c05ba779] ? do_initcalls+0x75/0x18d [2.408179] [c01a3eb9] ? create_proc_entry+0x67/0x7b [2.408179] [c01527b7] ? register_irq_proc+0xa4/0xba [2.408179] [c01a] ? pagemap_read+0x13a/0x1c2 [2.408179] [c05ba8e0] ? kernel_init+0x0/0x88 [2.408179] [c05ba8ad] ? do_basic_setup+0x1c/0x1e [2.408179] [c05ba92d] ? kernel_init+0x4d/0x88 [2.408179] [c010563b] ? kernel_thread_helper+0x7/0x10 [2.408179] === [2.408179] Code: c0 74 07 89 f0 e8 57 f4 ff ff 85 ff 74 11 90 ff 0f 0f 94 c0 84 c0 74 07 89 f8 e8 42 f4 ff ff 8b 45 d8 83 c4 1c 5b 5e 5f 5d c3 55 8b 40 1c 89 e5 e8 c [2.408179] EIP: [c01a9105] sysfs_remove_link+0x1/0xd SS:ESP 0068:f78a1e90 [2.408191] ---[ end trace 778e504de7e3b1e3 ]--- [2.412183] Kernel panic - not syncing: Attempted to kill init! I am booting using kexec with maxcpus=1. It does not have any problems with maxcpus=2 or higher. config # # Automatically generated make config: don't edit # Linux kernel version: 2.6.25-rc1 # Wed Feb 13 17:30:43 2008 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y # CONFIG_GENERIC_LOCKBREAK is not set CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y # CONFIG_GENERIC_GPIO is not set CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y # CONFIG_HAVE_SETUP_PER_CPU_AREA is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_AOUT=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_X86_SMP=y CONFIG_X86_32_SMP=y CONFIG_X86_HT=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_TREE=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=16 CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set # CONFIG_CGROUP_NS is not set # CONFIG_CPUSETS is not set
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/
