public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Hugh Dickins <hugh@veritas.com>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Alexey Dobriyan <adobriyan@sw.ru>,
	torvalds@osdl.org, ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc4: maxcpus still broken
Date: Wed, 29 Aug 2007 02:41:35 -0400	[thread overview]
Message-ID: <200708290241.36092.lenb@kernel.org> (raw)
In-Reply-To: <20070829052331.GB1765@martell.zuzino.mipt.ru>

On Wednesday 29 August 2007 01:23, Alexey Dobriyan wrote:
> On Wed, Aug 29, 2007 at 06:03:34AM +0100, Hugh Dickins wrote:
> > On Wed, 29 Aug 2007, Alexey Dobriyan wrote:
> > > On Wed, Aug 29, 2007 at 01:35:57AM +0200, Michal Piotrowski wrote:
> > > > On 28/08/07, Alexey Dobriyan <adobriyan@sw.ru> wrote:
> > > > > Every time I try to boot with maxcpus=1 it dies show_stat():
> > > > 
> > > > Is this a regression?
> > > 
> > > yep
> > 
> > A regression since when, I wonder?
> 
> Anything before "ACPI: boot correctly with "nosmp" or "maxcpus=0"" is
> fine.

In 2.6.23-rc4, maxcpus=1 is working for me, with and without acpi=off.
Can you post the failing .config?

thanks,
-Len

  reply	other threads:[~2007-08-29  6:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 11:14 2.6.23-rc4: maxcpus still broken Alexey Dobriyan
2007-08-28 23:35 ` Michal Piotrowski
2007-08-29  4:39   ` Alexey Dobriyan
2007-08-29  5:03     ` Hugh Dickins
2007-08-29  5:23       ` Alexey Dobriyan
2007-08-29  6:41         ` Len Brown [this message]
2007-08-29  7:25           ` Alexey Dobriyan
2007-08-31  3:26             ` [PATCH] fix maxcpus=1 oops in show_stat() Hugh Dickins
2007-08-31  4:33               ` Linus Torvalds
2007-08-31  7:37               ` Alexey Dobriyan
2007-08-29 20:20       ` 2.6.23-rc4: maxcpus still broken Hugh Dickins

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=200708290241.36092.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=adobriyan@gmail.com \
    --cc=adobriyan@sw.ru \
    --cc=ak@suse.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox