| 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
| ||
|
Date: Fri, 08 Oct 2010 15:15:04 -0700 From: Yinghai Lu <yinghai@...nel.org> To: Russ Anderson <rja@....com> CC: linux-kernel <linux-kernel@...r.kernel.org>, tglx@...utronix.de, "H. Peter Anvin" <h.peter.anvin@...el.com>, Jack Steiner <steiner@....com> Subject: Re: [BUG] x86: bootmem broken on SGI UV On 10/08/2010 02:34 PM, Russ Anderson wrote: > [BUG] x86: bootmem broken on SGI UV > > Recent community kernels do not boot on SGI UV x86 hardware with > more than one socket. I suspect the problem is due to recent > bootmem/e820 changes. > > What is happening is the e280 table defines a memory range. > > BIOS-e820: 0000000100000000 - 0000001080000000 (usable) > > The SRAT table shows that memory range is spread over two nodes. > > SRAT: Node 0 PXM 0 100000000-800000000 > SRAT: Node 1 PXM 1 800000000-1000000000 > SRAT: Node 0 PXM 0 1000000000-1080000000 > > Previously, the kernel early_node_map[] would show three entries > with the proper node. > > [ 0.000000] 0: 0x00100000 -> 0x00800000 > [ 0.000000] 1: 0x00800000 -> 0x01000000 > [ 0.000000] 0: 0x01000000 -> 0x01080000 > > The problem is recent community kernel early_node_map[] shows > only two entries with the node 0 entry overlapping the node 1 > entry. > > 0: 0x00100000 -> 0x01080000 > 1: 0x00800000 -> 0x01000000 > found the root cause, will send patch out today or tomorrow. Thanks Yinghai -- 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/
Powered by blists - more mailing lists