2.6.27rc1 cannot boot more than 8CPUs - Kernel

This is a discussion on 2.6.27rc1 cannot boot more than 8CPUs - Kernel ; I've a Dell R900 with 4 quad-core Xeon processors (total 16CPUs), but can only managed to boot up with CONFIG_NR_CPUS=8. Setting CONFIG_NR_CPUS=16 causes the kernel to hang while booting. Here's the dmesg with CONFIG_NR_CPUS=8 ... CPU6: Intel(R) Xeon(R) CPU L7345 ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 26

Thread: 2.6.27rc1 cannot boot more than 8CPUs

  1. 2.6.27rc1 cannot boot more than 8CPUs

    I've a Dell R900 with 4 quad-core Xeon processors (total 16CPUs), but
    can only managed to boot up with CONFIG_NR_CPUS=8. Setting
    CONFIG_NR_CPUS=16 causes the kernel to hang while booting.


    Here's the dmesg with CONFIG_NR_CPUS=8 ...

    CPU6: Intel(R) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
    checking TSC synchronization [CPU#0 -> CPU#6]: passed.
    CPU 7 irqstacks, hard=c0526000 soft=c051e000
    Booting processor 7/26 ip 6000
    Initializing CPU#7
    Calibrating delay using timer specific routine.. 3723.85 BogoMIPS (lpj=7447700)
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 6
    CPU: Processor Core ID: 2
    x86 PAT enabled: cpu 7, old 0x7040600070406, new 0x7010600070106
    CPU7: Intel(R) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
    checking TSC synchronization [CPU#0 -> CPU#7]: passed.
    Brought up 8 CPUs
    Total of 8 processors activated (29790.71 BogoMIPS).
    net_namespace: 596 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16


    Here's the dmesg with CONFIG_NR_CPUS=16 ...
    Booting processor 8/1 ip 6000
    Initializing CPU#8
    Calibrating delay using timer specific routine.. 3723.85 BogoMIPS (lpj=7447793)
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    x86 PAT enabled: cpu 7, old 0x7040600070406, new 0x7010600070106
    CPU8: Intel(R) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
    checking TSC synchronization [CPU#0 -> CPU#8]: passed.
    *** Hangs here ***


    How can I debug this further? I'm using the latest linux git pull.


    Thanks,
    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  2. references:in-reply-to:content-type:

    Jeff Chua wrote:
    > I've a Dell R900 with 4 quad-core Xeon processors (total 16CPUs), but
    > can only managed to boot up with CONFIG_NR_CPUS=8. Setting
    > CONFIG_NR_CPUS=16 causes the kernel to hang while booting.


    You could try booting CONFIG_NR_CPUS=16 with maxcpus=8 (kernel command line
    option).

    If it boots you can then try bringing the rest of the cpus online manually
    echo 1 > /sys/devices/system/cpu/cpu8/online
    ...
    echo 1 > /sys/devices/system/cpu/cpu15/online

    Might get a better OOPS/BUG_ON/etc report.

    Max
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 11:31 AM, Max Krasnyansky wrote:
    > You could try booting CONFIG_NR_CPUS=16 with maxcpus=8 (kernel command line option).
    > If it boots you can then try bringing the rest of the cpus online manually


    Ok, booted with CONFIG_NR_CPUS=16 with maxcpus=8, but can't find the
    rest of the CPUs.

    I can only find cpu0 to cpu7 ...


    drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu0
    drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu1
    drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu2
    drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu3
    drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu4
    drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu5
    drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu6
    drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu7
    -r--r--r-- 1 root root 4096 Aug 6 19:41 online
    -r--r--r-- 1 root root 4096 Aug 6 19:39 possible
    -r--r--r-- 1 root root 4096 Aug 6 19:38 present
    -rw-r--r-- 1 root root 4096 Aug 6 19:38 sched_mc_power_savings

    # cat online
    0-7
    # cat possible
    0-23
    # cat present
    0-7

    Thanks,
    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  4. references:in-reply-to:content-type:

    Jeff Chua wrote:
    > On Wed, Aug 6, 2008 at 11:31 AM, Max Krasnyansky wrote:
    >> You could try booting CONFIG_NR_CPUS=16 with maxcpus=8 (kernel command line option).
    >> If it boots you can then try bringing the rest of the cpus online manually

    >
    > Ok, booted with CONFIG_NR_CPUS=16 with maxcpus=8, but can't find the
    > rest of the CPUs.
    >
    > I can only find cpu0 to cpu7 ...
    >
    >
    > drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu0
    > drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu1
    > drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu2
    > drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu3
    > drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu4
    > drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu5
    > drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu6
    > drwxr-xr-x 4 root root 0 Aug 6 19:38 cpu7
    > -r--r--r-- 1 root root 4096 Aug 6 19:41 online
    > -r--r--r-- 1 root root 4096 Aug 6 19:39 possible
    > -r--r--r-- 1 root root 4096 Aug 6 19:38 present
    > -rw-r--r-- 1 root root 4096 Aug 6 19:38 sched_mc_power_savings
    >
    > # cat online
    > 0-7
    > # cat possible
    > 0-23
    > # cat present
    > 0-7


    Are you running 32-bit kernel ?

    Max


    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 11:50 AM, Yinghai Lu wrote:

    > 32bit or 64 bit?


    32bit.

    High Memory Support (64GB) --->
    -*- PAE (Physical Address Extension) Support
    Memory model (Sparse Memory) --->
    -*- 64 bit Memory and IO resources (EXPERIMENTAL)[*] Allocate 3rd-level pagetables from highmem


    > can you post full demsg?


    The following is "cut&paste" ... (gmail is not the a good way to do
    this.) for the 8 cpus that I managed to boot.

    routine.. 3723.90 BogoMIPS (lpj=7447810)
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 6
    CPU: Processor Core ID: 0
    x86 PAT enabled: cpu 3, old 0x7040600070406, new 0x7010600070106
    CPU3: Intel(R) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
    checking TSC synchronization [CPU#0 -> CPU#3]: passed.
    CPU 4 irqstacks, hard=c053f000 soft=c051f000
    Booting processor 4/2 ip 6000
    Initializing CPU#4
    Calibrating delay using timer specific routine.. 3723.87 BogoMIPS (lpj=7447748)
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 2
    x86 PAT enabled: cpu 4, old 0x7040600070406, new 0x7010600070106
    CPU4: Intel(R) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
    checking TSC synchronization [CPU#0 -> CPU#4]: passed.
    CPU 5 irqstacks, hard=c0540000 soft=c0520000
    Booting processor 5/10 ip 6000
    Initializing CPU#5
    Calibrating delay using timer specific routine.. 3723.89 BogoMIPS (lpj=7447794)
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 2
    CPU: Processor Core ID: 2
    x86 PAT enabled: cpu 5, old 0x7040600070406, new 0x7010600070106
    CPU5: Intel(R) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
    checking TSC synchronization [CPU#0 -> CPU#5]: passed.
    CPU 6 irqstacks, hard=c0541000 soft=c0521000
    Booting processor 6/18 ip 6000
    Initializing CPU#6
    Calibrating delay using timer specific routine.. 3723.89 BogoMIPS (lpj=7447791)
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 4
    CPU: Processor Core ID: 2
    x86 PAT enabled: cpu 6, old 0x7040600070406, new 0x7010600070106
    CPU6: Intel(R) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
    checking TSC synchronization [CPU#0 -> CPU#6]: passed.
    CPU 7 irqstacks, hard=c0542000 soft=c0522000
    Booting processor 7/26 ip 6000
    Initializing CPU#7
    Calibrating delay using timer specific routine.. 3723.88 BogoMIPS (lpj=7447769)
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 4096K
    CPU: Physical Processor ID: 6
    CPU: Processor Core ID: 2
    x86 PAT enabled: cpu 7, old 0x7040600070406, new 0x7010600070106
    CPU7: Intel(R) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
    checking TSC synchronization [CPU#0 -> CPU#7]: passed.
    Brought up 8 CPUs
    Total of 8 processors activated (29791.07 BogoMIPS).
    net_namespace: 596 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    No dock devices found.
    ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    ACPI: bus type pci registered
    PCI: Using configuration type 1 for base access
    PCI: Dell PowerEdge R900 detected, enabling pci=bfsort.
    ACPI: EC: Look up EC in DSDT
    ACPI: BIOS _OSI(Linux) query ignored
    ACPI: DMI System Vendor: Dell Inc.
    ACPI: DMI Product Name: PowerEdge R900
    ACPI: DMI Product Version:
    ACPI: DMI Board Name: 0C764H
    ACPI: DMI BIOS Vendor: Dell Inc.
    ACPI: DMI BIOS Date: 03/23/2008
    ACPI: Please send DMI info above to linux-acpi@vger.kernel.org
    ACPI: If "acpi_osi=Linux" works better, please notify linux-acpi@vger.kernel.org
    ACPI: Interpreter enabled
    ACPI: (supports S0 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:00.0: PME# disabled
    pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:01.0: PME# disabled
    pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:02.0: PME# disabled
    pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:03.0: PME# disabled
    pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:04.0: PME# disabled
    pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:06.0: PME# disabled
    pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.0: PME# disabled
    pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1d.7: PME# disabled
    pci 0000:00:1f.2: PME# supported from D3hot
    pci 0000:00:1f.2: PME# disabled
    pci 0000:16:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:16:00.0: PME# disabled
    pci 0000:16:00.3: PME# supported from D0 D3hot D3cold
    pci 0000:16:00.3: PME# disabled
    pci 0000:17:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:17:00.0: PME# disabled
    pci 0000:17:01.0: PME# supported from D0 D3hot D3cold
    pci 0000:17:01.0: PME# disabled
    pci 0000:19:00.0: supports D1
    pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:01:00.0: PME# disabled
    pci 0000:02:01.0: PME# supported from D0 D3hot D3cold
    pci 0000:02:01.0: PME# disabled
    pci 0000:02:02.0: PME# supported from D0 D3hot D3cold
    pci 0000:02:02.0: PME# disabled
    pci 0000:02:03.0: PME# supported from D0 D3hot D3cold
    pci 0000:02:03.0: PME# disabled
    pci 0000:02:04.0: PME# supported from D0 D3hot D3cold
    pci 0000:02:04.0: PME# disabled
    pci 0000:02:05.0: PME# supported from D0 D3hot D3cold
    pci 0000:02:05.0: PME# disabled
    pci 0000:0a:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:0a:00.0: PME# disabled
    pci 0000:0b:00.0: PME# supported from D3hot D3cold
    pci 0000:0b:00.0: PME# disabled
    pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:08:00.0: PME# disabled
    pci 0000:09:00.0: PME# supported from D3hot D3cold
    pci 0000:09:00.0: PME# disabled
    pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:06:00.0: PME# disabled
    pci 0000:07:00.0: PME# supported from D3hot D3cold
    pci 0000:07:00.0: PME# disabled
    pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:04:00.0: PME# disabled
    pci 0000:05:00.0: PME# supported from D3hot D3cold
    pci 0000:05:00.0: PME# disabled
    pci 0000:0c:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:0d:02.0: PME# disabled
    pci 0000:0d:04.0: PME# supported from D0 D3hot D3cold
    pci 0000:0d:04.0: PME# disabled
    pci 0000:10:00.0: PME# supported from D0 D3hot D3cold
    pci 0000:10:00.0: PME# disabled
    pci 0000:11:02.0: PME# supported from D0 D3hot D3cold
    pci 0000:11:02.0: PME# disabled
    pci 0000:11:04.0: PME# supported from D0 D3hot D3cold
    pci 0000:11:04.0: PME# disabled
    pci 0000:1b:0c.0: supports D1
    pci 0000:1b:0c.0: supports D2
    pci 0000:00:1e.0: transparent bridge
    bus 00 -> node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST.DWN1._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST.DWN2._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3.UPST.DWN2.BCOM._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3.UPST.DWN3.BCOM._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3.UPST.DWN4.BCOM._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3.UPST.DWN5.BCOM._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4.UPST.DWNB._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4.UPST.DWNC._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6.UPST.DWNB._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6.UPST.DWNC._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.SBEX._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.COMP._PRT]
    ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 5 6 7 10 *11 12)
    ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 *10 11 12)
    ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 *6 7 10 11 12)
    ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 10 *11 12)
    ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 *5 6 7 10 11 12)
    ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 6 7 10 *11 12)
    ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
    ACPI: PCI Interrupt Link [LK07] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
    Linux Plug and Play Support v0.97 (c) Adam Belay
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 11 devices
    ACPI: ACPI bus type pnp unregistered
    SCSI subsystem initialized
    libata version 3.00 loaded.
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    PCI: Using ACPI for IRQ routing
    Switched to high resolution mode on CPU 0
    Switched to high resolution mode on CPU 5
    Switched to high resolution mode on CPU 6
    Switched to high resolution mode on CPU 2
    Switched to high resolution mode on CPU 4
    Switched to high resolution mode on CPU 7
    Switched to high resolution mode on CPU 1
    Switched to high resolution mode on CPU 3
    system 00:07: ioport range 0x800-0x87f has been reserved
    system 00:07: ioport range 0x880-0x8bf has been reserved
    system 00:07: ioport range 0x8c0-0x8df has been reserved
    system 00:07: ioport range 0x8e0-0x8e3 has been reserved
    system 00:07: ioport range 0x8f0-0x8f1 has been reserved
    system 00:07: ioport range 0x900-0x900 has been reserved
    system 00:07: ioport range 0xc00-0xc7f has been reserved
    system 00:07: ioport range 0xca0-0xca7 has been reserved
    system 00:07: ioport range 0xca9-0xcab has been reserved
    system 00:07: ioport range 0xcad-0xcaf has been reserved
    system 00:08: ioport range 0xca8-0xca8 has been reserved
    system 00:08: ioport range 0xcac-0xcac has been reserved
    system 00:09: iomem range 0xe0000000-0xefffffff could not be reserved
    pci 0000:00:01.0: PCI bridge, secondary bus 0000:14
    pci 0000:00:01.0: IO window: disabled
    pci 0000:00:01.0: MEM window: disabled
    pci 0000:00:01.0: PREFETCH window: disabled
    pci 0000:17:00.0: PCI bridge, secondary bus 0000:19
    pci 0000:17:00.0: IO window: 0xe000-0xefff
    pci 0000:17:00.0: MEM window: 0xde200000-0xde3fffff
    pci 0000:17:00.0: PREFETCH window: disabled
    pci 0000:17:01.0: PCI bridge, secondary bus 0000:18
    pci 0000:17:01.0: IO window: disabled
    pci 0000:17:01.0: MEM window: disabled
    pci 0000:17:01.0: PREFETCH window: disabled
    pci 0000:16:00.0: PCI bridge, secondary bus 0000:17
    pci 0000:16:00.0: IO window: 0xe000-0xefff
    pci 0000:16:00.0: MEM window: 0xde200000-0xde3fffff
    pci 0000:16:00.0: PREFETCH window: disabled
    pci 0000:16:00.3: PCI bridge, secondary bus 0000:1a
    pci 0000:16:00.3: IO window: disabled
    pci 0000:16:00.3: MEM window: disabled
    pci 0000:16:00.3: PREFETCH window: disabled
    pci 0000:00:02.0: PCI bridge, secondary bus 0000:16
    pci 0000:00:02.0: IO window: 0xe000-0xefff
    pci 0000:00:02.0: MEM window: 0xde100000-0xde3fffff
    pci 0000:00:02.0: PREFETCH window: disabled
    pci 0000:02:01.0: PCI bridge, secondary bus 0000:03
    pci 0000:02:01.0: IO window: disabled
    pci 0000:02:01.0: MEM window: disabled
    pci 0000:02:01.0: PREFETCH window: disabled
    pci 0000:0a:00.0: PCI bridge, secondary bus 0000:0b
    pci 0000:0a:00.0: IO window: disabled
    pci 0000:0a:00.0: MEM window: 0xd6000000-0xd7ffffff
    pci 0000:0a:00.0: PREFETCH window: disabled
    pci 0000:02:02.0: PCI bridge, secondary bus 0000:0a
    pci 0000:02:02.0: IO window: disabled
    pci 0000:02:02.0: MEM window: 0xd6000000-0xd7ffffff
    pci 0000:02:02.0: PREFETCH window: disabled
    pci 0000:08:00.0: PCI bridge, secondary bus 0000:09
    pci 0000:08:00.0: IO window: disabled
    pci 0000:08:00.0: MEM window: 0xd8000000-0xd9ffffff
    pci 0000:08:00.0: PREFETCH window: disabled
    pci 0000:02:03.0: PCI bridge, secondary bus 0000:08
    pci 0000:02:03.0: IO window: disabled
    pci 0000:02:03.0: MEM window: 0xd8000000-0xd9ffffff
    pci 0000:02:03.0: PREFETCH window: disabled
    pci 0000:06:00.0: PCI bridge, secondary bus 0000:07
    pci 0000:06:00.0: IO window: disabled
    pci 0000:06:00.0: MEM window: 0xda000000-0xdbffffff
    pci 0000:06:00.0: PREFETCH window: disabled
    pci 0000:02:04.0: PCI bridge, secondary bus 0000:06
    pci 0000:02:04.0: IO window: disabled
    pci 0000:02:04.0: MEM window: 0xda000000-0xdbffffff
    pci 0000:02:04.0: PREFETCH window: disabled
    pci 0000:04:00.0: PCI bridge, secondary bus 0000:05
    pci 0000:04:00.0: IO window: disabled
    pci 0000:04:00.0: MEM window: 0xdc000000-0xddffffff
    pci 0000:04:00.0: PREFETCH window: disabled
    pci 0000:02:05.0: PCI bridge, secondary bus 0000:04
    pci 0000:02:05.0: IO window: disabled
    pci 0000:02:05.0: MEM window: 0xdc000000-0xddffffff
    pci 0000:02:05.0: PREFETCH window: disabled
    pci 0000:01:00.0: PCI bridge, secondary bus 0000:02
    pci 0000:01:00.0: IO window: disabled
    pci 0000:01:00.0: MEM window: 0xd6000000-0xddffffff
    pci 0000:01:00.0: PREFETCH window: disabled
    pci 0000:00:03.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:03.0: IO window: disabled
    pci 0000:00:03.0: MEM window: 0xd6000000-0xddffffff
    pci 0000:00:03.0: PREFETCH window: disabled
    pci 0000:0d:02.0: PCI bridge, secondary bus 0000:0f
    pci 0000:0d:02.0: IO window: disabled
    pci 0000:0d:02.0: MEM window: disabled
    pci 0000:0d:02.0: PREFETCH window: disabled
    pci 0000:0d:04.0: PCI bridge, secondary bus 0000:0e
    pci 0000:0d:04.0: IO window: disabled
    pci 0000:0d:04.0: MEM window: disabled
    pci 0000:0d:04.0: PREFETCH window: disabled
    pci 0000:0c:00.0: PCI bridge, secondary bus 0000:0d
    pci 0000:0c:00.0: IO window: disabled
    pci 0000:0c:00.0: MEM window: disabled
    pci 0000:0c:00.0: PREFETCH window: disabled
    pci 0000:00:04.0: PCI bridge, secondary bus 0000:0c
    pci 0000:00:04.0: IO window: disabled
    pci 0000:00:04.0: MEM window: disabled
    pci 0000:00:04.0: PREFETCH window: disabled
    pci 0000:11:02.0: PCI bridge, secondary bus 0000:13
    pci 0000:11:02.0: IO window: disabled
    pci 0000:11:02.0: MEM window: disabled
    pci 0000:11:02.0: PREFETCH window: disabled
    pci 0000:11:04.0: PCI bridge, secondary bus 0000:12
    pci 0000:11:04.0: IO window: disabled
    pci 0000:11:04.0: MEM window: disabled
    pci 0000:11:04.0: PREFETCH window: disabled
    pci 0000:10:00.0: PCI bridge, secondary bus 0000:11
    pci 0000:10:00.0: IO window: disabled
    pci 0000:00:06.0: MEM window: disabled
    pci 0000:00:06.0: PREFETCH window: disabled
    pci 0000:00:1c.0: PCI bridge, secondary bus 0000:15
    pci 0000:00:1c.0: IO window: disabled
    pci 0000:00:1c.0: MEM window: disabled
    pci 0000:00:1c.0: PREFETCH window: disabled
    pci 0000:00:1e.0: PCI bridge, secondary bus 0000:1b
    pci 0000:00:1e.0: IO window: 0xd000-0xdfff
    pci 0000:00:1e.0: MEM window: 0xde400000-0xde4fffff
    pci 0000:00:1e.0: PREFETCH window: 0x000000c8000000-0x000000cfffffff
    pci 0000:00:01.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36
    pci 0000:00:01.0: setting latency timer to 64
    pci 0000:00:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:02.0: setting latency timer to 64
    pci 0000:16:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:16:00.0: setting latency timer to 64
    pci 0000:17:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:17:00.0: setting latency timer to 64
    pci 0000:17:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    pci 0000:17:01.0: setting latency timer to 64
    pci 0000:16:00.3: setting latency timer to 64
    pci 0000:00:03.0: PCI INT A -> GSI 37 (level, low) -> IRQ 37
    pci 0000:00:03.0: setting latency timer to 64
    pci 0000:01:00.0: setting latency timer to 64
    pci 0000:02:01.0: setting latency timer to 64
    pci 0000:02:02.0: setting latency timer to 64
    pci 0000:0a:00.0: setting latency timer to 64
    pci 0000:02:03.0: setting latency timer to 64
    pci 0000:08:00.0: setting latency timer to 64
    pci 0000:02:04.0: setting latency timer to 64
    pci 0000:06:00.0: setting latency timer to 64
    pci 0000:02:05.0: setting latency timer to 64
    pci 0000:04:00.0: setting latency timer to 64
    pci 0000:04:00.0: setting latency timer to 64
    pci 0000:00:04.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
    pci 0000:00:04.0: setting latency timer to 64
    pci 0000:0c:00.0: setting latency timer to 64
    pci 0000:0d:02.0: setting latency timer to 64
    pci 0000:0d:04.0: setting latency timer to 64
    pci 0000:00:06.0: PCI INT A -> GSI 33 (level, low) -> IRQ 33
    pci 0000:00:06.0: setting latency timer to 64
    pci 0000:10:00.0: setting latency timer to 64
    pci 0000:11:02.0: setting latency timer to 64
    pci 0000:11:04.0: setting latency timer to 64
    pci 0000:00:1c.0: setting latency timer to 64
    pci 0000:00:1e.0: setting latency timer to 64
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    highmem bounce pool size: 64 pages
    HugeTLB registered 2 MB page size, pre-allocated 0 pages
    msgmni has been set to 1234
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered (default)
    pci 0000:1b:0c.0: Boot video device
    pcieport-driver 0000:00:01.0: setting latency timer to 64
    pcieport-driver 0000:00:01.0: found MSI capability
    pci_express 0000:00:01.0cie00: allocate port service
    pcieport-driver 0000:00:02.0: setting latency timer to 64
    pcieport-driver 0000:00:02.0: found MSI capability
    pci_express 0000:00:02.0cie00: allocate port service
    pci_express 0000:00:02.0cie00: allocate port service
    pcieport-driver 0000:00:03.0: setting latency timer to 64
    pcieport-driver 0000:00:03.0: found MSI capability
    pci_express 0000:00:03.0cie00: allocate port service
    pcieport-driver 0000:00:04.0: setting latency timer to 64
    pcieport-driver 0000:00:04.0: found MSI capability
    pci_express 0000:00:04.0cie00: allocate port service
    pcieport-driver 0000:00:06.0: setting latency timer to 64
    pcieport-driver 0000:00:06.0: found MSI capability
    pci_express 0000:00:06.0cie00: allocate port service
    pcieport-driver 0000:00:1c.0: setting latency timer to 64
    pcieport-driver 0000:00:1c.0: found MSI capability
    pci_express 0000:00:1c.0cie00: allocate port service
    pci_express 0000:00:1c.0cie02: allocate port service
    pcieport-driver 0000:01:00.0: setting latency timer to 64
    pcieport-driver 0000:02:01.0: setting latency timer to 64
    pcieport-driver 0000:02:01.0: found MSI capability
    pcieport-driver 0000:02:02.0: setting latency timer to 64
    pcieport-driver 0000:02:02.0: found MSI capability
    pcieport-driver 0000:02:03.0: setting latency timer to 64
    pcieport-driver 0000:02:03.0: found MSI capability
    pcieport-driver 0000:02:04.0: setting latency timer to 64
    pcieport-driver 0000:02:04.0: found MSI capability
    pcieport-driver 0000:02:05.0: setting latency timer to 64
    pcieport-driver 0000:02:05.0: found MSI capability
    pcieport-driver 0000:0c:00.0: setting latency timer to 64
    pcieport-driver 0000:0d:02.0: setting latency timer to 64
    pcieport-driver 0000:0d:02.0: found MSI capability
    pcieport-driver 0000:0d:04.0: setting latency timer to 64
    pcieport-driver 0000:0d:04.0: found MSI capability
    pcieport-driver 0000:10:00.0: setting latency timer to 64
    pcieport-driver 0000:11:02.0: setting latency timer to 64
    pcieport-driver 0000:11:02.0: found MSI capability
    ACPI: Power Button (FF) [PWRF]
    processor ACPI0007:00: registered as cooling_device0
    processor ACPI0007:01: registered as cooling_device1
    processor ACPI0007:02: registered as cooling_device2
    processor ACPI0007:03: registered as cooling_device3
    processor ACPI0007:04: registered as cooling_device4
    processor ACPI0007:05: registered as cooling_device5
    processor ACPI0007:06: registered as cooling_device6
    processor ACPI0007:07: registered as cooling_device7
    Real Time Clock Driver v1.12ac
    Non-volatile memory driver v1.2
    Linux agpgart interface v0.103
    [drm] Initialized drm 1.1.0 20060810
    brd: module loaded
    loop: module loaded
    pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de
    Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.7.9 (July 18, 2008)
    bnx2 0000:05:00.0: PCI INT A -> GSI 38 (level, low) -> IRQ 38
    eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
    133MHz found at mem dc000000, IRQ 38, node addr 00:1e:c9:d9:84:57
    bnx2 0000:07:00.0: PCI INT A -> GSI 37 (level, low) -> IRQ 37
    eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
    133MHz found at mem da000000, IRQ 37, node addr 00:1e:c9:d9:84:59
    bnx2 0000:09:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    eth2: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
    133MHz found at mem d8000000, IRQ 19, node addr 00:1e:c9:d9:84:5b
    bnx2 0000:0b:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    eth3: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
    133MHz found at mem d6000000, IRQ 18, node addr 00:1e:c9:d9:84:5d
    PPP generic driver version 2.4.2
    PPP Deflate Compression module registered
    PPP BSD Compression module registered
    tun: Universal TUN/TAP device driver, 1.6
    Uniform Multi-Platform E-IDE driver
    ide_generic: please use "probe_mask=0x3f" module parameter for probing
    all legacy ISA IDE ports
    Probing IDE interface ide0...
    hda: TSSTcorpDVD-ROM TS-L333A, ATAPI CD/DVD-ROM drive
    Probing IDE interface ide1...
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    ide1 at 0x170-0x177,0x376 on irq 15
    megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
    megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
    megasas: 00.00.03.20-rc1 Mon. March 10 11:02:31 PDT 2008
    megasas: 0x1000:0x0060:0x1028:0x1f0c: bus 25:slot 0:func 0
    megaraid_sas 0000:19:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    megaraid_sas 0000:19:00.0: setting latency timer to 64
    megasas: FW now in Ready state
    scsi0 : LSI SAS based MegaRAID driver
    scsi 0:0:0:0: Direct-Access SEAGATE ST973451SS SM04 PQ: 0 ANSI: 5
    scsi 0:0:1:0: Direct-Access SEAGATE ST973451SS SM04 PQ: 0 ANSI: 5
    scsi 0:0:2:0: Direct-Access SEAGATE ST973451SS SM04 PQ: 0 ANSI: 5
    scsi 0:0:3:0: Direct-Access SEAGATE ST973451SS SM04 PQ: 0 ANSI: 5
    scsi 0:0:4:0: Direct-Access SEAGATE ST973451SS SM04 PQ: 0 ANSI: 5
    scsi 0:0:5:0: Direct-Access SEAGATE ST973451SS SM04 PQ: 0 ANSI: 5
    scsi 0:0:6:0: Direct-Access SEAGATE ST973451SS SM04 PQ: 0 ANSI: 5
    scsi 0:0:7:0: Direct-Access SEAGATE ST973451SS SM04 PQ: 0 ANSI: 5
    scsi 0:0:32:0: Enclosure DP BACKPLANE 1.06 PQ: 0 ANSI: 5
    scsi 0:2:0:0: Direct-Access DELL PERC 6/i 1.11 PQ: 0 ANSI: 5
    Driver 'sd' needs updating - please use bus_type methods
    sd 0:2:0:0: [sda] 710410240 512-byte hardware sectors (363730 MB)
    sd 0:2:0:0: [sda] Write Protect is off
    sd 0:2:0:0: [sda] Mode Sense: 1f 00 00 08
    sd 0:2:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
    support DPO or FUA
    sd 0:2:0:0: [sda] 710410240 512-byte hardware sectors (363730 MB)
    sd 0:2:0:0: [sda] Mode Sense: 1f 00 00 08
    sd 0:2:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
    support DPO or FUA
    sd 0:2:0:0: [sda] 710410240 512-byte hardware sectors (363730 MB)
    sd 0:2:0:0: [sda] Write Protect is off
    sd 0:2:0:0: [sda] Mode Sense: 1f 00 00 08
    sd 0:2:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
    support DPO or FUA
    sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12
    sda13 sda14 sda15 >
    sd 0:2:0:0: [sda] Attached SCSI disk
    ata_piix 0000:00:1f.2: version 2.12
    ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
    ata_piix 0000:00:1f.2: BAR 0: can't reserve I/O region [0x1f0-0x1f7]
    ata_piix 0000:00:1f.2: failed to request/iomap BARs for port 0 (errno=-16)
    ata_piix 0000:00:1f.2: BAR 2: can't reserve I/O region [0x170-0x177]
    ata_piix 0000:00:1f.2: failed to request/iomap BARs for port 1 (errno=-16)
    ata_piix 0000:00:1f.2: no available native port
    Fusion MPT base driver 3.04.07
    Copyright (c) 1999-2008 LSI Corporation
    Fusion MPT SPI Host driver 3.04.07
    ehci_hcd 0000:00:1d.7: PCI INT B -> GSI 21 (level, low) -> IRQ 21
    ehci_hcd 0000:00:1d.7: setting latency timer to 64
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:1d.7: debug port 1
    ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
    ehci_hcd 0000:00:1d.7: irq 21, io mem 0xde0ffc00
    ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 8 ports detected
    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    ....
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  6. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 11:54 AM, Max Krasnyansky wrote:

    > Are you running 32-bit kernel ?


    Yes. But, does it matter?

    Thanks,
    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  7. references:in-reply-to:content-type:

    Jeff Chua wrote:
    > On Wed, Aug 6, 2008 at 11:54 AM, Max Krasnyansky wrote:
    >
    >> Are you running 32-bit kernel ?

    >
    > Yes. But, does it matter?


    It used to. 64-bit kernel used to handle maxcpus option as documented in the
    Documentation/cpu-hotplug.txt and 32-bit one was broken.
    I just looked at the latest code and realized that both are now broken. They
    ignore cpu id > maxcpus instead of not-booting them.

    I'll send a patch that fixes that tomorrow.

    Max
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  8. Re: 2.6.27rc1 cannot boot more than 8CPUs

    Max Krasnyansky wrote:
    > Jeff Chua wrote:
    >> On Wed, Aug 6, 2008 at 11:54 AM, Max Krasnyansky
    >> wrote:
    >>
    >>> Are you running 32-bit kernel ?

    >>
    >> Yes. But, does it matter?

    >
    > It used to. 64-bit kernel used to handle maxcpus option as documented in
    > the Documentation/cpu-hotplug.txt and 32-bit one was broken.
    > I just looked at the latest code and realized that both are now broken.
    > They ignore cpu id > maxcpus instead of not-booting them.
    >


    Yes. I have an x86_64 box with 4 cpus, but yesterday when I booted up with maxcpus=2,
    I didn't see the other 2 cpus.

    > I'll send a patch that fixes that tomorrow.
    >


    greate

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  9. Re: 2.6.27rc1 cannot boot more than 8CPUs

    From: "Jeff Chua"
    Date: Wed, 6 Aug 2008 11:15:30 +0800

    > I've a Dell R900 with 4 quad-core Xeon processors (total 16CPUs), but
    > can only managed to boot up with CONFIG_NR_CPUS=8. Setting
    > CONFIG_NR_CPUS=16 causes the kernel to hang while booting.
    >
    >
    > Here's the dmesg with CONFIG_NR_CPUS=8 ...


    Do you have lockdep enabled? If sure, try turning that off.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  10. Re: 2.6.27rc1 cannot boot more than 8CPUs



    On Wed, 6 Aug 2008, Jeff Chua wrote:
    >
    > How can I debug this further? I'm using the latest linux git pull.


    One trivial thing to try would be to just bisect it. I assume 2.6.26 is
    fine, so while it will take a few boots to try it out (there's 8111
    commits in between, so 13 reboots should do it), the advantage of
    bisection is that it's fairly straightforward to do even if you don't have
    any clue where the problem might lurk.

    And with your machine, recompiling the kernel 13 times shouldn't take that
    long

    Linus
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  11. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 2:01 PM, Linus Torvalds
    wrote:

    > One trivial thing to try would be to just bisect it. I assume 2.6.26 is
    > fine, so while it will take a few boots to try it out (there's 8111
    > commits in between, so 13 reboots should do it), the advantage of
    > bisection is that it's fairly straightforward to do even if you don't have
    > any clue where the problem might lurk.


    Bisecting now.

    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  12. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 1:19 PM, David Miller wrote:
    > From: "Jeff Chua"
    > Date: Wed, 6 Aug 2008 11:15:30 +0800
    > Do you have lockdep enabled? If sure, try turning that off.


    It's enabled by default, and I can't seem to disable it even if I
    commented it out or delete it, it comes back after running "make".

    CONFIG_X86_32=y
    # CONFIG_X86_64 is not set
    CONFIG_X86=y
    CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
    # 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_FAST_CMPXCHG_LOCAL=y
    CONFIG_MMU=y
    CONFIG_ZONE_DMA=y
    CONFIG_GENERIC_ISA_DMA=y
    CONFIG_GENERIC_IOMAP=y
    CONFIG_GENERIC_BUG=y
    CONFIG_GENERIC_HWEIGHT=y


    Thanks,
    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  13. Re: 2.6.27rc1 cannot boot more than 8CPUs

    From: "Jeff Chua"
    Date: Wed, 6 Aug 2008 14:42:11 +0800

    > On Wed, Aug 6, 2008 at 1:19 PM, David Miller wrote:
    > > From: "Jeff Chua"
    > > Date: Wed, 6 Aug 2008 11:15:30 +0800
    > > Do you have lockdep enabled? If sure, try turning that off.

    >
    > It's enabled by default, and I can't seem to disable it even if I
    > commented it out or delete it, it comes back after running "make".


    You have to turn off CONFIG_PROVE_LOCKING, in fact just turn off
    everything in the lock debugging section:

    # CONFIG_DEBUG_RT_MUTEXES is not set
    # CONFIG_RT_MUTEX_TESTER is not set
    # CONFIG_DEBUG_SPINLOCK is not set
    # CONFIG_DEBUG_MUTEXES is not set
    # CONFIG_DEBUG_LOCK_ALLOC is not set
    # CONFIG_PROVE_LOCKING is not set
    # CONFIG_LOCK_STAT is not set
    # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
    # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  14. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Tue, Aug 5, 2008 at 11:42 PM, Jeff Chua wrote:
    > On Wed, Aug 6, 2008 at 1:19 PM, David Miller wrote:
    >> From: "Jeff Chua"
    >> Date: Wed, 6 Aug 2008 11:15:30 +0800
    >> Do you have lockdep enabled? If sure, try turning that off.

    >
    > It's enabled by default, and I can't seem to disable it even if I
    > commented it out or delete it, it comes back after running "make".
    >
    > CONFIG_X86_32=y
    > # CONFIG_X86_64 is not set
    > CONFIG_X86=y
    > CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
    > # 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_FAST_CMPXCHG_LOCAL=y
    > CONFIG_MMU=y
    > CONFIG_ZONE_DMA=y
    > CONFIG_GENERIC_ISA_DMA=y
    > CONFIG_GENERIC_IOMAP=y
    > CONFIG_GENERIC_BUG=y
    > CONFIG_GENERIC_HWEIGHT=y
    >
    >


    do you have

    CONFIG_X86_GENERICARCH=y
    CONFIG_X86_BIGSMP=y

    8 more cpu need bigsmp mode.

    YH
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  15. Re: 2.6.27rc1 cannot boot more than 8CPUs

    From: "Jeff Chua"
    Date: Wed, 6 Aug 2008 17:33:07 +0800

    > On Wed, Aug 6, 2008 at 3:18 PM, David Miller wrote:
    >
    > > You have to turn off CONFIG_PROVE_LOCKING, in fact just turn off
    > > everything in the lock debugging section:
    > >
    > > # CONFIG_DEBUG_RT_MUTEXES is not set
    > > # CONFIG_RT_MUTEX_TESTER is not set
    > > # CONFIG_DEBUG_SPINLOCK is not set
    > > # CONFIG_DEBUG_MUTEXES is not set
    > > # CONFIG_DEBUG_LOCK_ALLOC is not set
    > > # CONFIG_PROVE_LOCKING is not set
    > > # CONFIG_LOCK_STAT is not set
    > > # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
    > > # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
    > >

    >
    > I don't any option to turn these off. Still searching.


    Maybe edit the ".config" file at the top level of the kernel
    sources and then type "make oldconfig" ?!?!?!

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  16. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 3:18 PM, David Miller wrote:

    > You have to turn off CONFIG_PROVE_LOCKING, in fact just turn off
    > everything in the lock debugging section:
    >
    > # CONFIG_DEBUG_RT_MUTEXES is not set
    > # CONFIG_RT_MUTEX_TESTER is not set
    > # CONFIG_DEBUG_SPINLOCK is not set
    > # CONFIG_DEBUG_MUTEXES is not set
    > # CONFIG_DEBUG_LOCK_ALLOC is not set
    > # CONFIG_PROVE_LOCKING is not set
    > # CONFIG_LOCK_STAT is not set
    > # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
    > # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
    >


    I don't any option to turn these off. Still searching.

    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  17. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 4:49 PM, Yinghai Lu wrote:
    > do you have
    >
    > CONFIG_X86_GENERICARCH=y
    > CONFIG_X86_BIGSMP=y
    >
    > 8 more cpu need bigsmp mode.



    Are these the ones that supposed to be set? Any, can't find a place to
    set these using menuconfig.

    # CONFIG_X86_GENERICARCH is not set
    # CONFIG_X86_VSMP is not set

    Thanks
    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  18. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 5:35 PM, Jeff Chua wrote:
    > On Wed, Aug 6, 2008 at 4:49 PM, Yinghai Lu wrote:
    >> do you have
    >> CONFIG_X86_GENERICARCH=y
    >> CONFIG_X86_BIGSMP=y
    >> 8 more cpu need bigsmp mode.

    > Are these the ones that supposed to be set? Any, can't find a place to
    > set these using menuconfig.
    >
    > # CONFIG_X86_GENERICARCH is not set
    > # CONFIG_X86_VSMP is not set


    Sorry, found it. These are not obvious. I had selected
    "Subarchitecture Type (PC-compatible)" and could find a place to set
    CONFIG_X86_GENERICARCH.

    Just found it under " Subarchitecture Type (Generic architecture)",
    and then it shows the CONFIG_X86_BIGSMP option.

    Ok, compiling and testing now.

    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  19. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 5:36 PM, David Miller wrote:
    > From: "Jeff Chua"
    > Date: Wed, 6 Aug 2008 17:33:07 +0800
    >
    >> On Wed, Aug 6, 2008 at 3:18 PM, David Miller wrote:
    >>
    >> > You have to turn off CONFIG_PROVE_LOCKING, in fact just turn off
    >> > everything in the lock debugging section:

    > Maybe edit the ".config" file at the top level of the kernel
    > sources and then type "make oldconfig" ?!?!?!


    Ok, may be not as bad as I thought. These are not in .config meaning,
    they are not set. So, it should ok. I'll test out these two first.

    > CONFIG_X86_GENERICARCH=y
    > CONFIG_X86_BIGSMP=y


    Thanks,
    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  20. Re: 2.6.27rc1 cannot boot more than 8CPUs

    On Wed, Aug 6, 2008 at 2:42 PM, Jeff Chua wrote:
    > On Wed, Aug 6, 2008 at 2:01 PM, Linus Torvalds
    > wrote:
    >> One trivial thing to try would be to just bisect it. I assume 2.6.26 is

    > Bisecting now.


    Thanks to all the great helpful suggestions from everyone, and this
    turns out that I just need to enable the following switches, so I
    didn't bisect further, and since it's first machine that I've tried
    with more than 8 CPUs so I wasn't sure whether 2.6.16 has the same
    problem, but if you wish, I could give 2.6.16 a try.

    > CONFIG_X86_GENERICARCH=y
    > CONFIG_X86_BIGSMP=y


    Thank you all for the great linux kernel!

    Jeff.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread
Page 1 of 2 1 2 LastLast