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: <1193692862.3133.14.camel@avenin.ebourne.me.uk>
Date:	Mon, 29 Oct 2007 21:21:02 +0000
From:	Martin Ebourne <martin@...ler.org>
To:	Dave Jones <davej@...hat.com>
Cc:	Andi Kleen <ak@...e.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Zou Nan hai <nanhai.zou@...el.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>, stable@...nel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: 2.6.23 boot failures on x86-64.

On Mon, 2007-10-29 at 15:43 -0400, Dave Jones wrote:
> On Mon, Oct 29, 2007 at 08:03:09PM +0100, Andi Kleen wrote:
>  > >  > But if allocating bootmem >4G doesn't work on these systems
>  > >  > most likely they have more problems anyways. It might be better
>  > >  > to find out what goes wrong exactly.
>  > > Any ideas on what to instrument ?
>  > 
>  > See what address the bootmem_alloc_high returns; check if it overlaps
>  > with something etc.
>  > 
>  > Fill the memory on the system and see if it can access all of its memory.
> 
> Martin, as you have one of the affected systems, do you feel up to this?

Faking a node at 0000000000000000-000000001fff0000
Bootmem setup node 0 0000000000000000-000000001fff0000
sparse_early_mem_map_alloc: returned address ffff81000070b000

My box has 512MB of RAM.

Cheers,

Martin.

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ