linux-kernel - Re: Git next: Second stage of cpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19f34abd0811042352q2df6ed0r6c92a35159d2b04c@mail.gmail.com>
Date:	Wed, 5 Nov 2008 08:52:01 +0100
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Stephen Rothwell" <sfr@...b.auug.org.au>
Cc:	"Christoph Lameter" <cl@...ux-foundation.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, travis@....com,
	linux-next@...r.kernel.org
Subject: Re: Git next: Second stage of cpu_alloc patches

On Wed, Nov 5, 2008 at 8:26 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Christoph,
>
> On Tue, 4 Nov 2008 19:52:05 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:
>>
>> On Tue, 4 Nov 2008 20:56:52 -0600 (CST) Christoph Lameter <cl@...ux-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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/