linux-kernel - Re: 2.6.24 git2/mm1: cpu_to_node mapping to non-existant nodes causing boot failure

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: <47BAFFD3.1070606@sgi.com>
Date:	Tue, 19 Feb 2008 08:12:03 -0800
From:	Mike Travis <travis@....com>
To:	Mel Gorman <mel@....ul.ie>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, mingo@...e.hu, tglx@...utronix.de,
	Christoph Lameter <clameter@....com>,
	Jack Steiner <steiner@....com>
Subject: Re: 2.6.24 git2/mm1: cpu_to_node mapping to non-existant nodes causing
 boot failure

Mike Travis wrote:
> Mel Gorman wrote:
> 
>> If you send me patches to apply on top of 2.6.25-rc1, I'll give them a spin
>> on the machine in question. Reverting didn't work out very well as there are
>> too many collisions with patches that were applied later. I eventually got
>> the machine booting but it only succeeds because it only brings up one core
>> on each processor.  The patch, which is pretty brain damaged is below in case
>> it helps you guess what the real problem is. dmesg logs are attached of the
>> vanilla failure with acpi=debug and the log with the patch applied showing
>> "__cpu_up: bad cpu 1" and "__cpu_up: bad cpu3" (i.e. the second cores of
>> each machine).
>>
> 
> This should completely undo the change to 16 bit apic ids until we can figure
> out the problem with the memory-less nodes.  I checked it on both the numa
> and non-numa x86_64 box.
> 
> Thanks,
> Mike
> 

Hi Mel,

Did you get a chance to try out this patch to see if it cleared up the problem
booting on your x86_64 numa box?

Thanks,
Mike
--
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/