Bug#476120: linux-2.6: please set CONFIG_X86_BIGSMP - Debian

This is a discussion on Bug#476120: linux-2.6: please set CONFIG_X86_BIGSMP - Debian ; Package: linux-2.6 Severity: normal Hi, on a recent intel quad-core (core2) CPU, CONFIG_X86_BIGSMP=y is needed to boot with more than 8 cpu. Without it, booting stops after CPU detection. Booting works when setting maxcpus=8 as boot parameter (but, obviously, you ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Bug#476120: linux-2.6: please set CONFIG_X86_BIGSMP

  1. Bug#476120: linux-2.6: please set CONFIG_X86_BIGSMP

    Package: linux-2.6
    Severity: normal

    Hi,

    on a recent intel quad-core (core2) CPU, CONFIG_X86_BIGSMP=y is needed
    to boot with more than 8 cpu.

    Without it, booting stops after CPU detection. Booting works when
    setting maxcpus=8 as boot parameter (but, obviously, you are then
    limited to 8 cores).

    Quadri Quad-core systems becomes more and more widespread these days
    (think virtualization), making x86 machines with more than 8 CPUs more
    common. Debian (be it Etch or Lenny) won't work on them.

    Please, enable this option, so that debian can be used for a high-end
    virtualization system without recompiling !

    Backporting this to Etch as well seems mostly harmless to me, but I'll
    let a kernel guru check

    Cheers,

    Clément Hermann (nodens)

    -- (Irrelevant) System Information:
    Debian Release: lenny/sid
    APT prefers unstable
    APT policy: (990, 'unstable'), (1, 'experimental')
    Architecture: amd64 (x86_64)

    Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
    Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
    Shell: /bin/sh linked to /bin/bash

  2. Bug#476120: marked as done (linux-2.6: please set CONFIG_X86_BIGSMP)


    Your message dated Wed, 24 Sep 2008 13:03:01 +0000
    with message-id
    and subject line Bug#476120: fixed in linux-2.6 2.6.26-6
    has caused the Debian Bug report #476120,
    regarding linux-2.6: please set CONFIG_X86_BIGSMP
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system
    misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    476120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476120
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


+ Reply to Thread