Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
And the same thing with 2.6.24.1. Cheers, Chris Linux version 2.6.24.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP PREEMPT Fri Feb 8 22:41:10 GMT 2008 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1ffeb000 (usable) BIOS-e820: 1ffeb000 - 1ffef000 (ACPI data) BIOS-e820: 1ffef000 - 1000 (reserved) BIOS-e820: 1000 - 2000 (ACPI NVS) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 511MB LOWMEM available. Zone PFN ranges: DMA 0 -> 4096 Normal 4096 -> 131051 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 -> 131051 DMI 2.3 present. ACPI: RSDP 000F7B40, 0014 (r0 ASUS ) ACPI: RSDT 1FFEB000, 0030 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: FACP 1FFEB100, 0074 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: DSDT 1FFEB180, 39FA (r1 ASUS TUSL2-C 1000 MSFT 10B) ACPI: FACS 1000, 0040 ACPI: BOOT 1FFEB040, 0028 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: APIC 1FFEB080, 005A (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: PM-Timer IO Port: 0xe408 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:8 APIC version 17 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level) Enabling APIC mode: Logical Cluster. Using 1 I/O APICs, target cpus f Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:dec0) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130028 Kernel command line: ro root=LABEL=/ video=matroxfb:vesa:0x11A console=ttyS0,115200n8 console=tty0 nmi_watchdog=1 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c035f000 soft=c035b000 PID hash table entries: 2048 (order: 11, 8192 bytes) Detected 1005.042 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled console [ttyS0] enabled Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 513484k/524204k available (1577k kernel code, 10128k reserved, 607k data, 196k init, 0k highmem) virtual kernel memory layout: fixmap : 0xfffb5000 - 0xf000 ( 296 kB) vmalloc : 0xe080 - 0xfffb3000 ( 503 MB) lowmem : 0xc000 - 0xdffeb000 ( 511 MB) .init : 0xc0327000 - 0xc0358000 ( 196 kB) .data : 0xc028a7ca - 0xc03227c4 ( 607 kB) .text : 0xc010 - 0xc028a7ca (1577 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Calibrating delay using timer specific routine.. 2011.89 BogoMIPS (lpj=4023790) Mount-cache hash table entries: 512 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 9k freed ACPI: Core revision 20070126 CPU0: Intel Pentium III (Coppermine) stepping 06 Leaving ESR disabled. Total of 1 processors activated (2011.89 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() Pid: 1, comm: swapper Not tainted 2.6.24.1 #1 [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x6c/0x72 [] native_smp_call_function_mask+0x44/0x102 [] smp_call_function+0x1e/0x22 [] on_each_cpu+0x2a/0x57 [] setup_nmi+0x33/0x4a [] setup_IO_APIC+0x929/0xf11 [] native_smp_prepare_cpus+0x487/0x497 [] kernel_init+0x54/0x2c3 [] kernel_thread_helper+0x7/0x10 === APIC timer registered as dummy, due to nmi_watchdog=1! Brought up 1 CPUs net_namespace: 64 bytes NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0e30, last bus=3 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: (supports S0 S1 S5) ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region ec00-ec3f claimed by ICH4 GPIO PCI: Transparent bridge - :00:1e.0 ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10
Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
And the same thing with 2.6.24.1. Cheers, Chris Linux version 2.6.24.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP PREEMPT Fri Feb 8 22:41:10 GMT 2008 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1ffeb000 (usable) BIOS-e820: 1ffeb000 - 1ffef000 (ACPI data) BIOS-e820: 1ffef000 - 1000 (reserved) BIOS-e820: 1000 - 2000 (ACPI NVS) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 511MB LOWMEM available. Zone PFN ranges: DMA 0 - 4096 Normal 4096 - 131051 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 - 131051 DMI 2.3 present. ACPI: RSDP 000F7B40, 0014 (r0 ASUS ) ACPI: RSDT 1FFEB000, 0030 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: FACP 1FFEB100, 0074 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: DSDT 1FFEB180, 39FA (r1 ASUS TUSL2-C 1000 MSFT 10B) ACPI: FACS 1000, 0040 ACPI: BOOT 1FFEB040, 0028 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: APIC 1FFEB080, 005A (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: PM-Timer IO Port: 0xe408 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:8 APIC version 17 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level) Enabling APIC mode: Logical Cluster. Using 1 I/O APICs, target cpus f Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:dec0) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130028 Kernel command line: ro root=LABEL=/ video=matroxfb:vesa:0x11A console=ttyS0,115200n8 console=tty0 nmi_watchdog=1 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c035f000 soft=c035b000 PID hash table entries: 2048 (order: 11, 8192 bytes) Detected 1005.042 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled console [ttyS0] enabled Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 513484k/524204k available (1577k kernel code, 10128k reserved, 607k data, 196k init, 0k highmem) virtual kernel memory layout: fixmap : 0xfffb5000 - 0xf000 ( 296 kB) vmalloc : 0xe080 - 0xfffb3000 ( 503 MB) lowmem : 0xc000 - 0xdffeb000 ( 511 MB) .init : 0xc0327000 - 0xc0358000 ( 196 kB) .data : 0xc028a7ca - 0xc03227c4 ( 607 kB) .text : 0xc010 - 0xc028a7ca (1577 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Calibrating delay using timer specific routine.. 2011.89 BogoMIPS (lpj=4023790) Mount-cache hash table entries: 512 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 9k freed ACPI: Core revision 20070126 CPU0: Intel Pentium III (Coppermine) stepping 06 Leaving ESR disabled. Total of 1 processors activated (2011.89 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() Pid: 1, comm: swapper Not tainted 2.6.24.1 #1 [c0105020] show_trace_log_lvl+0x1a/0x2f [c0105990] show_trace+0x12/0x14 [c010613d] dump_stack+0x6c/0x72 [c0113ab5] native_smp_call_function_mask+0x44/0x102 [c0114cc5] smp_call_function+0x1e/0x22 [c0125bbc] on_each_cpu+0x2a/0x57 [c01170f2] setup_nmi+0x33/0x4a [c0332a22] setup_IO_APIC+0x929/0xf11 [c0330178] native_smp_prepare_cpus+0x487/0x497 [c03273de] kernel_init+0x54/0x2c3 [c0104c83] kernel_thread_helper+0x7/0x10 === APIC timer registered as dummy, due to nmi_watchdog=1! Brought up 1 CPUs net_namespace: 64 bytes NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0e30, last bus=3 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: (supports S0 S1 S5) ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region ec00-ec3f claimed by ICH4 GPIO PCI:
Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
--- Andrew Morton <[EMAIL PROTECTED]> wrote: > So it's a CONFIG_SMP=y kernel on a single-cpu machine? Correct. > It is unclear to me what clocksource (if any) your machine is using. The 2.6.23.x kernel uses the TSC: ... ACPI: Core revision 20070126 CPU0: Intel Pentium III (Coppermine) stepping 06 Total of 1 processors activated (2011.69 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 APIC timer registered as dummy, due to nmi_watchdog=1! Brought up 1 CPUs NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0e30, last bus=3 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: EC: Look up EC in DSDT ACPI: Interpreter enabled ACPI: (supports S0 S1 S5) ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region ec00-ec3f claimed by ICH4 GPIO PCI: Transparent bridge - :00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: bus type pnp registered pnp: PnP ACPI: found 15 devices ACPI: ACPI bus type pnp unregistered PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Time: tsc clocksource has been installed. ... Cheers, Chris ___ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/ -- 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: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
On Thu, 7 Feb 2008 19:58:10 + (GMT) Chris Rankin <[EMAIL PROTECTED]> wrote: > --- Andrew Morton <[EMAIL PROTECTED]> wrote: > > It isn't clear (to me) where in this mess we disabled interrupts around the > > set_cpus_allowed(). Chris, if this is repeatable it would be helpful to > > set CONFIG_FRAME_POINTER=y which hopefully will get us a cleaner trace, > > Here you go, > Thanks. > > Linux version 2.6.24 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat > 4.1.2-33)) #1 > SMP PREEMPT Thu Feb 7 00:01:40 GMT 2008 So it's a CONFIG_SMP=y kernel on a single-cpu machine? > BIOS-provided physical RAM map: > BIOS-e820: - 0009fc00 (usable) > BIOS-e820: 0009fc00 - 000a (reserved) > BIOS-e820: 000f - 0010 (reserved) > BIOS-e820: 0010 - 1ffeb000 (usable) > BIOS-e820: 1ffeb000 - 1ffef000 (ACPI data) > BIOS-e820: 1ffef000 - 1000 (reserved) > BIOS-e820: 1000 - 2000 (ACPI NVS) > BIOS-e820: fec0 - fec1 (reserved) > BIOS-e820: fee0 - fee01000 (reserved) > BIOS-e820: fff8 - 0001 (reserved) > 511MB LOWMEM available. > Zone PFN ranges: > DMA 0 -> 4096 > Normal 4096 -> 131051 > Movable zone start PFN for each node > early_node_map[1] active PFN ranges > 0:0 -> 131051 > DMI 2.3 present. > ACPI: RSDP 000F7B40, 0014 (r0 ASUS ) > ACPI: RSDT 1FFEB000, 0030 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) > ACPI: FACP 1FFEB100, 0074 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) > ACPI: DSDT 1FFEB180, 39FA (r1 ASUS TUSL2-C 1000 MSFT 10B) > ACPI: FACS 1000, 0040 > ACPI: BOOT 1FFEB040, 0028 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) > ACPI: APIC 1FFEB080, 005A (r1 ASUS TUSL2-C 30303031 MSFT 31313031) > ACPI: PM-Timer IO Port: 0xe408 > ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > Processor #0 6:8 APIC version 17 > ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) > ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) > IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge) > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level) > Enabling APIC mode: Logical Cluster. Using 1 I/O APICs, target cpus f > Using ACPI (MADT) for SMP configuration information > Allocating PCI resources starting at 3000 (gap: 2000:dec0) > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130028 > Kernel command line: ro root=LABEL=/ nmi_watchdog=1 video=matroxfb:vesa:0x11A > console=ttyS0,115200n8 console=tty0 > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Initializing CPU#0 > CPU 0 irqstacks, hard=c035f000 soft=c035b000 > PID hash table entries: 2048 (order: 11, 8192 bytes) > Detected 1005.086 MHz processor. > Console: colour VGA+ 80x25 > console [tty0] enabled > console [ttyS0] enabled > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > Memory: 513484k/524204k available (1577k kernel code, 10128k reserved, 608k > data, 196k init, 0k > highmem) > virtual kernel memory layout: > fixmap : 0xfffb5000 - 0xf000 ( 296 kB) > vmalloc : 0xe080 - 0xfffb3000 ( 503 MB) > lowmem : 0xc000 - 0xdffeb000 ( 511 MB) > .init : 0xc0327000 - 0xc0358000 ( 196 kB) > .data : 0xc028a722 - 0xc03227c4 ( 608 kB) > .text : 0xc010 - 0xc028a722 (1577 kB) > Checking if this processor honours the WP bit even in supervisor mode... Ok. > SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 > Calibrating delay using timer specific routine.. 2011.89 BogoMIPS > (lpj=4023782) > Mount-cache hash table entries: 512 > CPU: L1 I cache: 16K, L1 D cache: 16K > CPU: L2 cache: 256K > Intel machine check architecture supported. > Intel machine check reporting enabled on CPU#0. > Compat vDSO mapped to e000. > Checking 'hlt' instruction... OK. > SMP alternatives: switching to UP code > Freeing SMP alternatives: 9k freed > ACPI: Core revision 20070126 > CPU0: Intel Pentium III (Coppermine) stepping 06 > Leaving ESR disabled. > Total of 1 processors activated (2011.89 BogoMIPS). > ENABLING IO-APIC IRQs > ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 > WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() > Pid: 1, comm: swapper Not tainted 2.6.24 #1 > [] show_trace_log_lvl+0x1a/0x2f > [] show_trace+0x12/0x14 > [] dump_stack+0x6c/0x72 > [] native_smp_call_function_mask+0x44/0x102 > [] smp_call_function+0x1e/0x22 > [] on_each_cpu+0x2a/0x57 > [] setup_nmi+0x33/0x4a > [] setup_IO_APIC+0x929/0xf11 > [] native_smp_prepare_cpus+0x487/0x497 > [] kernel_init+0x54/0x2c3 > [] kernel_thread_helper+0x7/0x10 > === I'm in a twisty maze
Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
--- Andrew Morton <[EMAIL PROTECTED]> wrote: > It isn't clear (to me) where in this mess we disabled interrupts around the > set_cpus_allowed(). Chris, if this is repeatable it would be helpful to > set CONFIG_FRAME_POINTER=y which hopefully will get us a cleaner trace, Here you go, Cheers, Chris Linux version 2.6.24 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP PREEMPT Thu Feb 7 00:01:40 GMT 2008 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1ffeb000 (usable) BIOS-e820: 1ffeb000 - 1ffef000 (ACPI data) BIOS-e820: 1ffef000 - 1000 (reserved) BIOS-e820: 1000 - 2000 (ACPI NVS) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 511MB LOWMEM available. Zone PFN ranges: DMA 0 -> 4096 Normal 4096 -> 131051 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 -> 131051 DMI 2.3 present. ACPI: RSDP 000F7B40, 0014 (r0 ASUS ) ACPI: RSDT 1FFEB000, 0030 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: FACP 1FFEB100, 0074 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: DSDT 1FFEB180, 39FA (r1 ASUS TUSL2-C 1000 MSFT 10B) ACPI: FACS 1000, 0040 ACPI: BOOT 1FFEB040, 0028 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: APIC 1FFEB080, 005A (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: PM-Timer IO Port: 0xe408 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:8 APIC version 17 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level) Enabling APIC mode: Logical Cluster. Using 1 I/O APICs, target cpus f Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:dec0) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130028 Kernel command line: ro root=LABEL=/ nmi_watchdog=1 video=matroxfb:vesa:0x11A console=ttyS0,115200n8 console=tty0 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c035f000 soft=c035b000 PID hash table entries: 2048 (order: 11, 8192 bytes) Detected 1005.086 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled console [ttyS0] enabled Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 513484k/524204k available (1577k kernel code, 10128k reserved, 608k data, 196k init, 0k highmem) virtual kernel memory layout: fixmap : 0xfffb5000 - 0xf000 ( 296 kB) vmalloc : 0xe080 - 0xfffb3000 ( 503 MB) lowmem : 0xc000 - 0xdffeb000 ( 511 MB) .init : 0xc0327000 - 0xc0358000 ( 196 kB) .data : 0xc028a722 - 0xc03227c4 ( 608 kB) .text : 0xc010 - 0xc028a722 (1577 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Calibrating delay using timer specific routine.. 2011.89 BogoMIPS (lpj=4023782) Mount-cache hash table entries: 512 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 9k freed ACPI: Core revision 20070126 CPU0: Intel Pentium III (Coppermine) stepping 06 Leaving ESR disabled. Total of 1 processors activated (2011.89 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() Pid: 1, comm: swapper Not tainted 2.6.24 #1 [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x6c/0x72 [] native_smp_call_function_mask+0x44/0x102 [] smp_call_function+0x1e/0x22 [] on_each_cpu+0x2a/0x57 [] setup_nmi+0x33/0x4a [] setup_IO_APIC+0x929/0xf11 [] native_smp_prepare_cpus+0x487/0x497 [] kernel_init+0x54/0x2c3 [] kernel_thread_helper+0x7/0x10 === APIC timer registered as dummy, due to nmi_watchdog=1! Brought up 1 CPUs net_namespace: 64 bytes NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0e30, last bus=3 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: (supports S0 S1 S5) ACPI: Using IOAPIC for
Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
On Thu, 7 Feb 2008 19:58:10 + (GMT) Chris Rankin [EMAIL PROTECTED] wrote: --- Andrew Morton [EMAIL PROTECTED] wrote: It isn't clear (to me) where in this mess we disabled interrupts around the set_cpus_allowed(). Chris, if this is repeatable it would be helpful to set CONFIG_FRAME_POINTER=y which hopefully will get us a cleaner trace, Here you go, Thanks. Linux version 2.6.24 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP PREEMPT Thu Feb 7 00:01:40 GMT 2008 So it's a CONFIG_SMP=y kernel on a single-cpu machine? BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1ffeb000 (usable) BIOS-e820: 1ffeb000 - 1ffef000 (ACPI data) BIOS-e820: 1ffef000 - 1000 (reserved) BIOS-e820: 1000 - 2000 (ACPI NVS) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 511MB LOWMEM available. Zone PFN ranges: DMA 0 - 4096 Normal 4096 - 131051 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 - 131051 DMI 2.3 present. ACPI: RSDP 000F7B40, 0014 (r0 ASUS ) ACPI: RSDT 1FFEB000, 0030 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: FACP 1FFEB100, 0074 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: DSDT 1FFEB180, 39FA (r1 ASUS TUSL2-C 1000 MSFT 10B) ACPI: FACS 1000, 0040 ACPI: BOOT 1FFEB040, 0028 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: APIC 1FFEB080, 005A (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: PM-Timer IO Port: 0xe408 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:8 APIC version 17 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level) Enabling APIC mode: Logical Cluster. Using 1 I/O APICs, target cpus f Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:dec0) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130028 Kernel command line: ro root=LABEL=/ nmi_watchdog=1 video=matroxfb:vesa:0x11A console=ttyS0,115200n8 console=tty0 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c035f000 soft=c035b000 PID hash table entries: 2048 (order: 11, 8192 bytes) Detected 1005.086 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled console [ttyS0] enabled Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 513484k/524204k available (1577k kernel code, 10128k reserved, 608k data, 196k init, 0k highmem) virtual kernel memory layout: fixmap : 0xfffb5000 - 0xf000 ( 296 kB) vmalloc : 0xe080 - 0xfffb3000 ( 503 MB) lowmem : 0xc000 - 0xdffeb000 ( 511 MB) .init : 0xc0327000 - 0xc0358000 ( 196 kB) .data : 0xc028a722 - 0xc03227c4 ( 608 kB) .text : 0xc010 - 0xc028a722 (1577 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Calibrating delay using timer specific routine.. 2011.89 BogoMIPS (lpj=4023782) Mount-cache hash table entries: 512 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 9k freed ACPI: Core revision 20070126 CPU0: Intel Pentium III (Coppermine) stepping 06 Leaving ESR disabled. Total of 1 processors activated (2011.89 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() Pid: 1, comm: swapper Not tainted 2.6.24 #1 [c0105020] show_trace_log_lvl+0x1a/0x2f [c0105990] show_trace+0x12/0x14 [c010613d] dump_stack+0x6c/0x72 [c0113ab5] native_smp_call_function_mask+0x44/0x102 [c0114cc5] smp_call_function+0x1e/0x22 [c0125bb0] on_each_cpu+0x2a/0x57 [c01170f2] setup_nmi+0x33/0x4a [c0332a22] setup_IO_APIC+0x929/0xf11 [c0330178] native_smp_prepare_cpus+0x487/0x497 [c03273de] kernel_init+0x54/0x2c3 [c0104c83] kernel_thread_helper+0x7/0x10 === I'm in a twisty maze of kernel versions, all
Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
--- Andrew Morton [EMAIL PROTECTED] wrote: It isn't clear (to me) where in this mess we disabled interrupts around the set_cpus_allowed(). Chris, if this is repeatable it would be helpful to set CONFIG_FRAME_POINTER=y which hopefully will get us a cleaner trace, Here you go, Cheers, Chris Linux version 2.6.24 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP PREEMPT Thu Feb 7 00:01:40 GMT 2008 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1ffeb000 (usable) BIOS-e820: 1ffeb000 - 1ffef000 (ACPI data) BIOS-e820: 1ffef000 - 1000 (reserved) BIOS-e820: 1000 - 2000 (ACPI NVS) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 511MB LOWMEM available. Zone PFN ranges: DMA 0 - 4096 Normal 4096 - 131051 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 - 131051 DMI 2.3 present. ACPI: RSDP 000F7B40, 0014 (r0 ASUS ) ACPI: RSDT 1FFEB000, 0030 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: FACP 1FFEB100, 0074 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: DSDT 1FFEB180, 39FA (r1 ASUS TUSL2-C 1000 MSFT 10B) ACPI: FACS 1000, 0040 ACPI: BOOT 1FFEB040, 0028 (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: APIC 1FFEB080, 005A (r1 ASUS TUSL2-C 30303031 MSFT 31313031) ACPI: PM-Timer IO Port: 0xe408 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:8 APIC version 17 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 20 low level) Enabling APIC mode: Logical Cluster. Using 1 I/O APICs, target cpus f Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:dec0) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130028 Kernel command line: ro root=LABEL=/ nmi_watchdog=1 video=matroxfb:vesa:0x11A console=ttyS0,115200n8 console=tty0 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c035f000 soft=c035b000 PID hash table entries: 2048 (order: 11, 8192 bytes) Detected 1005.086 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled console [ttyS0] enabled Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 513484k/524204k available (1577k kernel code, 10128k reserved, 608k data, 196k init, 0k highmem) virtual kernel memory layout: fixmap : 0xfffb5000 - 0xf000 ( 296 kB) vmalloc : 0xe080 - 0xfffb3000 ( 503 MB) lowmem : 0xc000 - 0xdffeb000 ( 511 MB) .init : 0xc0327000 - 0xc0358000 ( 196 kB) .data : 0xc028a722 - 0xc03227c4 ( 608 kB) .text : 0xc010 - 0xc028a722 (1577 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Calibrating delay using timer specific routine.. 2011.89 BogoMIPS (lpj=4023782) Mount-cache hash table entries: 512 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 9k freed ACPI: Core revision 20070126 CPU0: Intel Pentium III (Coppermine) stepping 06 Leaving ESR disabled. Total of 1 processors activated (2011.89 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() Pid: 1, comm: swapper Not tainted 2.6.24 #1 [c0105020] show_trace_log_lvl+0x1a/0x2f [c0105990] show_trace+0x12/0x14 [c010613d] dump_stack+0x6c/0x72 [c0113ab5] native_smp_call_function_mask+0x44/0x102 [c0114cc5] smp_call_function+0x1e/0x22 [c0125bb0] on_each_cpu+0x2a/0x57 [c01170f2] setup_nmi+0x33/0x4a [c0332a22] setup_IO_APIC+0x929/0xf11 [c0330178] native_smp_prepare_cpus+0x487/0x497 [c03273de] kernel_init+0x54/0x2c3 [c0104c83] kernel_thread_helper+0x7/0x10 === APIC timer registered as dummy, due to nmi_watchdog=1! Brought up 1 CPUs net_namespace: 64 bytes NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0e30, last bus=3 PCI: Using configuration type 1 Setting up standard PCI resources
Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
On Wed, 6 Feb 2008 13:22:26 -0500 Len Brown <[EMAIL PROTECTED]> wrote: > On Tuesday 05 February 2008 18:32, Andrew Morton wrote: > > On Sat, 2 Feb 2008 23:36:42 + (GMT) > > Chris Rankin <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > I have a 1 GHz Coppermine PC with 512 MB RAM, and it is failing to boot > > > with the nmi_watchdog=1 > > > option. This kernel was rebuilt after doing a "make mrproper". The dmesg > > > log follows: > > > > Can you tell us if earlier kernels worked OK, and if so which version(s)? > > >From your other mail it appears that 2.6.23 was OK? > > > > > ... > > > > > > ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 > > > WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() > > > Pid: 1, comm: swapper Not tainted 2.6.24 #1 > > > [] native_smp_call_function_mask+0x43/0x114 > > > [] enable_NMI_through_LVT0+0x0/0x26 > > > [] common_interrupt+0x23/0x28 > > > [] enable_NMI_through_LVT0+0x0/0x26 > > > [] enable_NMI_through_LVT0+0x0/0x26 > > > [] smp_call_function+0x1c/0x1f > > > [] on_each_cpu+0x28/0x54 > > > [] setup_nmi+0x30/0x47 > > > [] setup_IO_APIC+0x88c/0xe49 > > > [] number+0x159/0x22f > > > [] __switch_to+0x23/0x133 > > > [] _spin_unlock_irq+0xe/0x22 > > > [] finish_task_switch+0x1c/0x50 > > > [] schedule+0x527/0x541 > > > [] _spin_unlock+0xd/0x21 > > > [] preempt_schedule+0x43/0x54 > > > [] vprintk+0x2c1/0x2fc > > > [] device_add+0x318/0x541 > > > [] native_smp_prepare_cpus+0x45f/0x46f > > > [] acpi_ns_get_device_callback+0xfe/0x11c > > > [] _spin_lock+0xd/0x5a > > > [] task_rq_lock+0x28/0x4b > > > [] _spin_unlock_irqrestore+0xf/0x23 > > > [] set_cpus_allowed+0x86/0x8e > > > [] __driver_attach+0x0/0x7f > > > [] serial8250_set_termios+0x2b4/0x2c8 > > > [] kernel_init+0x0/0x2b2 > > > [] kernel_init+0x52/0x2b2 > > > [] _spin_unlock_irq+0xe/0x22 > > > [] finish_task_switch+0x1c/0x50 > > > [] schedule_tail+0x17/0x51 > > > [] ret_from_fork+0x6/0x1c > > > [] kernel_init+0x0/0x2b2 > > > [] kernel_init+0x0/0x2b2 > > > [] kernel_thread_helper+0x7/0x10 > > > === > > > > I think we've fixed that now. Len: if so, has that fix been sent in for > > 2.6.24.1? > > No, I don't know of any 2.6.24 oops fixes that aren't already in 2.6.24 -- > at least I can't think of any right now. Actually on closer inspection I'd say that acpi_ns_get_device_callback is stack gunk and it isn't involved here. It isn't clear (to me) where in this mess we disabled interrupts around the set_cpus_allowed(). Chris, if this is repeatable it would be helpful to set CONFIG_FRAME_POINTER=y which hopefully will get us a cleaner trace, thanks. -- 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: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
On Tuesday 05 February 2008 18:32, Andrew Morton wrote: > On Sat, 2 Feb 2008 23:36:42 + (GMT) > Chris Rankin <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I have a 1 GHz Coppermine PC with 512 MB RAM, and it is failing to boot > > with the nmi_watchdog=1 > > option. This kernel was rebuilt after doing a "make mrproper". The dmesg > > log follows: > > Can you tell us if earlier kernels worked OK, and if so which version(s)? > >From your other mail it appears that 2.6.23 was OK? > > > ... > > > > ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 > > WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() > > Pid: 1, comm: swapper Not tainted 2.6.24 #1 > > [] native_smp_call_function_mask+0x43/0x114 > > [] enable_NMI_through_LVT0+0x0/0x26 > > [] common_interrupt+0x23/0x28 > > [] enable_NMI_through_LVT0+0x0/0x26 > > [] enable_NMI_through_LVT0+0x0/0x26 > > [] smp_call_function+0x1c/0x1f > > [] on_each_cpu+0x28/0x54 > > [] setup_nmi+0x30/0x47 > > [] setup_IO_APIC+0x88c/0xe49 > > [] number+0x159/0x22f > > [] __switch_to+0x23/0x133 > > [] _spin_unlock_irq+0xe/0x22 > > [] finish_task_switch+0x1c/0x50 > > [] schedule+0x527/0x541 > > [] _spin_unlock+0xd/0x21 > > [] preempt_schedule+0x43/0x54 > > [] vprintk+0x2c1/0x2fc > > [] device_add+0x318/0x541 > > [] native_smp_prepare_cpus+0x45f/0x46f > > [] acpi_ns_get_device_callback+0xfe/0x11c > > [] _spin_lock+0xd/0x5a > > [] task_rq_lock+0x28/0x4b > > [] _spin_unlock_irqrestore+0xf/0x23 > > [] set_cpus_allowed+0x86/0x8e > > [] __driver_attach+0x0/0x7f > > [] serial8250_set_termios+0x2b4/0x2c8 > > [] kernel_init+0x0/0x2b2 > > [] kernel_init+0x52/0x2b2 > > [] _spin_unlock_irq+0xe/0x22 > > [] finish_task_switch+0x1c/0x50 > > [] schedule_tail+0x17/0x51 > > [] ret_from_fork+0x6/0x1c > > [] kernel_init+0x0/0x2b2 > > [] kernel_init+0x0/0x2b2 > > [] kernel_thread_helper+0x7/0x10 > > === > > I think we've fixed that now. Len: if so, has that fix been sent in for > 2.6.24.1? No, I don't know of any 2.6.24 oops fixes that aren't already in 2.6.24 -- at least I can't think of any right now. -Len > > > APIC timer registered as dummy, due to nmi_watchdog=1! > > Brought up 1 CPUs > > net_namespace: 64 bytes > > NET: Registered protocol family 16 > > ACPI: bus type pci registered > > PCI: PCI BIOS revision 2.10 entry at 0xf0e30, last bus=3 > > PCI: Using configuration type 1 > > Setting up standard PCI resources > > ACPI: Interpreter enabled > > ACPI: (supports S0 S1 S5) > > ACPI: Using IOAPIC for interrupt routing > > ACPI: PCI Root Bridge [PCI0] (:00) > > PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO > > PCI quirk: region ec00-ec3f claimed by ICH4 GPIO > > PCI: Transparent bridge - :00:1e.0 > > ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) > > ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) > > ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) > > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > > ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > > ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > > ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > > ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > > Linux Plug and Play Support v0.97 (c) Adam Belay > > pnp: PnP ACPI init > > ACPI: bus type pnp registered > > pnp: PnP ACPI: found 15 devices > > ACPI: ACPI bus type pnp unregistered > > PCI: Using ACPI for IRQ routing > > PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a > > report > > BUG: NMI Watchdog detected LOCKUP on CPU0, eip c0102ad1, registers: > > Modules linked in: > > > > Pid: 0, comm: swapper Not tainted (2.6.24 #1) > > EIP: 0060:[] EFLAGS: 0246 CPU: 0 > > EIP is at default_idle+0x2c/0x3e > > EAX: EBX: c0102aa5 ECX: 010bb000 EDX: fffedb3c > > ESI: EDI: c1409284 EBP: 0004 ESP: c031bfc8 > > DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 > > Process swapper (pid: 0, ti=c031b000 task=c02f4320 task.ti=c031b000) > > Stack: c010258e c140c000 c034e284 c031f8dc 0037 c031f0e0 > > 9000 > >c033b260 0002 00099800 c0311000 007a2007 > > Call Trace: > > [] cpu_idle+0x97/0xcc > > [] start_kernel+0x2e1/0x2e9 > > [] unknown_bootoption+0x0/0x195 > > === > > Code: 3d 48 a9 35 c0 00 75 32 80 3d e5 97 31 c0 00 74 29 89 e0 25 00 f0 ff > > ff 83 60 0c fd f0 83 04 > > 24 00 fa 8b 40 08 a8 04 75 04 fb f4 01 fb 89 e0 25 00 f0 ff ff 83 48 > > 0c 02 c3 f3 90 c3 55 57 > > 56 > > > -- > 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/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to
Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
On Tuesday 05 February 2008 18:32, Andrew Morton wrote: On Sat, 2 Feb 2008 23:36:42 + (GMT) Chris Rankin [EMAIL PROTECTED] wrote: Hi, I have a 1 GHz Coppermine PC with 512 MB RAM, and it is failing to boot with the nmi_watchdog=1 option. This kernel was rebuilt after doing a make mrproper. The dmesg log follows: Can you tell us if earlier kernels worked OK, and if so which version(s)? From your other mail it appears that 2.6.23 was OK? ... ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() Pid: 1, comm: swapper Not tainted 2.6.24 #1 [c0112a37] native_smp_call_function_mask+0x43/0x114 [c01149f2] enable_NMI_through_LVT0+0x0/0x26 [c01049b3] common_interrupt+0x23/0x28 [c01149f2] enable_NMI_through_LVT0+0x0/0x26 [c01149f2] enable_NMI_through_LVT0+0x0/0x26 [c0113c07] smp_call_function+0x1c/0x1f [c01244e2] on_each_cpu+0x28/0x54 [c0115eee] setup_nmi+0x30/0x47 [c032a820] setup_IO_APIC+0x88c/0xe49 [c01b2166] number+0x159/0x22f [c0103078] __switch_to+0x23/0x133 [c0282231] _spin_unlock_irq+0xe/0x22 [c011bd5a] finish_task_switch+0x1c/0x50 [c02807a5] schedule+0x527/0x541 [c02821a6] _spin_unlock+0xd/0x21 [c028083e] preempt_schedule+0x43/0x54 [c0120c92] vprintk+0x2c1/0x2fc [c020c610] device_add+0x318/0x541 [c0328084] native_smp_prepare_cpus+0x45f/0x46f [c01e0b07] acpi_ns_get_device_callback+0xfe/0x11c [c0282087] _spin_lock+0xd/0x5a [c011a998] task_rq_lock+0x28/0x4b [c028220f] _spin_unlock_irqrestore+0xf/0x23 [c011c13f] set_cpus_allowed+0x86/0x8e [c020e0d9] __driver_attach+0x0/0x7f [c0209860] serial8250_set_termios+0x2b4/0x2c8 [c031f349] kernel_init+0x0/0x2b2 [c031f39b] kernel_init+0x52/0x2b2 [c0282231] _spin_unlock_irq+0xe/0x22 [c011bd5a] finish_task_switch+0x1c/0x50 [c011cced] schedule_tail+0x17/0x51 [c0103ec2] ret_from_fork+0x6/0x1c [c031f349] kernel_init+0x0/0x2b2 [c031f349] kernel_init+0x0/0x2b2 [c0104bc3] kernel_thread_helper+0x7/0x10 === I think we've fixed that now. Len: if so, has that fix been sent in for 2.6.24.1? No, I don't know of any 2.6.24 oops fixes that aren't already in 2.6.24 -- at least I can't think of any right now. -Len APIC timer registered as dummy, due to nmi_watchdog=1! Brought up 1 CPUs net_namespace: 64 bytes NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0e30, last bus=3 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: (supports S0 S1 S5) ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region ec00-ec3f claimed by ICH4 GPIO PCI: Transparent bridge - :00:1e.0 ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: bus type pnp registered pnp: PnP ACPI: found 15 devices ACPI: ACPI bus type pnp unregistered PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try pci=routeirq. If it helps, post a report BUG: NMI Watchdog detected LOCKUP on CPU0, eip c0102ad1, registers: Modules linked in: Pid: 0, comm: swapper Not tainted (2.6.24 #1) EIP: 0060:[c0102ad1] EFLAGS: 0246 CPU: 0 EIP is at default_idle+0x2c/0x3e EAX: EBX: c0102aa5 ECX: 010bb000 EDX: fffedb3c ESI: EDI: c1409284 EBP: 0004 ESP: c031bfc8 DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 Process swapper (pid: 0, ti=c031b000 task=c02f4320 task.ti=c031b000) Stack: c010258e c140c000 c034e284 c031f8dc 0037 c031f0e0 9000 c033b260 0002 00099800 c0311000 007a2007 Call Trace: [c010258e] cpu_idle+0x97/0xcc [c031f8dc] start_kernel+0x2e1/0x2e9 [c031f0e0] unknown_bootoption+0x0/0x195 === Code: 3d 48 a9 35 c0 00 75 32 80 3d e5 97 31 c0 00 74 29 89 e0 25 00 f0 ff ff 83 60 0c fd f0 83 04 24 00 fa 8b 40 08 a8 04 75 04 fb f4 eb 01 fb 89 e0 25 00 f0 ff ff 83 48 0c 02 c3 f3 90 c3 55 57 56 -- 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/ -- To unsubscribe from
Re: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
--- Andrew Morton <[EMAIL PROTECTED]> wrote: > On Sat, 2 Feb 2008 23:36:42 + (GMT) > Chris Rankin <[EMAIL PROTECTED]> wrote: > > I have a 1 GHz Coppermine PC with 512 MB RAM, and it is failing to boot > > with the > nmi_watchdog=1 > > option. This kernel was rebuilt after doing a "make mrproper". The dmesg > > log follows: > > Can you tell us if earlier kernels worked OK, and if so which version(s)? > From your other mail it appears that 2.6.23 was OK? Oh yes, 2.6.23.14 is fine with nmi_watchdog=1. (This is on a UP machine with a SMP/PREEMPT kernel, BTW. "Just for fun.") Cheers, Chris __ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com -- 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: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
On Sat, 2 Feb 2008 23:36:42 + (GMT) Chris Rankin <[EMAIL PROTECTED]> wrote: > Hi, > > I have a 1 GHz Coppermine PC with 512 MB RAM, and it is failing to boot with > the nmi_watchdog=1 > option. This kernel was rebuilt after doing a "make mrproper". The dmesg log > follows: Can you tell us if earlier kernels worked OK, and if so which version(s)? >From your other mail it appears that 2.6.23 was OK? > ... > > ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 > WARNING: at arch/x86/kernel/smp_32.c:561 native_smp_call_function_mask() > Pid: 1, comm: swapper Not tainted 2.6.24 #1 > [] native_smp_call_function_mask+0x43/0x114 > [] enable_NMI_through_LVT0+0x0/0x26 > [] common_interrupt+0x23/0x28 > [] enable_NMI_through_LVT0+0x0/0x26 > [] enable_NMI_through_LVT0+0x0/0x26 > [] smp_call_function+0x1c/0x1f > [] on_each_cpu+0x28/0x54 > [] setup_nmi+0x30/0x47 > [] setup_IO_APIC+0x88c/0xe49 > [] number+0x159/0x22f > [] __switch_to+0x23/0x133 > [] _spin_unlock_irq+0xe/0x22 > [] finish_task_switch+0x1c/0x50 > [] schedule+0x527/0x541 > [] _spin_unlock+0xd/0x21 > [] preempt_schedule+0x43/0x54 > [] vprintk+0x2c1/0x2fc > [] device_add+0x318/0x541 > [] native_smp_prepare_cpus+0x45f/0x46f > [] acpi_ns_get_device_callback+0xfe/0x11c > [] _spin_lock+0xd/0x5a > [] task_rq_lock+0x28/0x4b > [] _spin_unlock_irqrestore+0xf/0x23 > [] set_cpus_allowed+0x86/0x8e > [] __driver_attach+0x0/0x7f > [] serial8250_set_termios+0x2b4/0x2c8 > [] kernel_init+0x0/0x2b2 > [] kernel_init+0x52/0x2b2 > [] _spin_unlock_irq+0xe/0x22 > [] finish_task_switch+0x1c/0x50 > [] schedule_tail+0x17/0x51 > [] ret_from_fork+0x6/0x1c > [] kernel_init+0x0/0x2b2 > [] kernel_init+0x0/0x2b2 > [] kernel_thread_helper+0x7/0x10 > === I think we've fixed that now. Len: if so, has that fix been sent in for 2.6.24.1? > APIC timer registered as dummy, due to nmi_watchdog=1! > Brought up 1 CPUs > net_namespace: 64 bytes > NET: Registered protocol family 16 > ACPI: bus type pci registered > PCI: PCI BIOS revision 2.10 entry at 0xf0e30, last bus=3 > PCI: Using configuration type 1 > Setting up standard PCI resources > ACPI: Interpreter enabled > ACPI: (supports S0 S1 S5) > ACPI: Using IOAPIC for interrupt routing > ACPI: PCI Root Bridge [PCI0] (:00) > PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO > PCI quirk: region ec00-ec3f claimed by ICH4 GPIO > PCI: Transparent bridge - :00:1e.0 > ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) > ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: PnP ACPI init > ACPI: bus type pnp registered > pnp: PnP ACPI: found 15 devices > ACPI: ACPI bus type pnp unregistered > PCI: Using ACPI for IRQ routing > PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report > BUG: NMI Watchdog detected LOCKUP on CPU0, eip c0102ad1, registers: > Modules linked in: > > Pid: 0, comm: swapper Not tainted (2.6.24 #1) > EIP: 0060:[] EFLAGS: 0246 CPU: 0 > EIP is at default_idle+0x2c/0x3e > EAX: EBX: c0102aa5 ECX: 010bb000 EDX: fffedb3c > ESI: EDI: c1409284 EBP: 0004 ESP: c031bfc8 > DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 > Process swapper (pid: 0, ti=c031b000 task=c02f4320 task.ti=c031b000) > Stack: c010258e c140c000 c034e284 c031f8dc 0037 c031f0e0 > 9000 >c033b260 0002 00099800 c0311000 007a2007 > Call Trace: > [] cpu_idle+0x97/0xcc > [] start_kernel+0x2e1/0x2e9 > [] unknown_bootoption+0x0/0x195 > === > Code: 3d 48 a9 35 c0 00 75 32 80 3d e5 97 31 c0 00 74 29 89 e0 25 00 f0 ff ff > 83 60 0c fd f0 83 04 > 24 00 fa 8b 40 08 a8 04 75 04 fb f4 01 fb 89 e0 25 00 f0 ff ff 83 48 0c > 02 c3 f3 90 c3 55 57 > 56 -- 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: [BUG] 2.6.24 refuses to boot - NMI watchdog problem?
--- Andrew Morton [EMAIL PROTECTED] wrote: On Sat, 2 Feb 2008 23:36:42 + (GMT) Chris Rankin [EMAIL PROTECTED] wrote: I have a 1 GHz Coppermine PC with 512 MB RAM, and it is failing to boot with the nmi_watchdog=1 option. This kernel was rebuilt after doing a make mrproper. The dmesg log follows: Can you tell us if earlier kernels worked OK, and if so which version(s)? From your other mail it appears that 2.6.23 was OK? Oh yes, 2.6.23.14 is fine with nmi_watchdog=1. (This is on a UP machine with a SMP/PREEMPT kernel, BTW. Just for fun.) Cheers, Chris __ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com -- 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/
