From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: "Christoph Lameter" <cl@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, travis@sgi.com,
linux-next@vger.kernel.org
Subject: Re: Git next: Second stage of cpu_alloc patches
Date: Wed, 5 Nov 2008 08:52:01 +0100 [thread overview]
Message-ID: <19f34abd0811042352q2df6ed0r6c92a35159d2b04c@mail.gmail.com> (raw)
In-Reply-To: <20081105182642.8497301a.sfr@canb.auug.org.au>
On Wed, Nov 5, 2008 at 8:26 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Christoph,
>
> On Tue, 4 Nov 2008 19:52:05 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> On Tue, 4 Nov 2008 20:56:52 -0600 (CST) Christoph Lameter <cl@linux-foundation.org> wrote:
>>
>> > The second stage of the cpu_alloc patchset can be pulled from
>> >
>> > kernel.org/pub/scm/linux/kernel/git/christoph/work.git cpu_alloc_stage2
>>
>> Please send the patches for review. Always.
>
> And I would like to see a bit of positive feedback from the first set
> (given we have boot failures bisected down to this stuff) before we add
> more on top.
Thanks. I will try out today's linux-next later today (if I can find
the time for it).
Just in case it helps track down the problem: Adding percpu=100000 to
the kernel command line got the thing booting for me. The number
itself was picked at random, but it worked on the first try. The
machine is a single-core P4 3.0 GHz with HT, 1G RAM, using slightly
modified F9 config.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-11-05 7:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 2:56 Christoph Lameter
2008-11-05 3:52 ` Andrew Morton
2008-11-05 7:26 ` Stephen Rothwell
2008-11-05 7:52 ` Vegard Nossum [this message]
2008-11-05 13:59 ` Christoph Lameter
2008-11-05 13:54 ` Christoph Lameter
2008-11-05 16:27 ` Andrew Morton
2008-11-05 21:12 ` Vegard Nossum
2008-11-05 21:24 ` Andrew Morton
2008-11-05 23:58 ` Johannes Weiner
2008-11-06 0:54 ` Stephen Rothwell
2008-11-06 14:54 ` Christoph Lameter
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=19f34abd0811042352q2df6ed0r6c92a35159d2b04c@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=travis@sgi.com \
/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
all inboxes | Powered by JetHome®