All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs
Date: Tue, 05 Aug 2008 20:54:45 -0700	[thread overview]
Message-ID: <48992085.3050203@qualcomm.com> (raw)
In-Reply-To: <b6a2187b0808052050h35e2786fwfbf1e1dd5c37d8cf@mail.gmail.com>

Jeff Chua wrote:
> On Wed, Aug 6, 2008 at 11:31 AM, Max Krasnyansky <maxk@qualcomm.com> 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



  reply	other threads:[~2008-08-06  3:54 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  3:15 2.6.27rc1 cannot boot more than 8CPUs Jeff Chua
2008-08-06  3:31 ` Max Krasnyansky
2008-08-06  3:50   ` Jeff Chua
2008-08-06  3:54     ` Max Krasnyansky [this message]
2008-08-06  4:06       ` Jeff Chua
2008-08-06  4:48         ` Max Krasnyansky
2008-08-06  4:53           ` Li Zefan
2008-08-06 20:11             ` Max Krasnyansky
     [not found] ` <86802c440808052050u489264beo30812523669ef4df@mail.gmail.com>
2008-08-06  4:05   ` Jeff Chua
2008-08-06  5:19 ` David Miller
2008-08-06  6:42   ` Jeff Chua
2008-08-06  7:18     ` David Miller
2008-08-06  9:33       ` Jeff Chua
2008-08-06  9:36         ` David Miller
2008-08-06  9:50           ` Jeff Chua
2008-08-06  8:49     ` Yinghai Lu
2008-08-06  9:35       ` Jeff Chua
2008-08-06  9:42         ` Jeff Chua
2008-08-06  6:01 ` Linus Torvalds
2008-08-06  6:42   ` Jeff Chua
2008-08-06 15:33     ` Jeff Chua
2008-08-11 19:59       ` Ingo Molnar
2008-08-11 20:03         ` Yinghai Lu
2008-08-11 20:08           ` Ingo Molnar
2008-08-11 20:12             ` Yinghai Lu
2008-08-11 20:36               ` Yinghai Lu
2008-08-11 20:44                 ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2008-08-06 11:09 Jeff Chua
2008-08-06 16:13 ` Yinghai Lu
2008-08-06 16:34   ` Jeff Chua
2008-08-11 19:54 ` Ingo Molnar
2008-08-13 14:16 ` Ingo Molnar
2008-08-13 17:10   ` Jeff Chua
2008-08-13 17:33     ` Jeff Chua
2008-08-13 17:39       ` Ingo Molnar
2008-08-13 17:46         ` Yinghai Lu
2008-08-13 18:33           ` Yinghai Lu
2008-08-14  7:16             ` Jeff Chua
2008-08-14  8:59               ` Yinghai Lu
2008-08-14  9:07               ` Ingo Molnar
2008-08-15 10:34 Jeff Chua
2008-08-15 14:07 ` Ingo Molnar
2008-08-18  3:07   ` Jeff Chua
2008-08-18  8:00     ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48992085.3050203@qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.